Depending on who you ask, right now JavaScript is either turning into a modern, reliable language, or a bloated, overly complex dependency hell. Or maybe both?
What's more, there's just so many options: Do you use React or Angular 2? Do you really need Webpack? And what's this month's recommended way of dealing with CSS?
Like you, I spent far too many hours reading about all this, and at the end I still wasn't sure. So I decided to create a survey to see what everybody else thought. It seems like I must've hit a nerve, because I got over 9000 answers in just over two weeks!
Further down in the article, the survey results are listed, though not in an easily scrape-able format. Oddly enough, the site degrades gracefully, and does not require Javascript to be enabled.
http://stateofjs.com/2016/introduction/
-- submitted from IRC
(Score: 1, Interesting) by Anonymous Coward on Tuesday October 11 2016, @07:34PM
Fat clients are a bad idea.
Thin clients may be boring, but more reliable and easier to deploy on, assuming eye-candy-fad-chasing is not your primary goal.
We just need a decent thin-client standard. For one, just make the client a dumb vector coordinate processor and put the layout engine on the server. I'm tired of testing web pages on 50 odd client brand/version variations and having stuff position all funny on some due to some slight variation in layout/render logic.
It's focking insane! Vulcans would puke; it's irrational. Bad humans!