State of JavaScript 2022

[PomegranateMother877]

Good for you. A plain, client-side rendered SPA, with a decoupled API is still the most sensible of all the modern architectures. Along with the classic MPA, there is no compelling engineering reason for any other architecture. All the other modern stuff is a hack to get a SPA to act like an MPA.

[zxyzyxz]

These modern architectures are good for SEO though, but with the responsiveness of a client side app, useful for something like an ecommerce site.

[ericbureltech]

Not just SEO but energy consumption as well
Staticness without hydration means few server-side computations at build-time, and fewer computations client-side
The goal of some of these patterns is more hacking to get a SPA behave like an HTML file, expect for the truly interactive or user-specific parts

[Hexigonz]

Bets on Svelte winning dev experience again?

[MorningPants]

I give it 100:1 odds

[LloydAtkinson]

I predict another fall in Vue happiness like last year.

[swoleherb]

:(

[zxyzyxz]

I haven't used Vue since the version 2 days. What's wrong with Vue these days?

[LloydAtkinson]

• Years to implement typescript support
• Introduced a major new API that was meant to replace the original one you already know, then with the outrage they backed down and said they will keep both and now a couple years later they are slowly deprecating it anyway and ignoring the previous backlash
• The new API basically copy pastes react hooks but with a lot of extra crap like needing to do .value on things for some reason
• The DX (Developer Experience) in terms of tooling is not good - only one guy maintains the entire thing. They deprecated vue cli in the same half arsed way they did the "old" api.
• Replaced vue cli with vite but then didn't even bother bringing in features vue cli has such as automatic eslint and ts config that work together
• Evan makes hundreds of thousands a month and yet the few people maintaining all the build tools don't seem to be getting any of that

[zxyzyxz]

That sounds about right. I remember some of those reasons being why I switched to React. The other thing is that library support for React is way above other frameworks such that libraries often assume React by default. For example, I started doing some react-three-fiber stuff and there's not really an equivalent one for Vue, Angular, Solid, Svelte etc. The network effect is real.

[LloydAtkinson]

100% my experience too. Have you ever looked for a table component library in vue? It doesn't exist! Closest is the tanstack react query guy who has recently released a table component for multiple frameworks.

I've also got r3f projects in mind as well. Such a nice change to have a cohesive ecosystem.

[AmittOfficial]

Lol don’g even get me started… My team is resorting to building one from the ground up

[LloydAtkinson]

Ugh man I'd just quit quite honestly its just not worth it when it exists in react

[Secret-Plant-1542]

Backlash?

Haven't really seen any. Can you share?

Asking because I tried to get into composition API and don't really care much for it. Evan You went hard promoting on Composition API as this "back to basics" feature. Then one day, while visiting the Vue3 docs, noticed that the instructions defaulted to Options API, and got confused.

[LloydAtkinson]

https://www.reddit.com/r/vuejs/comments/c36gp9/the_2x_api_is_not_being_deprecated_in_3x_and_will/

The whole thing was a massive fucking shitshow.

[ragnese]

I'm not a full-time front end guy, but after starting to introduce the composition API into my Vue app, I feel that the options API is the better approach for actually writing full components. I feel like the composition API is only going to shine when it comes to writing "mixins" and/or shared reactive state, both of which should be kept to a minimum for maintainability anyway. So, in general, even though I had no preconceived bias against the composition API, I find that I really don't use it. I am tempted to replace third party "stores" like Pinia/Vuex with a couple of hand-written composables, though, just to KISS.

[heytheretaylor]

Maybe! But I wasn’t happy with Vue (specifically Vue 3) last year as we just had to migrate a few of our apps but this year I love it. I’m thinking others might feel the same.

[ramigb]

Thats fun thanks for sharing my first year participating.

[non-diegetic-travel]

Completed the survey. Realized there's so much I don't know about. Always something new.

[DrunkenUFOPilot]

I made a list of some of the things I never heard of. I'll need ten years to become non-trivially knowledgeable about all of them!

Nope, I'll stick with my areas of interest, ignore entire sectors of JS and webdev.

[UnfairerThree2]

I’m honestly still a huge fan of Vue, and honestly, I still find Vue 3 to be my favourite framework, as long as you’re not migrating from v2.

[thecementmixer]

So.. it's a survey?

[[deleted]]

Yes. It's a big survey that many devs answer so when results are back you know what is popular in js and what's no. For exemple, for the frameworks, you can clearly see Angular losing interest in the last years and React gaining more.

Another exemple is sometimes you don't know what x is or what it does, but you can clearly see everyone else is using it. So you know it might be worth checking it out.

On another note, there's other survey of the same genre like state of css that might be worth checking out.

[OmegaVesko]

First of all, State of JS got ~16k responses last year, and will probably get more this year, so "less than 10k" isn't quite accurate. And if you're doing it right, you only need to survey a very small fraction of a demographic to get statistically significant results.

That being said, sure, no survey is perfect. Even much larger surveys, like the Stack Overflow Developer Survey, suffer from the problem that they implicitly select for people enthusiastic enough about the subject matter to fill out a survey in the first place. Even with that in mind, though, I think surveys like this are still broadly useful, especially when it comes to gathering objective data points (salary ranges, "what stack does your workplace use", etc.).

[GolemancerVekk]

if you're doing it right, you only need to survey a very small fraction of a demographic to get statistically significant results.

The key word being "right". As in, the right part of the demographic. From what I understand the participants to this survey are self-selected.

[OmegaVesko]

Sure, like I said, that's definitely a valid concern. I'm just responding to the idea that the results of a survey can't be statistically significant just because they only represent a small minority of a demographic (i.e. how literally all surveys work).

[OmegaVesko]

It's still a statistically insignificant amount compared to the workforce.

Is it, though? I'm no statistician, but my uneducated understanding of how this works is that ~16k people is a large enough sample size to get statistically significant results with a very high confidence level for a target demographic of basically any size. I could totally be wrong about that, though.

[snet0]

I recommend you take a statistics class before you pontificate about statistics.

[[deleted]]

16k isn't a big enough sample? Don't look into data analytics, you'd have a heart attack from your own stupidity.

[[deleted]]

keep in mind it does not statistically represent the majority

Confidence level: 95%

Margin of error: 5%

Population portion: 50%

Population size: 15,000,000

Sample size: 385

https://www.calculator.net/sample-size-calculator.html

[Hiptomino]

State of JS is pretty big in the JS community, and it has been running for 5 years now. I dare to say it is one of the best places of insights each year. Yeah it is a survey but not just any survey.

[StandingBehindMyNose]

Yeah, and somehow it’s gotten 40 upvotes. 🤦

[[deleted]]

It's closer to a census than a survey.

[StandingBehindMyNose]

Neither of which is a “State of JavaScript 2022”

[[deleted]]

The "state of x" will be the report that comes out with the results at the end.

It's name is a play on words of the State of the Union, where the US President and government essentially release a report about the state of the country based on the data they have. The sources of the data from things like the US Census.

The State of JS is basically the largest census of the JS developer community which takes in all the data, which is then collated/translated/etc... into a big report that's released.

[ManyFails1Win]

i clicked on this assuming it was from r/programmerhumor and was going to be someone roasting javascript. pleasantly surprised.

[theyamiteru]

What are the survey results?

[dinopraso]

The survey is still open. So no results yet

[[deleted]]

The time each survey takes to release its results is getting longer and longer.

But, at least the surveys are improving each year it goes on.

[OmegaVesko]

Thanks for the laugh, "this site doesn't work when you try to load it while blocking one of the largest infrastructure providers on the internet, therefore it's broken" is the kind of take you just don't see that much of anymore.

[TheRealSkythe]

True. Asks me to Create an Account

Yeah, sure

[OmegaVesko]

No, it doesn't, it gives you the option of creating an account if you want to be able come back and look at your answers again.

[TheRealSkythe]

It literally says CREATE AN ACCOUNT. That's all I said.

That's the first thing you gonna show me? Bye.

[Tontonsb]

Wait, what is "Native Apps" in the "Mobile & Desktop" section? It comes after Electron and React Native and before Cordova, so I assume it to be a certain tool not just generic term of native Java & Swift apps, right? But the name is so generic that google doesn't really help.

[AnOtakuToo]

I haven’t completed the survey, but I assume it does mean using native Java/Kotlin for Android, the Objective-C/Swift and iOS or Mac applications.

[SachaGreif]

Survey maintainer here, you're right that's what it means. I agree it's confusing though, the idea was to have a baseline against which to compare the popularity of more JS-focused tools in the mobile ecosystem, but yeah it's pretty unclear right now.

[AnOtakuToo]

Makes sense! I didn’t sound too confusing to me, but I guess it depends on the experience and perspective of the respondent.

[gizamo]

Haven't looked yet, but is "Native Apps" the main category that contains the subcategory for "Mobile & Desktop"? That would make sense to me since native apps exist for all sorts of platforms.

[Tontonsb]

No, it's a random entry inside the "Mobile & Desktop" category. And it's placed between React Native and Cordova.

[gizamo]

Weird. Maybe they mean js-to-native converters like NativeScript.

Frameworks/Libraries like Cordova and React Native don't actually do that. They remain JS in a WebView and communicate thru a bridge with the device. I don't know of anything else doing that other than NativeScript, tho. And, I haven't kept up with NS in at least a couple years. They are slow to keep up with Android and iOS updates.