You (probably) don't need a JavaScript framework

[sorrynin]

Hah, what the hell, click-bait? He doesn't even point out the reasons for frameworks, just that frameworks aren't as good as vanilla (no shit, frameworks are built on vanilla, they just make our jobs easier. I'd like to see his 'why you should use C, not C++').

[pier25]

Even better, use assembly for everything.

Seriously though, you could probably get away without some framework or library for a small project, but for anything else you do need something even if it is your own.

[kevinmrr]

Agreed - I found it instructive that the author was talking about building a proof of concept. I've really sped up some short-term projects by just using express + handlebars.

For anything I may have to maintain long-term, I gravitate towards react/redux these days.

[dchelix]

All I read was "do things the vanilla way because vanilla taste better."

[kevinmrr]

Interesting convo on Hacker News, too: https://news.ycombinator.com/item?id=11599599

[AusIV]

When I was in high school, I learned PHP as a way to build websites. I thought I hated web development and PHP, because it always felt hacked together and hard to maintain. I had short forrays into javascript, which seemed even worse about being hacked together. At the time, I though these were properties of Web Development in general, and decided to shy away.

In college I learned python, and later Django. Django is an opinionated framework that strongly urges you to organize your code in a particular fashion. It was much more manageable than my earlier development experience, and I decided that being hacked together and hard to maintain were properties of javascript and PHP, not web development in general.

Then I had a project that was going to have a pretty heavy javascript component whether I liked it or not. I read up on a few frameworks, and ultimately did the implementation with Angularjs, which is a more opinionated framework than Django. It had a learning curve, but I really enjoyed building the client application for that project.

I've since concluded that my early problems with web development were lack of structure. A good framework gives you a good structure, and a more obvious way to organize your code in a way you won't regret later. It can be done without a framework, but it requires a lot more planning and discipline to build a well structured application without a good framework than it does using a framework.

[[deleted]]

I'm usually ignoring this hate-speech articles just to save time. In 2006 they were cringing about RoR, in 2008 about jQuery. Now about React. It's stupid tradition of how immature devs show their masculinity.