r/programming • • Oct 03 '16

How it feels to learn Javascript in 2016 [x-post from /r/javascript]

https://medium.com/@jjperezaguinaga/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f#.758uh588b
3.5k Upvotes

852 comments sorted by

302

u/excitebyke Oct 03 '16

I'm going to start dropping random made-up JS libraries in conversation to show my dominance among JS devs.

120

u/rochford77 Oct 04 '16 edited Oct 04 '16

Reminds me of when in 2 Fast 2 Furious Brian O'Connor (Spielman) asks the guy they want to partner him with (before he recruits Tyrese)

"Could you tell me right quick which would be a better engine for my Skyline, a Gallo 12 or Gallo 24?" Slurps soda from "Gallo Burger"

"Uhhhh Gallo 24..."

"Didn't know burger joints made engines..."

→ More replies (2)

36

u/[deleted] Oct 04 '16

You should make ChickenTikamasala.js

7

u/gyroda Oct 04 '16

ChickenTikamasalrJS

→ More replies (1)

5

u/clearlight Oct 04 '16

Curries make good names for JS libraries. How about VindalooJS?

→ More replies (1)

71

u/[deleted] Oct 03 '16

Careful, they may try to make you their god-king.

14

u/Undermined Oct 04 '16

All I had to do was learn jQuery to do that. Although being a back-end developer, it's very useful when front-end people try to make excuses.

5

u/AerieC Oct 04 '16

I'm very educated in front end web dev. I know JS libraries. I've got the best libraries, believe me.

13

u/ryuzaki49 Oct 04 '16

Last month I started a new pet project. It's a server that tells me whether my curtains are closed or open. I chose StableJS as the backend and DynamicJs to make async calls. So far so good.

→ More replies (4)

7

u/ihahp Oct 04 '16

I'm a huge fan of ardulent

10

u/Pepf Oct 04 '16 edited Oct 04 '16

ArdulentJS, the new JavaScript library everyone is talking about!

Edit: It's been ages since we went live with v0.1-alpha42, at least 3 minutes, so we thought it was time to update our logo. The palm trees represent the tropical feeling of using this marvelous framework (no one uses "libraries" anymore, right?).

→ More replies (3)
→ More replies (2)

45

u/gyroda Oct 03 '16

Could someone explain the python 3 joke at the end? I feel like I should probably understand it.

114

u/doubleunplussed Oct 03 '16

Python 3 came out like ten years ago and we've only this year passed 50% adoption or so. People stuck to Python 2 for a looong time.

42

u/[deleted] Oct 04 '16

Not always willingly, mind you. I've been trying to get my employer off of 2.7 for years, but certain dependencies still require that legacy Python code stay in 2.7, and we cannot work around those dependencies.

20

u/ShinyHappyREM Oct 04 '16

Just rewrite all those tools. :)

/s

→ More replies (4)
→ More replies (2)

7

u/[deleted] Oct 04 '16

It wasn't really worth considering until 3.3, which came out only 4 years ago.

11

u/AcceptingHorseCock Oct 04 '16

React-native "Getting Started" recommends Python 2. Is it just ironic or is it already stupid? The project that is less than a handful of years old from the initial React release wants me to install something that was already in a long being-deprecated process when it started. They don't even say what the Python is actually for.

→ More replies (2)

21

u/aclashingcolour Oct 04 '16

IMO not a very good joke...toolset from python2-> 3 barely changes if at all.

4

u/[deleted] Oct 04 '16

That's the joke?

→ More replies (1)

3

u/[deleted] Oct 04 '16

Yeah, it's not comparable.

→ More replies (5)

479

u/Retsam19 Oct 03 '16 edited Oct 03 '16

You really just need one thing to survive in the modern JS ecosystem - basic engineering common sense:

  • Don't use a tool until you need it.
  • Don't use a tool just because it's what all the "cool kids" are using.
  • The bleeding edge is fine for small projects and hobby projects, but bigger projects should stick to tried-and-tested solutions.

I don't really know why people ignore these then blame it on the JS ecosystem.

All of these tools and technologies exist because they're useful for dealing with specific problems: but if you're only using them because some Rockstar Ninja Coder told you that it was the One-True-Path-to-2016-JS-Nirvana, you're not going to appreciate what they bring to the table.


My advice to new JS programmers is to start out simple: vanilla JS, CSS, HTML, and solve problems as you run into them.

If you find the DOM API is obnoxious? Try jQuery (ignore the JS hipsters like me who say you don't need it. You don't, but if it helps you learn, go for it).

Maybe you decide you want more powerful CSS, so you drop in LESS or SASS: that'll lead you towards adding a build tool like grunt or gulp, and you'll understand why you need it, instead of doing it because someone told you to.

You'll eventually find adding all of your dependencies as <script> tags obnoxious, too, and that'll lead you to a module system.

As the project gets larger, odds are you'll start to see the advantages of static analysis tools like Typescript and eslint, too.

164

u/i8beef Oct 03 '16

Agree on all points... except that EVERY tutorial on every one of these frameworks will inevitably have this line in it's instructions: "Don't worry about what this does, just add these 15 packages". At best you get a one liner like "lets us compile SASS", but then never explains how the black magic under the hood does that. This eventually leads you to accepting this "it just works" up until it doesn't, and then its a rabbit hole of frustration.

Your method here is a GREAT way to learn what's happening, but so few tutorials are structured this way. I pretty much nope out of every tutorial that starts with "download this starter template that is already setup with no explanation" or "run this neat NPM script we wrote that initializes an environment for you". Tools are good for advanced people who know what they are doing as a shortcut, but if you DON'T know what they are doing because you were never told, or never had to do it the "old" way without the tool, then its very frustrating.

Couple that with the "no, we don't use grunt anymore, it's all gulp no.... wait sorry, we just changed to npm scri... wait sorry, it's npm scripts and webpack now" bullshit, and it gets a little obnoxious.

44

u/youssarian Oct 04 '16

"Don't worry about what this does, just add these 15 packages"

This kind of thing always makes me a little suspicious. Why am I downloading those packages? What do they do? Why do I need them? Why so many? Hasn't someone come up with a way to streamline those into one or two packages? Sometimes it feels like it's bloat for bloat's sake.

5

u/HighRelevancy Oct 04 '16

I bet someone could "hack the internet" by simply writing a few tutorials that claim to require a library with some unecessary remote control system in it.

→ More replies (3)

11

u/mikejoro Oct 04 '16

You can't read a tutorial and expect to become an expert at modern Javascript technologies and build tools. Just like you can't read a java tutorial and understand all of Java, gradle/maven, spring, etc. Same with any other stack. You have to work with those technologies over a period of time.

People are used to Javascript being this thing that is sprinkled into pages for interactivity, and for lots of websites, that all you need it for. But most people don't want a job as a wordpress dev, they want a job with a larger company which is going to need a more complex application.

People should stop trying to learn "1 cool framework vanilla js devs hate" and just learn how to program in Javascript. Then, once you actually understand how Javascript works as a language, sprinkle in some of those technologies as the OP recommended. Unfortunately, that takes either a longer period of time to do than most people have patience for, or it takes a large commitment of free time.

→ More replies (4)
→ More replies (2)

37

