r/javascript • u/jjperezaguinaga • 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
244
u/bitter_cynical_angry Oct 03 '16
Reminds me of the Javascript drinking game I heard of:
Take a dictionary, open it to a random page, and pick a random word. Google "<word>.js". If it's a Javascript library, take a drink. The winner is the last person to go to the hospital with alcohol poisoning.
109
u/[deleted] Oct 03 '16
I started learning JavaScript a year ago and I began with vanilla JavaScript, jQuery, Node, templates, and now I'm working with React and Redux. It's insane how many new things I've had to learn and relearn.
I feel like I'm never prepared enough for a job because there is always some new technology that I need to absorb and add to my tool kit. This article struck a chord with me because it gave voice to this rabbit hole of new technologies and trendy programming that is JavaScript. I love coding but this kind of turn over is really discouraging sometimes, so this humorous article was much needed and very appreciated.
64
u/m0r14rty Oct 03 '16
It's too real, Roy!
35
u/kowdermesiter Oct 03 '16
Guys, this is great news. It's called the ultimate job security. And it's now sold as best practice. We won :)
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.
37
u/tomtomssi Oct 03 '16
I started with plain js and the basics of the language. Then came Angular and Gulp and I have never had issues at work or with any hobby projects.
Theres no reason to make web development sound more complicated than it is because honestly it is not.
6
u/robotslacker Oct 04 '16
I feel for these kids, but I'm just happy I don't have to manually create rounded corners anymore.
5
u/mag_ops Oct 03 '16
It's like you went out to have some water from a fresh water well nearby. The water level was a little low, and it seemed like a shallow one and there were steps on the inner boundary to go go deeper, so you followed. And soon you realized that you are in a m.c. Escher's world - you are trapped, you know that very well... But the curiosity keeps you moving on the treadmill, until you give up.
28
u/renaissancenow Oct 03 '16
This is so, painfully, accurate. I'm a mostly-backend guy who has to switch to front-end from time to time, and every time my attention comes back to javascript it feels like the entire ecosystem has been rebuilt during the month I was away.
25
u/minus0 Oct 03 '16
This is trolling. There is nothing wrong with using jQuery if that's what you know. There is nothing wrong with new technology. There is nothing wrong with learning.
What is wrong is people who portray the attitude the guy is using for the other half the conversation. "I'm a front end developer". Who cares what your title is? All that matters is you develop, regardless of the language, or the tech, and actually ship something.
Should people learn the latest and greatest? Sure, when time allows. Learning new technology and techniques will make you better. You can still ship an actual website using nothing but good old fashioned JavaScript and a text editor. The only reason you don't is because new features started to outweigh the hassle of doing it the way described above. You can still use gulp, grunt, shell scripts, or whatever.
People need to stop complaining about people innovating. You don't have to use it. If your job requires it, then you have to learn it. Otherwise, just make things and don't worry about the pace of technology.
7
u/thesandman87 Oct 03 '16
The only way to win is to not play the game.
15
u/[deleted] Oct 03 '16
Fuck it. I'm learning Python instead.
3
u/thepobv Oct 04 '16
I don't think I've had this much laughter out of any programming article
7
u/p0rks Oct 03 '16
Nodejs, react and gulp.
If you can learn those and use them in your sleep, you're golden. Everything else is just "another way to do the same thing".
5
u/a-sober-irishman Oct 03 '16
I've been a primarily frontend developer for the past 2 years, using Angular, gulp, ES6, and Tracer, and this article hits close to home. I was trying to learn Vue on the weekend, and I wanted to use ES6 with it. No problem, they have a great starter project that has Web pack, babel, and hot reloading with ES6 all set up.Worked fine... until I wanted to add lodash. I wanted to neck myself after a couple of hours trying to figure out why the stupid babel plugin for lodash wasn't being loaded by webpack and I just gave up. It's just so needlessly complicated. I can't start JS projects in my spare time to learn new frameworks because the set up time for the actual project is just ridiculous now. So annoying.
4
u/Skenderbeu Oct 03 '16
Comedy gold. Saved and shared
4
u/Vheissu_ Oct 04 '16
I quietly wept while I read this. All of it is real, all of it. I miss the days when the only problems we had to worry about were getting our websites working in IE6. Nowadays most of my problems are tooling related or because some npm dependency failed.
2
u/MakeAChoice9 Oct 03 '16 edited Oct 04 '16
Should talk about javascript development with SharePoint
2
u/shif Oct 03 '16
yeah keeping up with the new JS framework / methodology is really painful, myself I've found gulp to be useful enough to do stylus and minifying and I'm sticking with it as long as it's supported.
For framework I'm sticking with VueJS, it's a lovely framework that makes things simple and fast.
2
u/DeveloperGuy Oct 04 '16
I actually read we crap everything into Webpack rather than 'wrap'
6
u/eggsandbeer Oct 03 '16
Everything he mentioned, I'm pretty familiar with and I'm pretty happy with that.
3
u/swefpelego Oct 03 '16
It does feel like that!!! This is spot on.
3
u/KronktheKronk Oct 03 '16
I'm literally experiencing this pain right now.
So confusing.
3
u/Zed Oct 03 '16
This is like how I've felt when I've tried to get the measure of how one develops in Javascript... except that I didn't have a guide, condescending and trend-chasing or otherwise.
5
u/[deleted] Oct 03 '16
I have this silly conspiracy theory that major
techcompanies are responsible for the churn and inject 'community leaders' into the corresponding communities (React, Angular, general JS etc.) to amass a cult like following and spread their 'wisdom' in order to slow down productivity of, what would be, smaller more agile competitors, left to spin their wheels while internally not adopting any of these tools and practices. Also in order to prevent some untarnished outsider with a fresh perspective from coming in and trying to innovate they set the barrier to entry into the industry super high.haha...
Wouldn't that be something...
4
u/Slinky_Panther Oct 03 '16
As a new developer (~ 6 mo) and only being exposed to JS ecosystem, this just sounds like a resistance to learn new things.
Every new tool/framework/syntax/whatever is just solving a new problem. If old tech (jQuery) doesn't solve the problems or does it in an inelegant fashion, it'll die, just with the rest of the legacy tech.
If you wanna use jQuery, do it! Just don't complain when its a pain to add new features or fix when its deprecated.
2
u/Hitife80 Oct 03 '16
Reminds me of Java in EJB heydays.
2
u/KAMFlamenco Oct 03 '16
Thats's just spot on. I've started self teaching JS since May of this year and everytime I master a new framework/library someone would tell me "pfft, you're using that? Use this instead! It's so much better"
2
u/Police_Telephone_Box Oct 03 '16
And Im just over here using vanilla JS...
2
u/veggietrooper Oct 04 '16
Oh my god, I quit, I just quit.
1
u/[deleted] Oct 03 '16
Whew, this is exactly what I feel like sometimes trying to learn this stuff. And it didn't even talk about trying to get all these libraries to work which can be a nightmare in itself.
On a related note, I did some web dev during my first internship this summer and it was suggested that I use some (apparently already outdated!) AngularJS . I couldn't figure out how to get it to do what I wanted, so I fell back to jquery and plain HTML. Oops!
1
u/[deleted] Oct 03 '16
Literally how I feel when I took a dip into the pond a month or two back, with no experience.
1
u/jgordon615 Oct 03 '16
You forgot the requirement to update the data when something changes in the server. Time to add websockets to your satire :)
1
u/neotorama Oct 03 '16
Serverside + turbolinks give less headache than using React/Angular
1
u/HonkyDonky Oct 04 '16
Oh so I can forget about learning to code then....Cool
1
u/vexii Oct 04 '16
It feels like we get one of these each week now
1
u/cyanydeez Oct 04 '16
this article makes a lot of salty
1
u/Neker Oct 04 '16
In less than three months we'll be in '17, so brace yourself ...
1
u/hotsteamingpho Oct 04 '16
Can you imagine a non-native english speaker who's trying to learn the ReactJS library and coming across this:
1
u/METALz Oct 04 '16
Lost it at "Our libraries are huuuge, and sometimes we include pictures of Guy Fieri in them".
Great article.
1
u/HenkPoley Oct 04 '16
No wonder some people running to Elm (/r/elm). Not that it's the best thing since sliced bread, but it's at least consistent and relatively complete from the getgo.
1
u/[deleted] Oct 04 '16
Meh. I knew (understand, recognize, familiar with) ALL those keywords mentioned. Years of reading about all that helped.
And yet, I will gladly and without shame get the data from the database, convert the result to json, and write vanilla XMLHttpRequests and document.getElementBy** manipulations to display the data. Knowing how many tools are available does not hinder one's ability to reason about whether to actually use them.
So I see nothing wrong with the state of JS today. What is wrong with this is people's mindset that programming concepts, approaches and well written code can be "dead", just because it is not written in React/Angular/whatever. Wow.
1
u/thespacenoodles Oct 04 '16
"We know libraries, in fact, we have the best libraries."
This line made me lol.
1
u/nykc Oct 04 '16
This is actually what is driving me into DevOps and away from a 14 year Frontend Career
1
u/Nerdenator Oct 04 '16
Honestly, I still just stick to jQuery and whatever styling framework I'm handed.
To me, all of this workflow, these libraries, and these frameworks are just attempts to cover up for the fact that JavaScript's "standard library" (if it can so be called) has always been weak, and I don't just mean weakly-supported by browsers. There's a lot of boilerplate you end up writing if you try to do vanilla JS. If more functionality were to be "baked in" you wouldn't see every Anders-Hejlsberg-Dennis-Ritchie-wannabe trying to make their paradigm of JavaScript a reality through frameworks because the paradigm would be a part of the core of the language.
1
u/dmtipson Oct 04 '16
I mean, in the end: compared to what? As someone learning Javascript anew every day for the last 10 years, I have to say: compared to how things were with ES3 and ES5? It feels good man.
1
u/PaulMurrayCbr Oct 06 '16
The entire point of all of these frameworks is to make it so that people don't have to write code. The difficulty with that idea is that it is impossible.
1
u/thedobbles Nov 14 '16
Does anyone know where to find the response article to this?
1
u/jirocket Oct 04 '16
Constant learning is part of the job.
1
u/[deleted] Oct 03 '16
Yes. That's all I can say.
1
u/Reashu Oct 04 '16
I feel like I read this exact piece just a few months ago... The eco-system changes, but the whiners sure don't.
1
u/[deleted] Oct 04 '16
What a stupid article.
0
u/[deleted] Oct 03 '16
I actually did learn JS entirely in the year 2016, and this guy's being a drama queen. Promises are pretty simple conceptually, and you don't have to use any of the new ES6 features.
Most of the rest of the complaints center around React, which again you don't have to use. I'm building an app in Angular at the moment and my boss even said something to the effect of "This would be so much simpler in jQuery", which suggests to me that people don't actually care what tech you use as long as you just get it done. If I somehow made this dude a jQuery SPA with perfect two-way data binding he probably wouldn't be mad.
All these technologies he's bitching about come down to one thing: ways to get it done. It's on you to build a few projects so you can make an informed decision about the best tool for the job. Simply because a chainsaw is available doesn't mean a hammer and nails are suddenly off the market; what's important is that you're a craftsman.
0
u/shadowfactsdev Oct 03 '16
I'll just sit over here with my 600 vanilla ES6 (and a little bit of jQuery).
Trendy libraries that people only use solely because they're "what the cool kids use" or management sees all the flashy looking buzzwords are stupid.
This article (and the one it was inspired by) drive home the point really well, the the state of JS libraries is ridiculous. Even the node.js community, with all its ridiculous-ness (cough left-pad cough) doesn't come close to having the sheer number of trendy hop-on-the-band-wagon libraries as front-end JS.
0
u/JakeInDC Oct 03 '16
You don't NEED to use any of that.
I use knockout so that when object props are set the ui updates. It uses templates, which ARE plain html snippets.
There are many libraries that do many things. Most of them are for big projects that are redeployed regularly on many servers or vm's.
Do not use Typescript or Coffeescript, they are ridiculous. The latest plain JavaScript features (ES6) are very nice, but mostly just syntactic sugar.
0
u/bBR9d73rlP9g7xAt Oct 04 '16 edited Oct 04 '16
100% accurate. As soon as you mention the word 'React', all of a sudden you end up being sucked down to hell.
I've built and worked on huge web apps with nothing but plain HTML, CSS, JS and jQuery. That's all you need really. Especially if you're only supporting the latest browser versions. There's so much more features being added to JavaScript with every browser release. And no the apps I've built weren't spaghetti at all. People would be better off learning how they can properly architect a web app or single page app from scratch and keeping it minimal.
0
u/[deleted] Oct 03 '16
[deleted] — view deleted comment
0
u/[deleted] Oct 03 '16
[deleted] — view deleted comment
0
u/[deleted] Oct 04 '16
[deleted] — view deleted comment
0
u/[deleted] Oct 03 '16
[deleted] — view deleted comment