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

101–110 of 245 posts

Re: State of JavaScript 2021

#101

Post by toastal »

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…

And they're looking at closing the bubble up more cross-referencing specifically survey takers' closed-source Twitter and GitHub accounts, leaving out the privacy-conscience and open-source fundamentalists that don't use these platforms but have a worthwhile opinion that should be represented and heard.

Re: State of JavaScript 2021

#103

Post by ricardobeat »

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…

Next.js, SvelteKit and so on are backend frameworks for sure, giving you an http server, routing, authentication, data loading. It’s just a slightly different toolkit than you’d get from traditional frameworks (an ORM, job scheduling, etc). Express indeed hardly qualifies.

As a long-time frontend developer, I find Angular pretty bad, but I understand it feels fine if you come from .NET/Java or another “enterprise-y” environment.

Re: State of JavaScript 2021

#104

Post by seumars »

rembrant wrote: post #63

Proxies are cool. I use them in github.com/thebinarysearchtree/artwork which I haven't released. That libraries tag line is "you wanted less javascript and more html, so we delivered - artwork, the 100% javascript and css front-end framework". Anyway, I use proxies when I want a bunch of divs with classnames. You just do const { container, heading } = divs; and then container is assigned to an HTMLDivElement and the…

Your comment makes no sense without you specifying what the "divs" variable value even is.

Re: State of JavaScript 2021

#105

Post by seumars »

samwillis wrote: post #73

When choosing a framework to build with now, I always look at how the project is funded and increasingly want to see a business backing it where it's a core part of their business model. That's what's so appealing about Svelte, now its effectively funded by Vercel, they need it to thrive as they want people to host their Svelte app on their platform. The other one with an even more explicit in its commercial support…

"a core part of their business model" means actively look for vendor lock-in. I have to say I don't get it.

Re: State of JavaScript 2021

#106

Post by matt7340 »

Klaster_1 wrote: post #98
arcosdev wrote: post #87

Earlier quoted context omitted.

Nah, Angular is that bad

What do you consider "that bad" in Angular?

I could rant for a while, but a few things off the top of my head: over-architected, overly complex, sometimes bad tooling (karma, protractor), tons of old issues (though they’ve been working to clean this up lately), big time inner platform effect (the templating feels like a language to itself), slow compilation, RxJS is generally overkill, Reactive forms is untyped(!) and clunky, and the “included batteries” are sometimes later removed leaving you to figure it out yourself, such as with protractor and eslint. If I’m just gonna figure it out, why not use React anyway and get a much simpler framework?

That said, for a team or teams with lots of apps where a consistent structure provides real benefits in getting up to speed, I can appreciate that some of angular’s enforced structure could be helpful.

Re: State of JavaScript 2021

#107

Post by krembanan »

jillesvangurp wrote: post #88
cj wrote: post #48

Only 22% make above $100k? [0] Those salary demographics makes me doubt the entire data set. Over 40% of respondents make less than $50k [0] https://2021.stateofjs.com/en-US/demographics/#yearly_salary Edit: Only 14% of respondents are in the US, which probably explains the above.

Frontend development is not a great career path; it's mostly a young people's game. I know senior react developers in their thirties that are increasingly struggling to find well paying gigs because they are competing with young people at half their rate. A lot of frontend developers transition to full stack js and from there to doing more serious things using Go, Rust, or whatever. That's where the money is. It's a…

Do you have any data to back this up at all? My experience is opposite, many backend jobs have been replaced by different BaaS', while most of the programming is done on the frontend. If you hire a younger developer half your rate, you get what you pay for. Complicated frontend projects needs good seniors, and they get paid their fair share.

IME demand for experienced and talented frontend seniors have never been higher, as frontend continues to expand in complexity, and more logic is handled on the frontend-stack (routing, API-routes with eg. Nextjs, SSG/SSR and so on.

Re: State of JavaScript 2021

#109

Post by ducharmdev »

sylens wrote: post #91
rk06 wrote: post #84

Earlier quoted context omitted.

No, it is not. Unless you are planning to use your experience for getting a job, it is not worth it. I would advise you to use vue or svelte.

Would most likely not factor into the career path as I don't have the time to dedicate myself to becoming a front-end pro

If career ambitions aren't a factor, I'd definitely second Svelte. I used to do frontend dev and switched into a more backend role, but every time I do a hobby project with frontend work, I always pick Svelte. I briefly peek into the others, but Svelte is the simplest by far.

Re: State of JavaScript 2021

#110

Post by neurotrace »

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 supported
Post reply on HN