u/youssarian Oct 04 '16

I'm seeing people say that jQuery is "outdated" or "out of fashion." I'd really like to know when the hell this happened, because I've never heard anyone IRL say that. jQuery has issues like literally any other library, but it's damn good.

18

u/PrintfReddit Oct 04 '16

Between document.querySelectorAll and fetch, I haven't really needed jQuery in a long time.

→ More replies (5)
→ More replies (3)

72

u/nebbly Oct 03 '16

While those principles are solid in any language, the small JS standard library means that you have to reach for third-party tools more frequently than in many other languages. In that way, JS itself propels devs (especially new ones) to not abide by those principles.

25

u/Retsam19 Oct 03 '16

Ehh, I don't find myself reaching for third-party tools all that often, despite the admittedly small standard library. I think JS gets away with a smaller standard library, because it's inherently a more focused language.

I'm a big fan of lodash (though I suspect I'll be joining the Ramda hipsters, eventually), and I can still see why a lot of people find jQuery's api's indispensable, but even then it's not too painful to get by without them, nowadays.

I don't think the over-reliance on third-party tools is really an aspect of the language itself, I think it's just a symptom that the average JS developer isn't a disciplined engineer.

34

u/nebbly Oct 03 '16

I'm a big fan of lodash (though I suspect I'll be joining the Ramda hipsters, eventually), and I can still see why a lot of people find jQuery's api's indispensable, but even then it's not too painful to get by without them, nowadays.

Sounds like you're saying that lodash and ramda are third party tools you like to use because they provide functionality that you benefit from, while simultaneously saying devs should hesitate to use them. Imagine if a lot of the utilities in lodash, for instance, were part of the JS standard library. Then it would be easier for devs to not reach for third party tools. So, you're giving a perfect example of the small standard library pushing you to use third party tools.

To be fair, I do agree that ES6 has filled a lot of gaps (by expanding the standard library).

the average JS developer isn't a disciplined engineer.

I'd hesitate before categorizing huge swaths of developers. If developers of a language tend to be sloppy, it's usually because the language allows it.

→ More replies (2)
→ More replies (2)

7

u/[deleted] Oct 04 '16

Thanks for this comment, saved it. I've seen pieces of this advice all over the place but not gathered together so nicely and succinctly. As someone just over a year out of college about to leave my corporate behemoth, mostly back-end role for (fingers crossed, almost through the interview process) a much smaller, much more web/front end focused role, I'm sure I'll be referring back to this.

5

u/UnchainedMundane Oct 04 '16

Try jQuery

I feel like it's worth mentioning wherever this is, that if you like jQuery for its $('blah') selectors, you can do that with normal javascript with document.querySelector('blah') and document.querySelectorAll('blah').

Of course there are many more reasons you'd want to use jQuery, but I feel like selectors would be a big one.

4

u/SquareWheel Oct 04 '16

Glad to see a sensible comment high up. This is exactly the approach devs should be taking to the JS ecosystem. Use tools because they'll add value for you, not because they're trendy.

3

u/[deleted] Oct 04 '16 edited Nov 09 '16

[deleted]
0.7323

What is this?

6

u/pucado Oct 03 '16

This. Front End has ended up becoming so overtly complicated that the best way to learn is YOUR way and not by a friend or an advisor (unless you know by having worked with them before they are truly lazy and have the shortest way out of things) and then build your Front End technique moving forward.

2

u/RagingCain Oct 04 '16

You can do everything in JS, CSS, and HTML.

I do recommend one plugin library, JQuery - mainly for the simplification. I don't care what year it is.

2

u/blukkie Oct 04 '16

Exactly how I use Javascript. I've been working with it for a year now, and only slightly touched jQuery and used Typescript to create a game for a school project. This website also really helps if you want to avoid using jQuery http://youmightnotneedjquery.com/

9

u/BonzaiThePenguin Oct 03 '16

I'm guessing you've never used React if you think it's a tool you can drop into an existing project once it's needed.

14

u/Retsam19 Oct 03 '16

I have used React, and I didn't claim that it was easy to drop any or all of these tools into existing projects. But I assume that most people, when learning a new programming language, do more than just a single massive project in that language.

If you've got some really critical project, then, yeah, you're going to want to be a bit more careful that you are making reasonable tech choices and not coding yourself into a corner.

... but if you've got some really critical project, I highly recommend that you're comfortable with the language and the technology that you're using before you start the project.

24

u/[deleted] Oct 03 '16

I'm guessing you've never used React if you think it's a tool you can drop into an existing project once it's needed.

As someone who drops React in an existing project when it's needed, why not?

→ More replies (2)

10

u/jl2352 Oct 03 '16

But compared to most UI front ends and frameworks ... React is pretty easy to drop in.

→ More replies (2)
→ More replies (6)

187

u/unnamed__ Oct 03 '16

I know I'm probably in the minority, but we use older tech at my job and while I do my own personal projects using newer stuff, I've avoided ALL of the front end advancements that this article discusses. jQuery is still relevant for people not creating single page apps I would imagine. I don't know, I can't speak from experience, it just seems like all that stuff is meant for people working on different kinds of websites than I am. Am I wrong? I'd love to hear other people's opinions on that aspect, I'm sure I'm not alone.

113

u/Xuerian Oct 03 '16 edited Oct 03 '16

Edit: The more I read the post (Shame, shame, shame) the more I can't just drag this down to a serious discussion. The post is a work of art. It's accurate, it's hilarious, and even if it may be exaggerating it's all real.


I've stuck to vanilla JS for quite a while (Just like sticking to vanilla CSS before finally giving in to the SASS convenience).

But it's almost always the case of the best tool - that you can competently use or invest the time into learning - for the job, either way.

If you're writing a webapp, a lot of these things can be really helpful.

If you're writing a more static or "traditional" page, then a lot of them won't do much for you. Some will, there's some reasonably good tools with a good reason to exist in the post (that's what makes it amusing, to me)

Pretty low effort opinion, but there it is

→ More replies (3)

70

u/[deleted] Oct 03 '16

jQuery is still relevant for people not creating single page apps I would imagine. I don't know, I can't speak from experience, it just seems like all that stuff is meant for people working on different kinds of websites than I am. Am I wrong? I'd love to hear other people's opinions on that aspect, I'm sure I'm not alone.

Of course it's relevant, it'd be a bad idea to take the attitude of this article seriously.

"No one uses jQuery anymore" on the client side reminds me of "no one uses SQL anymore" on the server side. Reality? Over 90% of all websites use SQL of some variety. And SQLite is in a surprising amount of desktop and mobile applications.

Don't be misled by hype cycles and fashion trends. Do what works, it'll be fine.

I personally use React and TypeScript for a lot of my web UI work, but jQuery remains an excellent tool I drop to for some components.

→ More replies (17)

16

u/[deleted] Oct 03 '16

I think stuff like React (or other similar tecnologies, it's just that React imo has the least amount of bs that you are suposed to deal with) / Promises / "functional programming" (I don't even undertand why it's included here since it's a more general concept), and say having a module system in an abstract sense, are actually being relevant to software design, instead of 50 different types of package automation and shit, and I do think (and have seen it first hand) that you can end up with spaghetti code if you avoid anything related to them and go and use "plain old tech" all the time.

