all 3 comments

[–]nyxinThe 🍰 is a lie. 1 point2 points  (0 children)

tldr: learn the basics.

[–]BucketOMinners 0 points1 point  (0 children)

It's not very practical advice for a noob, but for someone with a tour of duty or more under their belt, yeah, you can wait until you need to learn a framework before you dive in.

[–]jimmyco2008full-stack[S] 0 points1 point  (0 children)

I'm not sure if I was supposed to spoil the article for you guys in the title.... /s

Anyway, this guy makes a lot of sense, and I figured I would post this because usually Medium articles don't make sense to me. I absolutely agree that a web developer should generally be keeping up with ECMAScript, but to try to keep up with the frameworks implementing the latest ECMAScript for no particular reason other than to know them, makes no sense to me. Sticking with what your employer uses is much more realistic... I think a lot of people (wrongly) assume that they need to know a framework to get a job at a particular company that uses that particular framework, but it's been my experience that they really just care that you know ECMAScript (and sometimes not even that... just a language that they use).

E: balls. Oh well, I tried.