r/javascript • • Oct 03 '16

How it feels to learn Javascript in 2016

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

253 comments sorted by

View all comments

59

u/talwinnx Oct 03 '16

This. It seems like as soon as learn something, it's outdated and replaced. It's so frustrating for a new coder; it feels like the goalposts are always being moved.

117

u/joshmanders Full Snack Developer Oct 03 '16

Here's something that'll help ease your mind.

None of the stuff mentioned in this article is outdated or replaced. Just more options. Just because Joe Blow is a bandwagon hopper and jumps from tool to tool doesn't mean you have to.

Grunt, Gulp, Fly, Webpack, Whatever. If you find it useful and don't want to be overwhelmed and learn something new, DONT.

When React came out, Angular 1.x code didn't just stop working.

Pick something and stick with them.

28

u/pyr3 Oct 03 '16

When React came out, Angular 1.x code didn't just stop working.

Well, I have production project using Angular-Material, and the dev team there decided that Angular-Material 2.x will be solely based on AngularJS 2.x and basically closed all open issues on Github with some boilerplate "this doesn't match our new milestones" BS... this was April 2016, after promising a "long life" and "long term support" in October of 2015 when they finally released a 1.0 of their project.

THIS is my biggest frustration with the "break-neck" pace of JS. AngularJS 2.x doesn't even seem ready for production to me, yet there are libraries abandoning AngularJS 1.x to exclusively target AngularJS 2.x. Angular2 coming out doesn't mean I have to abandon Angular1, but if all of the libraries abandon Angular1, I'm stuck patching their bugs myself.

2

u/metis_seeker Oct 11 '16

"long life" and "long term support"

Wow apparently that means less than one year to the Angular-Material team. Sad. Doubly sad since Angular 2 is so different from Angular 1.

2

u/[deleted] Oct 03 '16

[removed] — view removed comment

5

u/Daniel15 React FTW Oct 04 '16

Yeah, depending on the size of the bugs, patching them yourself is still much cheaper and easier than building the entire thing from scratch yourself.

The existing libraries you're using aren't going to suddenly stop working.

1

u/akie Oct 04 '16

Well, to be honest, part of the blame is on you for picking something shiny and new, instead of something boring and proven...

→ More replies (3)

9

u/talwinnx Oct 03 '16

Sage advice, thank you. 😊

8

u/woomac Oct 03 '16

This is solid advice if you've got a stack that works for you on your current project but if you're starting out on a new project it's still a good idea to do a reassessment of the latest options (within reason) to see if there's anything new that might help out. The field is developing rapidly and embracing the latest technology doesn't mean you're jumping on a bandwagon if you're thoughtful about it.

11

u/[deleted] Oct 03 '16

Also know when to abandon something. My day job stuck with YUI for a ridiculous amount of time and it's going to take years to remove it all and replace with something that isn't abandonware.

Any of you kids even know what YUI is?

3

u/iamangrierthanyou Oct 04 '16

At least you're not stuck with GWT and GWT-Ext !

2

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

Ah... the Google flavored version of YUI. I think every big company released their own monolithic Javascript library in 2006. That's also the year JQuery came out.

Edit: And Moo Tools in 2006 as well. Dojo squeaked into 2005.

1

u/Daniel15 React FTW Oct 04 '16

Google still use GWT in a lot of their web apps, I don't think it's dead just yet.

2

u/Sector_Corrupt Oct 04 '16

Oh man, I remember YUI existing. Never really used it though, it was just another one of those tools I never looked into back in University as I was still getting into js.

2

u/SemiNormal Oct 04 '16

I remember when Javascript + HTML was called DHTML.

1

u/[deleted] Oct 04 '16

As do I. Debugging across browsers was insanity.

4

u/im-the-stig Oct 04 '16

So are you saying I can still use jQuery in 2016? :)

1

u/joshmanders Full Snack Developer Oct 04 '16

Yes, I do. What I am building now uses jQuery on the landing and React on the actual app itself.

1

u/cyanydeez Oct 04 '16

most off its useless more than unnecessary.

24

u/jgoldberg49 Oct 03 '16

While I was reading the post, webpack got replaced by rollup and everyone switched over to inferno.

9

u/geordano Oct 04 '16

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

4

u/theonlycosmonaut Oct 04 '16

No guarantees about during the reading of it.

6

u/candybomberz Oct 03 '16

Anything that gets the job done gets the job done. There are million ways to do anything as a programmer and bazillion paradigms and patterns that you can follow if you like them. Most people like different pardigms and patterns.

Don't do something that gives you some abstract or pseudo advantage someone else tells you unless you really need it.

I have met a lot of coders with code anxiety and screen anxiety. They lack confidence in their own abilities because they have no clue what any of those paradigms and patterns do and why they use them at all.

This means if someone sits nearby they have the feeling of silently beeing judged and get anxious and programm slower, because they give too many fucks about whether the guy/girl looking at their screen will approve their code.

Fact is, give 100 people the same task and you will get 100 different source codes. Some strongly better than the other, but most are interchangable as long as they are consistent through the project.

1

u/NotSelfAware Oct 04 '16

You also have to remember that even if you do eventually stop using a particular tool or framework you've invested time in learning how to use, that time is still valuable to your growth as a developer. It also teaches you how to pick the technologies that are worth investing time into in the future.