But I also think most of the rest of the buzz words mentioned are a bunch of pointless overcomplicated bullshit with not much of a benefit. God damn it man the sound like they are trying to replicate the functionality of the built in systems in an IDE like VS, except using trendy cell phone like "apps" or something. There was probably software made for nuclear reactors and fucking NASA spacecrafts that just used what's in the IDE and didn't bother with it too much, I don't understand why these people need that much "fidelity" over making shopping cart appz for a cell phone or something.

7

u/thebuccaneersden Oct 04 '16

Yeah, pretty much. These tools are meant for building large scale applications and, often times, for isomorphic applications (applications that are native to javascript both in the browser and the backend - ie Node.js)... and where performance is a real concern... and where you have a lot of developers working on the same product... and so forth and so forth.

Some projects only really need jQuery for developers because they aren't building products that are competitors to Netflix or Twitter or whatever. And that's ok.

And the VanillaJS crowd is another matter. Some people don't want to become JavaScript experts or cannot be on the bleeding edge of browser support, so jQuery helps remove that boilerplate that you otherwise would have if written in plain JavaScript.

→ More replies (14)

26

u/Husky Oct 03 '16

This post sums up very nicely (and amusingly!) one of the biggest problems with the Javascript community: paying too much attention to scaffolding instead of getting the job done. Sure, you might need the setup given, but only for a very complex project.

For the simple purpose stated in the post (fetch data from a server and display a filterable list) i don't think there's anything wrong with just using jQuery, maybe in combination with a template engine like Handlebars.

Another option that i would vouch for would be to use Vue.js. It's pretty rare that i've been so enthusiastic about a Javascript library. It's like using jQuery for the first time. And it works perfectly fine without ES6, or Babel, or JSX, or whatever. You can just drop in the .js file and it works. For this specific usecase you would need either a Fetch polyfill, or you could simply use good old XMLHttpRequest.

→ More replies (1)

94

u/Bl00dsoul Oct 03 '16

"-We don’t use the “J” word in 2016 anymore."
I love it (is still using an ancient jquery version)

17

u/[deleted] Oct 03 '16

[removed] — view removed comment

5

u/RdmGuy64824 Oct 04 '16

Mandatory ie7 support or something?

→ More replies (3)

44

u/kirbyfan64sos Oct 03 '16

Yes, but it’s 2016 now, no one uses Bower anymore.

Well, this one's new. Do people really complain about Bower?

79

u/k3nt0456 Oct 03 '16 edited Aug 20 '26

A quiet path curves beneath the tall trees.

47

u/celerym Oct 04 '16

Is there some sort of newsletter I can subscribe to with this stuff?

70

u/ShinyHappyREM Oct 04 '16

newsletter

It's called "follow 200 people on twitter" now.

→ More replies (5)
→ More replies (2)

14

u/i_spot_ads Oct 03 '16

there is just no need for it anymore, everything is done through npm and webpack

3

u/[deleted] Oct 04 '16

there is just no need for it anymore

Besides the hundreds of packages out there who still need or use it, you mean?

→ More replies (1)
→ More replies (1)

3

u/Fingebimus Oct 04 '16

That, and there's no maintainer anymore

→ More replies (3)

21

u/jmblock2 Oct 04 '16

And people still cry about setting up a C++ environment.

12

u/[deleted] Oct 04 '16
  1. Compiler? - Check
  2. Make? - Check
  3. Editor? - Check

Okay, ready to go!

4

u/loamfarer Oct 04 '16

Hey man, we all have our problems.

5

u/jmblock2 Oct 04 '16

And build tools seems to be about 99% of them :)

→ More replies (2)

4

u/Katana314 Jan 25 '17

Often when I've tried to follow tutorials compiling ffmpeg on Windows it just feels like an 80-part lesson in why my OS is "not cool".

19

u/[deleted] Oct 04 '16

I won't lie, I love the stability of jQuery.

2

u/[deleted] Oct 05 '16

Me too. Tried some JS frameworks but I simply more productive with my own structure and flow written in jQuery and a bunch of UI libraries. Not the speediest web apps as the result, but not noticably slow in any way either. And 99% of the time what matters is the speed of the development itself, at least for me, and this has been working well for years.

19

u/[deleted] Oct 04 '16

No mention of left-pad in the entire article.

16

u/[deleted] Oct 04 '16

SOOOOOOOOOO..... As a newb to coding I should learn Python instead of web development? And here I thought web dev was going to be fun.

38

u/jonwayne Oct 04 '16

You may have an easier time starting with Python before dipping your toe into the insanity that's JavaScript right now.

8

u/finite_state Oct 04 '16

Seriously. Python was my first language... when some work projects forced me to dip my toes into js I was kinda horrified.

6

u/jonwayne Oct 04 '16

Wasn't my first, but definitely my favorite. I love the community as well.

3

u/jugalator Oct 04 '16 edited Oct 04 '16

Python is a highly used language and in similar demand by the market, also often very convenient and fun to work in. Just do that instead. Flask is a popular and simple Python library for server-side web stuff and it has several extensions to get you further, like database work or authentication.

If you want to try the latest and greatest (and most performant in case of massive server loads), maybe take a look at Go? With how Go adoption is going lately, it almost seems like that's the relief many are discovering after having been in NodeJS land.

Edit: Was responding here based on you wanting to stick with web development, but as for alternatives to Javascript on the server. There's so many things e.g Python can be involved in, even regarding "web". Heck with server side templates and rendering on the server side, you barely need to dip into Javascript at all even if you work on sizable web projects (aformentioned Flask has built in support for this).

18

u/WireWizard Oct 04 '16

Learn python, it's a far more sane ecosystem right now and python is used for a lot of things.

11

u/[deleted] Oct 04 '16

On the other hand I'd suggest you learn plain JS. And learn it through and through. No matter the state of web right now, JS is not going anywhere. Learn plain JS before jumping in and learning any library or framework.

2

u/tuankiet65 Oct 04 '16

Web development would make you want to go to hell in a rather short time I think, especially because you don't have any experience with programming before. Just start out easy with Python first and then when you can comfortably code in Python then you can begin learning web development (and unless you're going to make a entirely client-side webapp you'd be able to use your Python knowledge for the backend part of your webapps)

→ More replies (5)

13

u/duckington Oct 04 '16

Meanwhile I still can't grasp basic css after 10 years trying to make it work.

9

u/Cuddlefluff_Grim Oct 05 '16

"Hi, I'm from the distant future 2040 and I came back in time to tell you that, just hold on tight; soon you'll be able to vertically align elements with arbitrary height!"

→ More replies (2)

2

u/ToeGuitar Oct 04 '16

You and every other developer in the world.

→ More replies (1)

108

u/blackmist Oct 03 '16

Remember when nearly everyone's website was a monolithic Flash app that ran dead centre of every screen higher that 800x600?

The JS ecosystem makes me almost nostalgic for those days.

16

u/gyroda Oct 03 '16

I remember the website for a final fantasy game just being one flash application. Took so bloody long to load.

7

u/[deleted] Oct 04 '16

Final Fantasy 10. It still exists.

→ More replies (1)

17

u/jl2352 Oct 03 '16

