State of JavaScript 2019
2019.stateofjs.com
State of JavaScript 2019
1–10 of 372 posts
Re: State of JavaScript 2019
#2Something that jumps out to me in the demographics is how few respondents are from Japan (0.6% vs e.g. 5.1% from Germany). Does anyone have a good explanation?
Re: State of JavaScript 2019
#3Sad to see Ionic in the avoid category. Their latest release I thought was quite polished, and I've enjoyed using Capacitor rather than Cordova. I think the key to further success is breaking away from Cordova entirely, and expanding the native features supported in Capacitor. Right now I find myself having to use both due to some things not being implemented in Capacitor yet.
Re: State of JavaScript 2019
#4Something that jumps out to me in the demographics is how few respondents are from Japan (0.6% vs e.g. 5.1% from Germany). Does anyone have a good explanation?
I would be more interested as to why there is so little response from different demographics in the first place, even in Europe there’s little response, except for a few countries.
It seems to me they mostly targeted English speaking countries, which would explain why Japan (and Asia in general) has such low response.
Re: State of JavaScript 2019
#5Sad to see Ionic in the avoid category. Their latest release I thought was quite polished, and I've enjoyed using Capacitor rather than Cordova. I think the key to further success is breaking away from Cordova entirely, and expanding the native features supported in Capacitor. Right now I find myself having to use both due to some things not being implemented in Capacitor yet.
At this point with React Native (or even Flutter if we're considering things apart from JS) there really isn't a compelling reason to build anything in a Webview as far as I know. Also in my personal experience their support team members have been pretty impatient and passive aggressive in the Github issues tickets so I'm not entirely surprised that they're building something that the community has moved away from.
Re: State of JavaScript 2019
#6EmberJS should not be in the "avoid' section.. it is one of the most well thought-out framework which just gets the job done.. and it is a bit contra-indicatory that Ember guys are the highest paid.
Re: State of JavaScript 2019
#7The most interesting data in my opinion are the conflicting opinions on the overall state of the ecosystem:: https://2019.stateofjs.com/opinions/
While there is a sharp downtick of people who think that JavaScript is moving in the right directin, most agree that the overall situation in terms of complexity and velocity is getting better.
I don't have any explanation for this, but would agree: Developing in JavaScript feels easier to me than just a few years ago.
Re: State of JavaScript 2019
#8Something that jumps out to me in the demographics is how few respondents are from Japan (0.6% vs e.g. 5.1% from Germany). Does anyone have a good explanation?
Hmm why would you expect anything else? They do not live in the same Internet bubble as say US/Nordics/Germany.
Re: State of JavaScript 2019
#9Interesting that GraphQL is slowly gaining interest - I kind of thought the hype would fizzle out.
Good to also see Typescript making a foothold - it's a great alternative to pure JS.
Re: State of JavaScript 2019
#10The most interesting data in my opinion are the conflicting opinions on the overall state of the ecosystem:: https://2019.stateofjs.com/opinions/ While there is a sharp downtick of people who think that JavaScript is moving in the right directin, most agree that the overall situation in terms of complexity and velocity is getting better. I don't have any explanation for this, but would agree: Developing in JavaScript…
Maybe by now we're all conditioned to immediately respond with "argh it's moving too quickly" :P
But I totally agree. Things like the various cli tools, widely available documentation and good IDE support for frameworks has made JS a lot better in recent years.