151–160 of 286 posts
Glad to see Svelte [2] starting to get some attention. It’s a true little wunderkind.
[1] https://2018.stateofjs.com/front-end-frameworks/conclusion/ [2] https://svelte.technology
One important data point there is Visual Studio Code. It used to be really popular in 2017 (double the popularity of Atom/Sublime/Webstorm), now it's just eating everyone's lunch (triple the popularity of Sublime/Vim/Webstorm/Atom, almost equal to all of them combined). Also Atom is declining sharply. Compare https://2018.stateofjs.com/other-tools/ to https://2017.stateofjs.com/2017/other-tools/
People are generally happy with the development of JS the trends of always improving languages along with frameworks makes developing with JS makes developer increase in happiness for the third time in a row. ES6 is good, TypeScript is gaining ground, people are moving away from Flow. Angular is dead? Most don't even want to touch it again ( Great ). Ember hasn't moved a bit in three years with a declining of interes…
Loved? Well, it's a point of view. I personally hate it, due to the tooling and the dependency management (npm and yarn are catastrophic, an "hello world" example with React downloads on average more than 100 packages).
People are generally happy with the development of JS the trends of always improving languages along with frameworks makes developing with JS makes developer increase in happiness for the third time in a row. ES6 is good, TypeScript is gaining ground, people are moving away from Flow. Angular is dead? Most don't even want to touch it again ( Great ). Ember hasn't moved a bit in three years with a declining of interes…
> Angular is dead? Most don't even want to touch it again ( Great ). Yet what I see around me is enterprise customers on our projects adopting Angular as the official internal Framework, as React is seem as too advanced.
Once enterprise chooses a tool, that tends to stay the tool for that project, then all of the team is competent in the tool after a couple of years working with it. There's a critical time-frame when new competing tools win a geographical majority [2].
[0] Link to facebook announcing Reach license changes: https://code.fb.com/web/relicensing-react-jest-flow-and-immu...
[1] Link to short article on MIT-Patents license in reack. Takeaway: This has never been litigated before https://hackernoon.com/4-lessons-from-the-react-patent-licen...
[2] Geographical majority http://www.businessdictionary.com/definition/geographic-mono... replace 'place' with 'technology tool'
Earlier quoted context omitted.
well it's certainly better than listening to ranting retrograde gramps "zomg new framework, I have to LEARN again :("
This is a fairly vacuous remark, if I'm frank. The problem isn't that you have to learn another framework (although it does become a problem when they're all slightly similar and they start to meld together after the umphteenth, not to mention that learning slows down with age). The problem is that each frameworks brings along new edge cases, new problems and forces you to reinvent tools you already had for this new…
The state of javascript in 2018 is a dumpster fire. It was a dumpster fire in 2017... it will be a dumpster fire in 2019.
Earlier quoted context omitted.
I find it amusing that your post links to a page which itself doesn't work without javascript. :)
Fortunately there is a direct link to the image there. http://i64.tinypic.com/2v31s94.jpg
The weirdest part of this survey is in many categories, the most experienced developers (and by extension, the highest paid) were using a less popular technology. Over 50% of people surveyed had heard of ClojureScript and were not interested, but the developers who used it and liked it had the highest average years of experience and highest average salary. Same goes for Ember and Polymer for frameworks, and Relay for…
The weirdest part of this survey is in many categories, the most experienced developers (and by extension, the highest paid) were using a less popular technology. Over 50% of people surveyed had heard of ClojureScript and were not interested, but the developers who used it and liked it had the highest average years of experience and highest average salary. Same goes for Ember and Polymer for frameworks, and Relay for…
A junior dev is going to learn ES6, and Vue and/or React because they want a job, but learning Polymer/Ember/Relay/ClojureScript isn't worth the time because there are fewer jobs for it. But a more senior dev has probably maintained a few projects using that tech, maybe surveyed it for use in a new project, etc.
Earlier quoted context omitted.
> TypeScript is gaining ground, people are moving away from Flow. Is it really the case? Both projects are watched and have quite big number of stars in github. I have tried flow and liked it. I have used typescript in the past and I'm not crazy about it. Therefore I would like to get better understanding here. Is there anything I could read about it?
Don’t have to take the survey so seriously. It’s not representative of all JS community. My circle of JS hackers don’t even bother to participate.
The survey can be a representative sample, without including your ̈́"circle of JS hackers". That's how surveys work.