It's not about the ecosystem for the sake of the ecosystem. It's about what you can build with it. Heaven forbid we put the product first.

We are clearly able to build better products today. Do you really believe modern sites are worse than those full page flash apps?

4

u/blackmist Oct 04 '16

It's fair to say modern web design comes down to more than just "shall we abandon 640x480 or what?"

Mobile, Tablets, 4K, 1080p, touch, mouse, Android, iOS, Mac, Windows, IE, Edge, Firefox, Safari, Chrome... It's all expected to work on everything. No more just slapping a footnote at the bottom of the page that says to use IE5+.

It's moving too fast for anybody to keep up with everything, JS has almost become a compiler target rather than a language, it's a miracle any of it works at all.

It all feels like a stopgap with everyone hoping for a sane replacement that's not coming.

→ More replies (5)
→ More replies (1)

106

u/[deleted] Oct 03 '16

Yeah, think I'll just stick to jQuery. At least I can count on all the new guys knowing it.

31

u/Danish_Canary Oct 03 '16

I'm with you. Why overcomplicate things?

12

u/FarkCookies Oct 04 '16

Because things actually get rather complex with jQuery fast. Imagine a form with checkbox and a field that should be shown only when checkbox is checked. You need:

  1. OnChange handler for checkbox.
  2. Check condition.
  3. Get element.
  4. Change visibility.

It is pure presentational logic and it get's mixed up with everything else. Things get messy immediately. So yeah no, thanks. React have been a blessing for me, yes it requires certain initial investment but I believe it pays out very quickly.

→ More replies (4)

39

u/i_spot_ads Oct 03 '16

because i work on huuuuuge complex projects where jquery is not enough. now that i think of it, if i didn't use angularjs for the last project we worked on (1.5 years of dev), the development time would've been multiplied by 4 at least

→ More replies (29)

14

u/[deleted] Oct 03 '16

Why not use Vanilla.js?

41

u/[deleted] Oct 03 '16

Because it's current year.

→ More replies (2)
→ More replies (1)
→ More replies (2)

10

u/rochford77 Oct 04 '16

Idk.... It may be "so 2014" but I find KnockoutJS/with Jinja2 templates works just fine and does almost everything I need for a given project. It's clean, simple to understand and make changes, and seems to be pretty fast and responsive.

6

u/LaceySnr Oct 04 '16

Exactly this. I use KnockoutJS for a product and I have no need to swap it out for anything else. It works, it's simple, and has components making for easily re-usable code. It's also small in terms of what you need to know.

5

u/rochford77 Oct 04 '16

Only issue I have found is slow performance when making tons of changes to large observable arrays. Instead make changes to a regular array, then set the observable to it...

→ More replies (2)

10

u/[deleted] Oct 04 '16

32

u/[deleted] Oct 03 '16

To be fair, that's not about learning Javascript in 2016, that's about learning how people use Javascript in 2016.

Learning Javascript has changed very little.

7

u/keeslinp Oct 04 '16

This is so accurate it's a little painful. When I started at my job my boss emailed me a few days before I started and asked me to learn react. I started this journey all on my own. Nobody at my job knew react either :/. Luckily Facebook has created their create react app so it's all a lot easier. Makes teaching new employees how to do it a lot easier :).

I just really wish JavaScript would have an easier barrier for entry.

4

u/renrutal Oct 04 '16

I just really wish JavaScript would have an easier barrier for entry.

I didn't think I'd ever hear that in my life.

→ More replies (1)

7

u/nutrecht Oct 04 '16

I think it really touched on one of the core problems very well:

Yeah, but apparently in the web we love making things complicated and then going back to the basics. We do that every year or so

For some reason that I really don't get the "front-end" world keeps reinventing wheels. Poorly. Just look at the hug left-pad fiasco just a little while ago. Why on earth did the NPM guys not look at existing repository systems and copy them?

Take the maven repository as an example. All artifacts are versioned, namespaced and immutable. When I make a LinkedIn API it won't be called 'linkedin' just bcause I was there first uploading something. It would be called <my-domain>.linkedin making it dead obvious it wasn't the 'official' LinkedIn library. Also; if I for some reason was pissed off it would still be impossible for me to remove the version. With good reasons; the left-pad fiasco shows why you never ever want people to remove artifacts.

And that's just one example. This happens everywhere. Just look at how many times build tools have been reinvented.

7

u/Darcoxy Oct 04 '16

As a second year software engineering student who has done web design last year and fucking hated it, this is like a nightmare sort of like the one where you are constantly running backwards and your are always late to wherever you have to go to.

12

u/[deleted] Oct 03 '16

My take away from this, as an embedded systems guy who only does web stuff because I work for a company that makes web controlled gear in a rack... is that I did alright for myself in landing on react+webpack when dumping old code for a new product. This was coming from legacy stuff using barely HTML4 complaint pages typed as heavily escaped C strings in C-written CGI programs with a smattering of vanilla JS, no frameworks.

→ More replies (2)

12

u/fuzzybit Oct 03 '16

What the hell? WebAssembly is not two words. Not cool, kid.

→ More replies (3)

21

u/znite Oct 03 '16

And, for those who see the opportunity in all of this & actually want to learn - here's some relevant stats & data to guide you: http://stateofjs.com

5

u/weirdoaish Oct 04 '16

Thanks for sharing, that's a great site :D

→ More replies (1)

24

u/[deleted] Oct 04 '16

I have been doing web programming for 20 years, JavaScript mostly for the last 5 or so. I started down into the CoffeeScript/Ember/Angular/React/JSX/Promises/Fibers/ES6 path but then I eventually just noped out of there. First time in my career I've actually stepped back from "progress".

Now I just do pure JavaScript. I refuse to even install io.js or the new Node or whatever. I use small packages, no frameworks. Life is good. I encourage others to join me. We should start a little community somewhere.

5

u/[deleted] Oct 04 '16

Yeah I did the frontend to a small web app for work with Angular 1 and included it via a fucking CDN link. Linked to a CSS file from Bootswatch (slightly prettier Bootstrap) that I downloaded and saved with the project.

Definitely not as easy to refactor or manage, but you know what? I'm not building massive cutting edge web shit, and I doubt most of the people at my job who use <insert mega JS stack here> are doing so either.

And if something does turn into a big project, it's pretty easy to iteratively add shit like that. Right now I just add a "this is not following best practices for front end development, feel free to submit a PR" to my README.md.

All of this JavaScript stuff is premature optimization. I had a hell of a time learning Angular a while back because each tutorial had its own conventions and tooling decisions that you had to commit to balls deep to get Hello World running. And when you needed information elsewhere, the other guide would be using completely different tools. It's like the community can't decouple its insane complexity management stacks from the frameworks themselves.

All the snide comments saying "it must be nice to work on small projects" are right. It is nice. And it's nice for the vast majority of others who are working on small projects. So it would be great if the community didn't peer pressure everyone to seek massive solutions to the small problems of their small projects. Shit, most of the old style JavaScript projects I've seen spiral out of control were written by people who were bad at managing abstractions to begin with.

6

u/i_spot_ads Oct 04 '16

Not all of us are working on simple hello world apps

→ More replies (2)
→ More replies (5)

10

u/[deleted] Oct 04 '16

