State of JavaScript 2021

Post by davedx » Fri, Feb 18, 2022, 11:17 AM UTC

ricardobeat wrote: post #103

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”…

Post by midrus » Fri, Feb 18, 2022, 1:47 PM UTC

rembrant wrote: post #79

tmstieff wrote: post #47

Earlier quoted context omitted.

I'm working on a codebase that evolved at the same pace as React, but without any thought for idiomatic principals. As a result, you have class-based components, purely functional components, hook based components, HOCs, Redux state passed in through the older functional way, Redux state passed in through an HOC, styled components, traditional CSS styled components, and anything else you can think of that was in vogu…

I believe React is inherently terrible, rather than your reason. I think all libraries that try to abstract an underlying technology into something that it is not, and then also have to provide escape clauses for the abstraction because the user actually has to know how the underlying stuff works, are inherently broken. I also think state-based reactivity is a terrible way to reason about things because sometimes you…

Post by ecf » Fri, Feb 18, 2022, 8:26 PM UTC

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…

Post by manigandham » Sat, Feb 19, 2022, 6:14 PM UTC

pjmlp wrote: post #147

rob74 wrote: post #136

Earlier quoted context omitted.

Well, if developers would approach their task with knowledge and wisdom, then the abomination that is Node.js would never have been unleashed on the developer community. But here we are: "yay, Google has written a blazingly fast JS engine, so now we can use JS in the backend!" - never once stopping to question if this is really a good idea...

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.

Post by Gigacore » Sun, Feb 20, 2022, 11:08 AM UTC

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…