Glad to see lots of satisfied developers of Svelte as I am one. TBH though didn't expect to see it up there this quick.
State of JavaScript 2019
41–50 of 372 posts
Re: State of JavaScript 2019
#42Do other languages do these types of surveys? e.g. is there a "State of Python 2019"?
Re: State of JavaScript 2019
#43So sad to see Meteor solidly in the avoid quadrant, but it seems deserved. Meteor is what I learned how to do web development with back in 2015, and it was fun . It didn't take much to make stuff happen, and the baked-in live sync was like magic. I'm still eager to whip Meteor out for proof of concept prototyping because of how convenient it is to have a schemaless database and a framework that abstracts away HTTP, b…
Survey author here, it's all the more ironic considering all these 21k responses were collected through a Meteor app ;)
Re: State of JavaScript 2019
#44Do other languages do these types of surveys? e.g. is there a "State of Python 2019"?
• Go 2019 — https://blog.golang.org/survey2019 (survey only)
• Go 2018 — https://blog.golang.org/survey2018-results
• Go 2017 — https://blog.golang.org/survey2017-results
• Go 2016 — https://blog.golang.org/survey2016-results
• Rust 2018 — https://blog.rust-lang.org/2018/11/27/Rust-survey-2018.html
• Rust 2017 — https://blog.rust-lang.org/2017/09/05/Rust-2017-Survey-Resul...
• C++ Global Insights 2019 — https://isocpp.org/files/papers/CppDevSurvey-2019-04-summary...
• C++ Global Insights 2018 — https://isocpp.org/files/papers/CppDevSurvey-2018-02-summary...
• StackOverflow Insights 2019 — https://insights.stackoverflow.com/survey/2019
• StackOverflow Insights 2018 — https://insights.stackoverflow.com/survey/2018
• StackOverflow Insights 2017 — https://insights.stackoverflow.com/survey/2017
• StackOverflow Insights 2016 — https://insights.stackoverflow.com/survey/2016
• StackOverflow Insights 2015 — https://insights.stackoverflow.com/survey/2015
• IntelliJ, Dev Ecosystem (All) — https://www.jetbrains.com/lp/devecosystem-2019/
• IntelliJ, Dev Ecosystem (Java) — https://www.jetbrains.com/lp/devecosystem-2019/java/
• IntelliJ, Dev Ecosystem (C) — https://www.jetbrains.com/lp/devecosystem-2019/c/
• IntelliJ, Dev Ecosystem (C++) — https://www.jetbrains.com/lp/devecosystem-2019/cpp/
• IntelliJ, Dev Ecosystem (C#) — https://www.jetbrains.com/lp/devecosystem-2019/csharp/
• IntelliJ, Dev Ecosystem (Go) — https://www.jetbrains.com/lp/devecosystem-2019/go/
• IntelliJ, Dev Ecosystem (Javascript) — https://www.jetbrains.com/lp/devecosystem-2019/javascript/
• IntelliJ, Dev Ecosystem (Kotlin) — https://www.jetbrains.com/lp/devecosystem-2019/kotlin/
• IntelliJ, Dev Ecosystem (PHP) — https://www.jetbrains.com/lp/devecosystem-2019/php/
• IntelliJ, Dev Ecosystem (Python) — https://www.jetbrains.com/lp/devecosystem-2019/python/
• IntelliJ, Dev Ecosystem (Ruby) — https://www.jetbrains.com/lp/devecosystem-2019/ruby/
• IntelliJ, Dev Ecosystem (Rust) — https://www.jetbrains.com/lp/devecosystem-2019/rust/
• IntelliJ, Dev Ecosystem (Scala) — https://www.jetbrains.com/lp/devecosystem-2019/scala/
• IntelliJ, Dev Ecosystem (Swift & Objective-C) — https://www.jetbrains.com/lp/devecosystem-2019/swift-objc/
Re: State of JavaScript 2019
#45Do other languages do these types of surveys? e.g. is there a "State of Python 2019"?
No, because these languages aren't broken and don't need a new ECMAscript standard every year (none of which can fix JS anyway because it's fundamentally wrong and unfixable). Other languages don't have a bunch of busybodies adding useless features to a broken language without any hope that all browsers ever will fully support it.
Re: State of JavaScript 2019
#46Earlier quoted context omitted.
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.
Except they excluded the country with the highest English language proficiency on the continent of Europe, the Netherlands. I suspect there’s another reason.
(Survey author) The Netherlands doesn't have a large population, so it's never going to show up as a large part of the results. For next time it would be interesting to also let you toggle a relative view of participation vs population though.
Re: State of JavaScript 2019
#47All the content aside, I just want to say that the presentation in State of JavaScript is magnificent. Some of these charts are superbly designed.
Re: State of JavaScript 2019
#48Sad 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.
I've tried Native with a Kotlin, Flutter, and Ionic 4 with Angular and then Ionic 4 again but with Stencil. Out of all of them I'd probably gotten the farthest with Ionic 4 + Angular but I wouldn't recommend either of them.
Right now I'm trying no framework approach to make a web app with intension on using Cordova or Capacitor to hook into native Tensorflow.
Re: State of JavaScript 2019
#49The state of Javascript in 2019 is that it should be deprecated. I have never had more problems, undefined behavior, mysterious errors and malfunctions, dependency hell and generally shitty syntax as when dealing with Javascript. God, please, just destroy this language. The web needs something different, something not broken and flawed.
Re: State of JavaScript 2019
#50Earlier quoted context omitted.
Probably because a lot of people have been working with it for a long time (like you). I think I started 20 years ago - but I just learned like 40% of css grid this past weekend. (I've been a happy flexbox user for a few years) But I know what you're saying. I also noticed a few percentage points of people saying they have 20+ years or React experience at this point.
The `20+ years` demographic refers to 20+ years of JavaScript experience, AFAICT.
I had the same misunderstanding, thanks for pointing that out