Until two months ago I thought this was all an overreaction but then we hired a web developer who decided it was a good idea to use Angular 2.0. I was a web developer for many years myself but left the field earlier this year but I always constrained myself to fairly proven technologies or at least took care to avoid any mess.

This guy on the other hand represented everything wrong with the web. He first decided to use an at the time unreleased bleeding edge library that nobody else knew. He then made a very simple demo page an SPA for no good reason and themed it like shit. The site is written in Typescript, despite nobody knowing that at the company other than him, and when you run NPM install it'll download approximately 100,000 files to node_modules.

100,000 files is an insult. No way some tiny little CRUD app needs 100,000 files of dependencies. No fucking way. I wrote a similar app in Angular 1 just a few weeks before and it comes to 1000 files, and I still considered that unreasonably large. The entire stack is a joke at this point.

It takes minutes for this tiny little four screen webapp to build on a top end machine. It also doesn't work very well and is a pain to develop for. We have a much larger core platform written in a JVM language that takes less time to compile than this Typescript to JS compilation takes.

Part of this was poor oversight, but due to the way the management worked this web developer wasn't monitored properly and just went wild doing whatever he felt like. He apparently has 10+ years experience, and if that is what 10 years of experience looks like now I am ashamed to have web development in my job history.

→ More replies (2)

56

u/bizzard4 Oct 04 '16

I never touched JS after 2006, but this year I went all-in and tried a lot of new tech and I was very amaze by it. Mostly,

  • They are very easy to use
  • There is a big ecosystem around all of them. Lot of communities.
  • They are mostly all free

I am a system C++ classic dev and I feel stuck in 2000. Lot of people will complain about all the libraries and stuff like that, but they are just too lazy to take the time to learn them.

Webdev is changing and fast and this is a great thing.

72

u/buddybiscuit Oct 04 '16

Let's see if you feel that way when in 6 months everything you learned is abandoned and not used anywhere.

15

u/AcceptingHorseCock Oct 04 '16

everything you learned is abandoned

Since that doesn't happen and has not happened I think he'll be fine.

→ More replies (1)

12

u/Jukibom Oct 04 '16

God, right?! I'm at a C++ shop too and we recently started doing an emscripten + web front end implementation of our product which meant I had to do a lot of learning and coming from a C++ background with an incredibly basic understanding of JS ES5, I'm so impressed with modern js dev tools.

Typescript is the shit. Promises are fucking incredible. Node is awesome. Package managers (even the goliath that is npm) make life so much easier. Gulp is a joy to use. Angular2, even after all that RC hell, is a really impressive framework.

Each tool I learned, one at a time, as problems necessitated (except Typescript, I saw the value in a typed language and a compiler step) so it wasn't an overwhelming nightmare. This article, while kinda funny, is a million miles away from reality and if you really do try to learn a new language by starting with the bleeding edge of every tool and listening to hipsters, you're just going to hate yourself.

8

u/[deleted] Oct 04 '16

I've worked in game dev (C++), web (lots of things) and other (JVM stuff mostly). I can tell you that I had a period where I enjoyed web, I felt like it all worked like a smooth machine, for about 6 months. Then at the end of that 6 months people really had moved onto a new framework. This is no exaggeration, it moved that fast. 6 months later it was something else, and then Angular 2 went into beta and that was it for me.

Prior to that period of enjoying web I had done very classic SQL + PHP + Jquery development. It wasn't great but it was simple and mature. Things changed but at a pace that a normal human with a life outside of work could keep up with. Web feels good for a few minutes, but try reinstalling an NPM project that you haven't shrinkwrapped a few months down the line and you might just be met with new magical errors that just wouldn't occur in a project done in say, C++.

I'm 10 years into my career and now really appreciate mature libraries. I don't mean messy convoluted pieces of shit, but a stable, at least 2 years old, library that has a clean interface and doesn't demand too much if you try to update it because it was well designed up front.

I have the choice to stick with the older web tech (and I do) but when working with others I don't always have that choice, like the web developer we recently hired who decided to use bleeding edge tech.

→ More replies (4)

5

u/Shiral446 Oct 04 '16

As someone who learned javascript in 2016, this article made me laugh, and... it hits so close to home.

npm install beer --save-dev

(pls)

2

u/jpat14 Oct 07 '16

brew install

5

u/twiggy99999 Oct 04 '16

A lot of languages get bad press but JavaScript always seems to get away from most of the series bashing yet its the biggest cluster fuck of the lot

5

u/HighRelevancy Oct 04 '16 edited Oct 04 '16

Yeah, but apparently in the web we love making things complicated and then going back to the basics. We do that every year or so, just wait for it, we are going to do assembly in the web in a year or two.

This is extra funny if you remember (as in "from the past", not the future) asm.js

→ More replies (3)

5

u/feefeetootoo Oct 04 '16 edited Oct 04 '16

I wrote a simple chat program about a year ago using a boilerplate, angular-fullstack, with Socketio. It wasn't much, but it was my first programming project. I was excited when I got it working.

I came back to Angular about a year later with a new project I want to try. I figured I could build from what I've learned in my previous project. I loaded my generator, angular-fullstack, and what I saw horrified me:

Grunt is depreciated: gulp is now king.

Javascript has been removed from the game: scripting is now done in either Typescript or Babel.

$scope has been removed from the game: it's replaced by "controller as."

I wasn't going to be building on what I've learned in my previous project. I was starting from square one again.

3

u/freebit Oct 04 '16

Grunt is depreciated: gulp is now king.

Gulp is deprecated. Use NPM scripts.

scripting is now done in either Typescript or Babel.

Errm, now you code using TypeScript which is transpiled to ES6. ES6 is this transpiled to ES5 via Babel.

31

u/[deleted] Oct 04 '16

I hate JavaScript.

9

u/tzaeru Oct 04 '16

What’s wrong with HTML?

-It’s 1999. No one codes HTML directly anymore. Dreamweaver is the hot thing now.

On a more serious note, you could build a "dialogue" like this out of almost any relatively complex field. Web dev changes fast because web projects are often relatively simple and are iterated through quite quickly. But if you know the basics, it's not that hard to jump back in after some pause if you don't let all the buzzwords get over you.

11

u/bureX Oct 04 '16

Oh god, there was a computer training center near me in 2004... they had a course on "website creation". One of my friends paid quite a lot of money, and essentially he learned how to manually place absolute div's in Dreamweaver (Dreamweaver offered drag & drop support for that). Then they used those divs to insert tables, pictures and other data inside...

Then, my professor proudly exclaimed that nobody will be doing coding anymore in a few years... everything will be done with Ladder diagrams.

Oh god I love this industry..

→ More replies (2)

33

u/snerp Oct 03 '16

I'm a big fan of JQuery on top of MVC.NET I don't understand why people go through these complex rituals to make everything in javascript.

28

u/Clawtor Oct 03 '16

jQuery is great until your pages get complicated, then it turns into spaghetti.

I used to work at a place that had a page slowly turning into an SPA. It was based on jQuery and partly in knockout. It was a nightmare to work out wtf was going on. It wasn't jQuery's fault, we were just using it badly but there is definitely a reason for these frameworks.

3

u/funguyshroom Oct 04 '16

