I expanded my surprisingly-popular last Quora answer into a Medium article: Which JavaScript frameworks should you learn in 2018?https://medium.com/@samerbuna/which-javascript-frameworks-should-you-learn-in-2018-ecea9a27617d …
I'm not saying "use the best tool for the job" abstractly. I'm saying a use-case based analysis is better than categorizing tools into "framework" or "not a framework" and then broadly advising *all* developers to "not learn a framework" as your post did.
-
-
I didn't mean to say a library is better than a framework but rather learning how to use a framework is a big commitment that needs a reason (job, project). I learned Ember when I needed to use it. I think understanding small libraries is a better time investment career-wise.
-
Thanks for the feedback. I modified the article to remove the "React bias". The point I wanted the article to highlight is: learn freaking js itself first and how to run it correctly before wasting your time getting confused about a big framework.
-
Thanks for listening :) I appreciated this conversation.
-
I think you're exactly right that ppl should learn frameworks for concrete reasons, and that people can learn frameworks on the job when it comes up. There's way too much adoption confusion around "where will I get an <X> programmer". Answer: hire a JS programmer and teach them
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
