Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

State of JavaScript 2021

2021.stateofjs.com

Post reply on HN
Print view View original

211–220 of 245 posts

Re: State of JavaScript 2021

#211

Post by rk06 »

agumonkey wrote: post #186
rk06 wrote: post #160

Earlier quoted context omitted.

react also happens to be The js framework used by meta. and the most popular js framework. how do you get something like 90% of that?

My comment wasn't clear but I had this idea that if someone made a clone of react called flowy with only marginal changes, people might be happy to use that because it's just "not react" anymore. I was questioning the emotional aspect of group work.

Take a look at preact. It is 90% like react in technical sense, and provides missing 10% in compat package

Re: State of JavaScript 2021

#212

Post by solarmist »

neurotrace wrote: post #110
tomerkr wrote: post #7

Interested in the steady drop in satisfaction with Vue since 2018. I remember being positively impressed when I looked into it. Is it simply due to more usage in actual systems causing people to dislike tools they really work with, or is the framework developing in a direction people are unhappy with?

Unpopular opinion here: the more I use Vue, the more I realize that it started off doing things differently because it thought it was smarter than more established frameworks. Over time, you're seeing it copy a lot ideas from other systems because they're actually hard earned lessons. Vue is the manifestation of the frontend hype cycle. There's no reason to use it over something like React which is much better suppor…

How does the Vue 2/Vue 3 change factor into your opinion? Making things more consistent or something else?

Re: State of JavaScript 2021

#213

Post by max__d »

hutrdvnj wrote: post #53
davedx wrote: post #22

I read this report every year. This year it feels the most like it's driven by hype (and marketing, hi Vercel!). In my professional and personal experience, react has never been better to use (in terms of features, DX, maturity, community, productivity), yet if you look at the "popularity" (oh dear) graph, it's basically just describing how older tech slides down while newer shiny tech comes in and is instantly the m…

React is becoming a boring technology and that's a good thing.

I went from building dummy projects in vue2 to production ready apps in react(next actually) because of the giant community it has, in particular in the web3 world. Boring or not, if it has better support/resources it's a logical better choice

Re: State of JavaScript 2021

#214

Post by pjmlp »

MonaroVXR wrote: post #207
pjmlp wrote: post #147

Earlier quoted context omitted.

I miss the days when bundling was just dumping a couple of JS scripts into the scripts/lib directory and that was it. Guess what is my approach when having side gigs.

>Guess what is my approach when having side gigs Webpack?

Nope, my first sentence, pack the JavaScript stuff on the scripts lib and let Java/.NET build take care of the rest, as it belongs on a proper full stack SSR framework.

Re: State of JavaScript 2021

#215

Post by sandstrom »

ravenstine wrote: post #173
was_a_dev wrote: post #16

Not familiar with much front-end work - can anyone give insight to what's gone on with Ember?

Ember today is too little too late. As someone else said, Ember was never that popular, and the community doesn't really strive to be popular. This is, however, a dilemma, because you need some popularity for your framework to have people interested in working on it. Ember was cool initially because, if you knew Rails, then you could get what Ember was about even if it was confusing at times. There were some choices…

I agree there have been some mistakes (difficult to design the perfect framework on your first attempt), but overall we're quite happy with Ember.

- Embroider is actually 1.0 now and quite usable (https://github.com/embroider-build/embroider).

- Agree with Ember Data and nested resources, that's still needlessly complicated. Same with lack of wildcard in the router/URL.

There are still things Ember needs to fix, for example removing controllers and improve Ember Data. But overall I think there is a good future ahead for Ember.

Re: State of JavaScript 2021

#216

Post by AlfeG »

nawgz wrote: post #14
tomerkr wrote: post #7

Interested in the steady drop in satisfaction with Vue since 2018. I remember being positively impressed when I looked into it. Is it simply due to more usage in actual systems causing people to dislike tools they really work with, or is the framework developing in a direction people are unhappy with?

Vue.js is heavily magic and doesn't support basic React concepts like render props. How is that possibly a popular framework? Like any "easy" library, you'll run into hard situations with no solutions.

I understand all this traction with Composition API, and don't liked it at all first time.

Whenever I need to go and fix some bugs in old Vue 2 app without CompositionAPI and setup syntax - I feel very bad. Guess that Vue team a bit failed to properly describe why to use composition api, but now I think that it seems to be useful a lot

Re: State of JavaScript 2021

#217

Post by derangedHorse »

searchableguy wrote: post #17
nindalf wrote: post #3

Not surprised to see satisfaction drop with increase in usage for React. People feeling like they’re forced to use something because of external constraints (coworkers choices etc) are rarely satisfied with that choice. That’s the fate of any tool that becomes popular enough.

People inheriting old react codebases now have to deal with way more complexity. For example, everyone was using styled components 2-3 years ago and now they are moving away. The complexity styled components introduced has to be managed alongside the current trend (tailwind?). Old styled components codebase looks horrible. They end up with Java inheritance hell. You create a button, then create another button inherit…

React doesn’t stop you from writing messy and inconsistent code. I’d say it does bring structure to code that could be a lot worse without it though.

Re: State of JavaScript 2021

#218

Post by EnKopVand »

mollerhoj wrote: post #177
EnKopVand wrote: post #130

Earlier quoted context omitted.

I’ve got quite a lot of experience with non-IT enterprise, in Denmark, and almost nobody uses those fancy new technologies around here. Over the past few years everything has moved to typescript (typically with react, but some angular remains from older decisions), dotnet, Java, php or c++. That’s basically it. The only job listing to even mention things like Rust in the region where I live in the past 5 years is Goo…

While non-IT enterprise is a big job marked, I guess the HN crowd leans towards the startup scene. There are plenty of python/django and ruby on rails and node companies in copenhagen :-)

Oh this is very true. There are actually a few django and Ruby on Rails jobs open in my area (region midt) on a fairly regular basis. There are a lot of node jobs as well as most things have moved to have some sort of TypeScript front end.

I’m not sure those really count as “new and hipster”, however, I mean the person I was replying to was lamenting “react” being old. ;)

Re: State of JavaScript 2021

#219

Post by MisterSandman »

davedx wrote: post #22

I read this report every year. This year it feels the most like it's driven by hype (and marketing, hi Vercel!). In my professional and personal experience, react has never been better to use (in terms of features, DX, maturity, community, productivity), yet if you look at the "popularity" (oh dear) graph, it's basically just describing how older tech slides down while newer shiny tech comes in and is instantly the m…

To say that React is only popular because it was "new" and "shiny" is laughable. It took years to get to the point where it is now.

Re: State of JavaScript 2021

#220

Post by MisterSandman »

sundarurfriend wrote: post #93
Vinnl wrote: post #57

Earlier quoted context omitted.

There's also a tab that divides it up by country. In the US, 58.4% makes $100k-$200k, and 16.1% over $200k.

The contrast is really stark when you compare it to for eg. India, where 64% of the respondents earn less than $50k. And this is likely with a skewed sample too - 343 respondents, of which I'd bet most are in FAANG and FAANG-adjacent companies (eg. Flipkart). The actual percentage that earn above 2 lakhs per month (= $50k p.a.) is likely less than 20%, even allowing for a strict definition of a "Javascript developer"…

Those numbers for India are way, way, way off, even more than you said. The average Indian dev working in TCS, Infosys or Cognizant isn't going to care about surveys like these. (Though, I don't know if any of these companies even hire too many JS devs?)
Post reply on HN