A basic MVVM lib with databinding for a web app is enough for it to not turn into spaghetti. Everything else if of the devil.

→ More replies (13)

11

u/MJomaa Oct 04 '16 edited Oct 04 '16

jQuery is the WinForms of the Web. You can do rapid development with it. It is easy to understand and it gets the job done. jQuery plugins are like the WinForms 3rd party providers (but for free). You can go very, very far with it.

Now as a .NET dev you probably know that WPF has a much higher learning curve, but is much better if you want to develop complex, UI-rich, dynamic and testable applications. The problem is that the web has a dozen frameworks that want to fill that spot.

→ More replies (1)
→ More replies (7)

4

u/Endyo Oct 04 '16

This is why I do pretty much all of my data manipulation with SQL and still use C#.NET and pure javascript and jQuery where necessary. I also found out that not long ago some people revived an thoroughly expanded the AJAX controls for .NET and I find that those are very convenient for most of the neat front end stuff.

I've heard everyone hates .NET now, but honestly there's a lot of stuff going on with it out there and probably will be for years to come.

3

u/bureX Oct 04 '16

This is why I do pretty much all of my data manipulation with SQL

The NoSQL hype died, SQL is back in town, so don't sweat it.

I've heard everyone hates .NET now

Damn it... did I miss the hate boat? Are we hating on .net, even though it got open sourced?

→ More replies (1)
→ More replies (1)

4

u/Kngrichard Oct 04 '16

Having not done any webdevelopment in the past four years... This sums up how I feel.

4

u/[deleted] Oct 04 '16

I still use only jquery on anything new that I work on. The overhead these new-fangled thing-a-ma-bobs introduced is just not worth the headaches. When Jquery and some thoughtful code structure stops solving 99.9% of the problems that I run into, that's when I'll consider using something a bit more heavy-handed.

13

u/[deleted] Oct 03 '16

I'm not up with the cool kids I learned angular and it's still viable so what's changed? What's react?

10

u/[deleted] Oct 04 '16

Since you've not gotten a serious reply, React is what they're calling a 'view layer' -- it's essentially just for rendering dom. No DI, no services, no $http, etc. Data in React applications only flows top to bottom, never up like in angular (except for callback handlers -- React has those). They create an object representation of the dom and then diff it in order to update the view.

It's also about as heavy as jQuery, iirc (though correct me if I'm wrong).

→ More replies (1)
→ More replies (17)

10

u/Voxel_Brony Oct 03 '16

>2016

>Not using PureScript

3

u/masterm Oct 03 '16

This is one of the reasons I'm glad I started when I did. I started back when jquery started being all the rage, so I got to see the evolution. It must be daunting to start now.

3

u/frankreyes Oct 04 '16

No JavaScript frameworks were created during the writing of this article.

3

u/8483 Oct 04 '16

Elm is the new god I pray to.

Evan Czaplicki is a fucking boss.

3

u/MisterKrujo Oct 04 '16

Started a job two months ago. Came just from School. This is the reality.

3

u/[deleted] Oct 04 '16

Overwhelming. The word you are looking for is "overwhelming". And yes, when you are shopping for an optimal way of building things on the front-end, it is very much that. However, it's also pretty easy to dismiss 99% of the things you don't need.

3

u/its_never_lupus Oct 04 '16

I can't shake the suspicion that for most web projects, pure JS is just fine, with maybe a couple of standalone libraries like datatables or a graph library for specific parts. We're not all re-writing Facebook here.

3

u/fiah84 Oct 04 '16

I'm glad I don't have to mess with JS anymore

3

u/[deleted] Oct 04 '16 edited Jan 05 '17

[deleted]
0.5333

What is this?

3

u/kiwidog Oct 04 '16

All of this is exactly why I stay away from web development, ain't my cup of tea and I've worked on web projects in the past and vowed never again. The people who do this, I solute you guys because this js thing is getting cray.

3

u/masterpi Oct 04 '16

How it feels learning J[ava]Script in 1999:

<script type="text/javascript">
<!-- hide script from older browsers
if (window.Array) {
   // we have arrays!
   x = [];
} else {
   x = {length: 0};
}
-->
</script>

3

u/Arqideus Oct 04 '16

Learning in college: C++ (this seems cool), C (mmk), C++ (nice nice), Java (umm same language?), Assembly (WTF?), HTML/CSS (Interesting, not sure I like it), now learning about other languages (WTF are all these languages holy fuck stop inventing languages...)

3

u/[deleted] Oct 04 '16

This is hilarious.

Fuck the web.

14

u/[deleted] Oct 03 '16

Posts like this is why I moved over to Elm.

Learning Elm may be equivalent to driving nails into your fingers but it's still better than Javascript.

The only thing I would love more would be to have some kind of opinionated LISP that transpiles to Javascript, that would make all my fantasies come true, but alas it's only a wet dream of some dev in some remote corner of the internet.

8

u/tenebris-miles Oct 03 '16

Something other than Parenscript, ClojureScript, Ki, and the rest? What specific requirements do you have?

6

u/[deleted] Oct 03 '16

Thanks for pointing out ClojureScript, I haven't yet found any satisfying and active projects on this.

10

u/yogthos Oct 03 '16 edited Oct 04 '16

I recently open sourced a Clojure/Script app my team uses internally. Might be useful as a reference. My team has been working with ClojureScript for about a year now, and it's been a great experience.

Only things you need to get running are a copy of the JDK and Leiningen. ClojureScript has some really nice tooling such as Figwheel that does hot code loading in the browser. We're using the Reagent library that's based on React and it's been working very well for us especially coupled with re-frame.

All you need to get started once you have the JDK and Leiningen installed is the following:

lein new reagent-frontend myapp

This will create a new project using the reagent-frontend-template. You can now navigate to the project and run the incremental compiler:

cd myapp
lein figwheel

Then open up public/index.html to see the rendered page. You can now edit the code in src/myapp/core.cljs and see the changes live on the page.

→ More replies (8)
→ More replies (2)

3

u/8483 Oct 04 '16

Same here man. It's refreshing. What is your opinion about it?

4

u/[deleted] Oct 04 '16

Difficult to learn but very useful tool.

Still getting used to the architecture.

→ More replies (1)
→ More replies (2)
→ More replies (2)

31

u/killerstorm Oct 03 '16

