Live data from Hacker News

The Brutal Lifecycle of JavaScript Frameworks

stackoverflow.blog

31–40 of 128 posts

Re: The Brutal Lifecycle of JavaScript Frameworks

#31
About to make an App using React(and react native?)

Up until this point, I usually would make most things from scratch and pull in libraries sparce. No big deal because my previous programs didnt need to. (Self taught programmer for 11 years.)

For the next 3 months, I'll be working on this almost alone. Is it worth using some of my resources to hire a React developer?

Also, this topic implies React will be gone in about ~5 years? That sounds good for me.

Re: The Brutal Lifecycle of JavaScript Frameworks

#32

Woah... Was honestly surprised to see Vue.js was so tiny in comparison to Ang and React regarding "% of Stack Overflow questions that month". I thought it was much bigger

Vue.js has a spectacular tutorial that answers most if not all questions one might have about the framework.

[deleted]

Re: The Brutal Lifecycle of JavaScript Frameworks

#33

One of the things I don't think it accounts for in talking about the downfall of something like jQuery is that as time goes on, the questions have already been asked. So of course there's going to be less questions asked about jQuery in 2017 versus 2009, because if I need to figure out how to select elements based on an attribute rather than a class or id, it's already there.

Yep! Same for React. It has a much smaller API surface area than Angular (and goes wrong it mysterious ways less often!), so fewer people will be asking questions about it. From my perspective, it appears that React is still very much in ascendancy.

From my anecdotal experience of just watching SO's React queue, most questions about React that show up (that aren't repeats) are almost always regarding how it's used with some library in the ecosystem.

React-router, Redux, Webpack, Material UI, etc.

So even though the API itself small, there's still an endless number of questions out there for people to ask!

Re: The Brutal Lifecycle of JavaScript Frameworks

#34
post #22

The JavaScript/jQuery community (no difference from outside) was absolutely cancerous. It was impossible to find a javascript question that didn't include top answer "In jQuery...". Makes my blood boil just thinking about it years later. I wonder what effect this has on usage. How likely are new developers to use it if virtually every question they have is answered by this (no matter how irrelevant the answer should…

To be fair, that's because the jQuery solution was usually orders of magnitude simpler. Although newer versions of javascript have absorbed enough of the jQuery api that this is no longer the case.

Acceptable way would be "Hey, it's done like this, but since the language sucks there's this random library where you can do it this way".

Including jQuery for one small task would be stupid.

Including jQuery in a non-web project would be weird.

Including jQuery in some es variants would be impossible.

Re: The Brutal Lifecycle of JavaScript Frameworks

#35

One of the things I don't think it accounts for in talking about the downfall of something like jQuery is that as time goes on, the questions have already been asked. So of course there's going to be less questions asked about jQuery in 2017 versus 2009, because if I need to figure out how to select elements based on an attribute rather than a class or id, it's already there.

On the same note, the older frameworks solved older problems. jQuery was the killer framework because it handled browser compatibility back in a time when people not only needed to support IE8, but IE6, and few companies felt comfortable telling people to just update their browser. Well, those days are past, so that problem is no longer a reason to choose a framework, and when you take that out of the picture, jQuery…

[deleted]

Re: The Brutal Lifecycle of JavaScript Frameworks

#36

About to make an App using React(and react native?) Up until this point, I usually would make most things from scratch and pull in libraries sparce. No big deal because my previous programs didnt need to. (Self taught programmer for 11 years.) For the next 3 months, I'll be working on this almost alone. Is it worth using some of my resources to hire a React developer? Also, this topic implies React will be gone in ab…

React's API is fairly small. Most of the code you're writing with React (outside of libraries) is based on ES6.

You can easily get by with someone that has years of Javascript experience instead, preferably a developer who's familiar with Functional-style JS.

Re: The Brutal Lifecycle of JavaScript Frameworks

#37
post #22

The JavaScript/jQuery community (no difference from outside) was absolutely cancerous. It was impossible to find a javascript question that didn't include top answer "In jQuery...". Makes my blood boil just thinking about it years later. I wonder what effect this has on usage. How likely are new developers to use it if virtually every question they have is answered by this (no matter how irrelevant the answer should…

The contemporary equivalent, albeit one or a few steps up the abstraction ladder, is "how to get started with (javascript|frontend development)" guides — append "in 2018" for better SEO — which boil down to "use React".

Re: The Brutal Lifecycle of JavaScript Frameworks

#38

About to make an App using React(and react native?) Up until this point, I usually would make most things from scratch and pull in libraries sparce. No big deal because my previous programs didnt need to. (Self taught programmer for 11 years.) For the next 3 months, I'll be working on this almost alone. Is it worth using some of my resources to hire a React developer? Also, this topic implies React will be gone in ab…

I would learn React if I was you. Check out create-react-app on Github. It will set you up with a working app to play with in a matter of seconds. If you're expecting to use React Native it looks like they have a create-react-native-app also.

Re: The Brutal Lifecycle of JavaScript Frameworks

#39
post #16

The PHP and Vue correlation can at least partly be explained by the fact that Laravel, a popular PHP web framework, has first-hand support for Vue and installs Vue by default in projects bootstrapped with their cli tool.

WordPress.com But Vues triumphal march starts before Laravel or WordPress.
Post reply on HN