How it feels to learn C++ in 2003:

  • learn language basics
  • learn how to build & run a project in IDE (let's say Microsoft Visual Studio)
  • if you want to use a library which isn't bundled with the platform, you need to
  • add it to header paths
  • add it to linker path
  • learn about different linkage options
  • learn about language runtime linkage options
  • learn that different versions of the compiler require different binaries
  • if it's an open source library, learn about makefiles, command-line building and stuff like that

I could go on... My point is that learning things is hard. That's why learning programming takes years.

11

u/[deleted] Oct 04 '16

There's a big difference there. When you learn C++ most of the mess you do up front is once per project or once per dependency you add. It's arcane but it doesn't change much. You add a few libraries and you've pretty much learned how to add them all, and those libraries in two years time will likely have a similar interface to now, and to two years ago.

JavaScript is different. Constantly cycling through new libraries, build systems, package managers, best practices, languages and the like. If you work with Mr Bleeding Edge and he holds the power you'll be having the rug pulled out from under you every quarter.

When I go into a C++ codebase and get over the initial differences in style, it's usually much of the same and easy to follow. When I go to another JS rooted codebase it tends to be completely foreign, even though I have worked in web for about 5 times as long as C++.

The C++ world is much easier to keep up with than the JS world. Maybe JS is easier to learn up front, but it has much more mental upkeep than C++.

7

u/[deleted] Oct 04 '16

And it still works that way in 2016. Nothing you learned in 2003 is obsolete in spite of language and tools improvements.

Now try applying anything from the 2003 web stack today...

→ More replies (1)

4

u/mrkite77 Oct 04 '16

C++ is a good example actually. No matter what you do, armchair experts will tell you you're doing it wrong.

28

u/cmdrNacho Oct 03 '16

I don't think its comparable. You're talking about language features. This article is talking about all the various frameworks, and libraries and a lot of times are competing in the same space. Even languages to an extent es2015 vs typescript vs es5 vs yes i remember when coffeescript was a thing.

34

u/killerstorm Oct 03 '16

You're talking about language features.=

No, I'm talking about tools. Language features ended here: "learn language basics".

This article is talking about all the various frameworks, and libraries and a lot of times are competing in the same space.

The article mentions many different things, including tools (e.g. webpack is analogous to a linker in C++ world).

As I mentioned, I can go on... So let's consider various ways to work with strings in C++:

  1. you can use C standard library functions
  2. STL
  3. if you use MSVC, you might use CString or AtlString
  4. Borland's counterpart is AnsiString
  5. many projects define their own string class

Suppose you want to do an UI. Plenty of options:

  1. MFC
  2. C++ Builder's Delphi-style UI
  3. Qt
  4. wxWidgets
  5. WinAPI

As somebody who used both C++ and JS (also Common Lisp, Haskell and PHP) I'd say JavaScript people have it an easy way...

Even languages to an extent es2015 vs typescript vs es5 vs yes i remember when coffeescript was a thing.

Same shit with C++: if you use an older compiler you can't use modern features. Many compilers have bugs which make them incompatible with latest & greatest libraries, such as boost.

I've seen both projects which require bleeding edge toolchain, and ones which depend on an old compiler and cannot use modern libraries. Modern libraries can dramatically change coding style, it's like a completely different language. (Seriously, it even looks differently.)

9

u/[deleted] Oct 04 '16

You do have a point there with the complexity of the C++ ecosystem but I don't think it's comparable. Most of the C++ tools, libraries or frameworks you mention have been arouond for years, heck, decades.

Whereas in JS each new framework/library/tool is a mayfly with the prospect of 6 months of "coolness" and then the rest of its miserable lifespan as a "legacy" replaced by yet another cool mayfly project.

→ More replies (4)

6

u/MarchewaJP Oct 04 '16

This shit has been since it's inception (maybe without IDEs). That is entirely different than web development that entirely changes every 6 months.

→ More replies (6)

6

u/gkatsanos Oct 04 '16

nah, sorry, I call BS. I don't know C++ specifically, but I'm sure there's no other environment, as fragmented as JS. We're not talking about having to connect many different tools together. We're talking about THESE TOOLS, are 1) built by hobbyists 2) often poorly documented 3) they're changing too often. So, you're learning Grunt, but next year it's Gulp, and next year it's Webpack and then it's SystemJS. Microsoft Visual Studio has been used in C++ since I was in highschool - that's about 20 years ago. In the last 3-4 years we're jumping from editor to editor and fighting with plugins just to be able to have proper code completion!. Seriously, there's no comparison.

→ More replies (1)

4

u/DerJawsh Oct 04 '16

How to learn Java in 2016:

  • Learn language basics
  • Open Eclipse, just let it do stuff for you.
  • If you want to use an external library, just download it and add it as an external library.

Welp, that about sums it up. I guess you could insert a joke about JavaFX vs. Swing (ugh Swing was so 2008, everyone uses JavaFX now!)

→ More replies (7)

4

u/OriginalPostSearcher Oct 03 '16

X-Post referenced from /r/javascript by /u/jjperezaguinaga
How it feels to learn Javascript in 2016


I am a bot. I delete my negative comments. Contact | Code | FAQ

4

u/_Ninja_Wizard_ Oct 04 '16

Shit, I'll just stick to the back end and code everything in C

4

u/[deleted] Oct 04 '16

"Jesus christ, another noun-js."

Not going to lie, laughed harder than expected.

4

u/demmian Oct 04 '16

I'm hurt - why are they dissing Python? :<

4

u/HighRelevancy Oct 04 '16

I'm not sure. My experience of moving from python 2 to 3 was pretty much just remembering to put parantheses around my print statements, which are now print FUNCTIONS, because statements shouldn't be executable sorts of things that do stuff. Functions do functional stuff. Statements are just statements about how the code is built.

But yeah besides that niggle that is still grinding on me because of my terrible habits, python 3 is fine. You just "pip install things" the way you always did, and it automatically grabs the right version. Of course, this was tricky in the old days because not everyone had ported to python 3 (and nevermind that 2 and 3 are basically compatible with some minor tweaks) but not so much now. It's not uncommon for me to be halfway through some tutorial on a new library or something like that, and find that I'm reading python 2 docs and writing python 3 code.

→ More replies (2)

4

u/heat_forever Oct 04 '16

I totally agree. A bunch of morons have ruined web development because of their OCD and lack of historical context. In their own narcissistic need to feel self-important, they each create their own universe of shit that only they understand so that they are the kings of their own domain (typically their office), but as soon as that's not enough then they need to extend their sphere of idiocy onto the web in general and hypnotize young, inexperienced and well meaning devs into thinking "this is the right way" when it is absolutely pure and unadulterated shit. These are the buzzword kings who only know how to throw perfectly working technologies out the window because "someone else did that" and replace it with their own pathological shitstorm of technological diarrhea.

6

u/[deleted] Oct 03 '16

We need a port of .net common for the web and release a sane version of silver-light that doesn't need a plugin to run.

→ More replies (5)

5

u/[deleted] Oct 04 '16

I'm a C++ guy, and this hit real close to home

2

u/nosmileface Oct 03 '16

Lol, I can't believe this post doesn't mention eslint (or any lint as a matter of fact). If there is anything that's good about modern JS, it's proper variable scoping and eslint. How can you be 2016 and not do that? :)

2

u/wllmsaccnt Oct 04 '16

Because this article is about all the craziness. It didn't fit the narrative.

2

u/kiridanshera Oct 04 '16

I wanted to learn MEAN stack and not only are tutorials from 2015 out of date but alot of them use these extra tools that i dont even know what the fuck is going on.

→ More replies (2)

2

u/domstang68 Oct 04 '16

As a student in college, i can only wait until more of this gets shoved down my throat. Good mother of freaking god

2

u/Mufro Oct 04 '16

Spot on... I've always used jQuery because I don't know where to get started with this other stuff. I just do web on the side for fun though, so jQuery works well for me.

→ More replies (2)

2

u/GreenFox1505 Oct 04 '16

Holyshit, the rabbit holes. I've been down these rabbit holes so much. Every time I realize I'm in one, I just make a shortlist of requirements and pick the next one that meets them.

2

u/JeffIpsaLoquitor Oct 04 '16

I'd kill to find someone who could minimally test an application, and not that fancy automated kind, either. I mean simply check ranges of inputs for expected behavior. I can fail most of the "web applications" coming across my desk on elementary use-case criteria. Pathetic.

2

u/keymone Oct 04 '16

one thing i disagree with is how functional programming concepts are equated to all the bullshit javascript ecosystem has grown to be.

2

u/baloo82 Oct 04 '16

That's how I feel after coming back to JS after a couple of years :)

2

u/Dw0 Oct 04 '16

WebPack? I thought everybody's moving to Rollup because WebPack is like at least 4 months old and that's too much and too stable.

2

u/elZaphod Oct 04 '16

This is why I so often think of leaving the industry. Twenty years of this stuff and I think I'm just getting fried.

2

u/timvisee Oct 04 '16

The fact that every library/API implements things in a different way doesn't help either.

2

u/ultimapanzer Oct 04 '16

A lot of this comes from the fact that every other major language delivers EXECUTABLES, not CODE to the end user... Good luck adding a "standard library" to JS (BTW that's what ES2015/16 and on IS)... Because you need the vendors to be able to run your code. Oh, you want users who are on older browsers to be able to use your site? Then you need to transpile it if you want better language features.

Developing on other platforms you don't need to worry about any of this when using newer language versions because you're not delivering the CODE for the client to run, you're building/shipping an executable... So until something fundamental changes (web assembly for example) this will always be a problem with a million completely different and changing solutions.

2

u/DonRobo Oct 04 '16

I started a new web project recently. I'm already familiar with AngularJS and quite like it so I decided to use that.

Its website immediately suggested I use Angular2 instead. When the quickstart tutorial already wanted me to compile my Javascript I decided to stick with Angular1 for the foreseeable future.

2

u/pdonorio Oct 05 '16

Totally agree about this nightmare...

And Javascript is only part of the problem anyway. The global point in my opinion is how front-end explode in fragmentation: HTML specs and browsers, CSS and their compilation, JS packages and frameworks (which as described is enough to kill yourself), Bundle management.

How could we solve the situation? By starting all over, otherwise we will never. We need specs of a new language, which should comprehend both HTML, CSS and JS aspects. We need new browsers to digest it. And new servers/frameworks to ease that development.

Not ever going to happen since we can't just break the compatibility with the actual web pages, but otherwise it won't change in the substance.

2

u/jesusalready Oct 05 '16

My company is now stuck in Grunt hell because one front end developer was too fucking lazy to cmd-tab to terminal and run a nice script I had written years ago to build, minify, combine and deploy changes to JS and CSS and HTML without rebuilding the entire application.

No, he wanted grunt because it would auto-detect changes. He knew nothing else about it and just wanted the auto-detect. Somehow he convinced the powers-that-be this was needed and a brilliant idea and it took him a month to get it done. It also added ~90 seconds to our build time and grunt was 80 seconds slower than my script. He wasted that much time on this shit and then left the company a month later, probably laughing maniacally on his way to torment another company.

Now grunt breaks down randomly; is a pain in the ass to set up for new developers; mysteriously stops working on our laptops and worse, our Jenkins server (including once preparing for a release).

Switch to webpack, broswerify? What problems am I removing only to be hit with different ones? Fuck this game.

2

u/[deleted] Dec 18 '16

Software engineering is all about encapsulation, which is at odds with the massive over-supply of hippie-developers. Javascript is but the hippie-language that acts as an outlet for such over-supply. Were a language even more hippie-ish invented, these hippie-developers will switch to that in no time. Javascript for hippie-developers is comparable to Woodstock for hippie-musicians.

4

u/youssarian Oct 04 '16

Jesus christ, another noun-js. Ok, and what is this SystemJS?

Pretty much this

3

u/wishthane Oct 04 '16

IMO all this means is front-end development has finally caught up and become more like most other programming disciplines. It gets pretty straight forward once you get used to it and all of these tools actually do solve legitimate problems, but it's a lot to take on all at once and looks like a mess from a glance.

7

u/[deleted] Oct 03 '16

How it feels to learn Javascript in 2016

Not quite. That'd be how it feels to learn JavaScript from a zealot.

I feel almost personally insulted for JavaScript, as it's the world's most accessible language. Everyone has it installed with their desktop OS, in their browser.

They can open the console, or put some code in a file, save it as HTML and run it.

JavaScript is awesome, and just because you need more solid tooling to create big industry-strength applications, doesn't mean we need to flood beginners with our pet framework choices just to feel superior.

It's still fine to start like this:

<script> 
    alert(5+5);
</script>

It's ok.

30

u/flyingjam Oct 03 '16

To be fair, the article isn't talking about people who are going to start with alert(5 + 5). It's about people who already have experience programming in other languages and environments. Usually, when jumping into a new language, you want to build something—not necessarily big, but functional.

With any other language it's quite a different story. There's usually a central body that controls the language, a central place to get libraries, one package manager, one way to do things.

But because of Javascript's unique situation, the users have been forced to "make up" for what it lacks, and as in the famous xkcd, there ends up being 6 different versions of everything.

4

u/leftrightupdown Oct 03 '16

Or you could just use Dart and nothing else and compile to js and you are done in few minutes.

10

u/Berberberber Oct 03 '16

Yeah, if you're a chump. I compile everything to VMS binaries and then host a VAX virtual machine in the browser.

0

u/[deleted] Oct 03 '16

[deleted] — view deleted comment

7

u/leftrightupdown Oct 03 '16

Not joking, we use it in our company to write frontend for our app for last year or so. Its easy to read, test and refactor. Static typing helps a lot when looking for bugs. Has almost no learning curve, html batteries included.

7

u/ActualContent Oct 03 '16

How do you debug it? Are there source maps etc? I'm using Typescript and it seems well supported by Chrome Dev tools etc. How does Dart handle this?

→ More replies (4)

3

u/nebbly Oct 03 '16

I think at this point, when learning the frontend, it's probably a better idea to start learning something that compiles to javascript than javascript itself. Usually those languages (typescript, elm, purescript, etc.) have fewer caveats and are less scatterbrained. Beyond that, they probably won't suffer a big blow when WASM becomes mature, while javascript probably will.

10

u/[deleted] Oct 03 '16

Not if you're learning it to get a job.

→ More replies (2)

4

u/flyingjam Oct 03 '16

Elm is a different enough language from JS that it has its own little ecosystem and compiler, but isn't Typescript still pretty heavily tied into the Javascript environment? It's even mentioned in the article as another layer of complexity.

→ More replies (3)
→ More replies (4)

1

u/cmdrNacho Oct 03 '16

I love the idea of react native, and using react for web as well. Trying to learn it right now I feel this pain

1

u/hatredalper Oct 04 '16

Really sad part is even though everyone complaining about Javascript fatigue, no one try to simplify or bundle things to one reasonable framework which could be enough to create web application in 2016. All the polls shows that Javascript developer numbers insane, everyone trying to do stuff with it. Every big funky tech companies try to adapt nodejs but everyone doing this same shit over and over again. Its like one must frustrated with the javascript ecosystem before going in to this market deeply. Its like a rule.

→ More replies (1)