28 ms·
The State of JavaScript – Survey results
- FajitaNachos 10y agoI like the stats on the home page. A 53% response rate seems really good.
- Macsenour 10y agoIs it me, or is 89 questions a lot of questions? I wonder if the number of questions cuts down on the response rate. edit: I assume it does, but what is the tipping point?
- tracker1 10y agoI would think that next year, maybe staging into 3-4 different surveys may be a better idea... a month apart even... that way there isn't the drop off on a single survey. I really do appreciate the format though.
- ggregoire 10y agoGlad to see that some stats are the complete opposite of what we usually read on HN about JavaScript. -- > Years of Experience 29% : 2-5 years, 30% : 5-10 years and 23% : 10-20 years "It turns out JavaScript programmers are not all inexperienced jQuery-wielding junior devs." -- > I would like JavaScript to be my main programming language 49% completely agree and 84% agree -- > I enjoy building JavaScript apps 52% completely agree and 94% agree -- > JavaScript is moving in the right direction 40% completely agree and 94% agree
- deleted 10y ago[deleted]
- anamoulous 10y agoI apologize if the predictability of this comment, but I just want to say, I recently started a new gig at a company that has undergone a full on embrace of Javascript for tooling and server side projects and it boggles my mind how much productivity is wasted on this ecosystem. There is an interesting amount of energy put into making asynchronous code read synchronously in situations where asynchronous code provides no benefit. The dependency tree of any one project tends to be incomprehensibly sprawling. Runtime version numbering is... weird. Don't even get me started on the interplay of Gulp, Grunt, Webpack and NPM. ES6 is bizarrely noisy. ESLint fascism is a necessity given the history of legal anti-patterns the language must shoulder. Scoping can occasionally lead to absurdist solutions [1]. I know this is the future and I'm trying to embrace it, but boy does it feel icky doing it. http://stackoverflow.com/questions/33629343/what-is-the-best-way-in-es6-to-assign-a-constant-conditionally http://stackoverflow.com/questions/33629343/what-is-the-best...
- Klathmon 10y agoCould it be that you are still just new to it (in the grand scheme of things)? Because all of those things sound very similar to the complaints I hear from web developers on their first foray into desktop development. There are so many tools it's impossible to know them all (or to even know which one is best to use in which situation), so much legacy code out there it's tough to learn what the "right" way to do things is, it often feels like you are fighting the OS or the language to get what you want how you want it, and dependencies are hard. Application development is hard, and is still far from "solved". And while the "web stack" is far from perfect, I'm personally significantly more productive in it than I ever was in anything else. And in my experience that extra productivity makes better applications because I spend less time just trying to get it working, and more time getting it working well.
- SadWebDeveloper 10y agoI actually thing is the other way around... App Development is solved (unless you want to run the same codebase on multiple OS) but Web Development is a mess now that JS devs are trying hard to put themselves in every layer of the app from the networking layer to the data layer, throwing out the window years of good practices.
- anamoulous 10y agoI'm not going from backend to frontend or desktop apps. I'm going backend to backend. I guess part of my point is I'm made uncomfortable by the encroachment of Javascript into areas where it's not particularly well suited, and the historical baggage it must carry into those areas. It's the when you have Javascript as a hammer, everything looks like a nail issue. I don't think my organization is unique in its embrace of Javascript-everything, either.
- deleted 10y ago[deleted]
- matthewmacleod 10y agoSee, I'm not sure that's the case. When I started writing apps using Cocoa, for example, I had a pretty good experience. Yeah, I fought some of the tooling that I wasn't really used to, but given that it was quite different from my backgrounds in web and embedded development, I was overall quite pleased with how easy and more importantly how obvious everything was. I found this to be the same when I wrote applications in Qt, and also when starting to work with newer languages (like Go). This contrasts very much with the Javascript ecosystem. Despite having been a nominal web developer for approaching a decade, I am still consistently baffled by how difficult it is to get to grips with how everything is put together. There seem to be dozens of different workflows, none of which are entirely compatible with one another. There are bad configuration formats all over. Every tool seems to be broken into 200 different parts that subsequently have to be reassembled in order to implement a working pipeline. Documentation is erratic at best, and so on. I used to feel pretty productive with Javascript, back when the web was a bit more 'Wild West'. But as it has developed as an application platform, it feels more and more like I am fighting the tools, rather than having them help me. That's not a nice feeling.
- sillyquiet 10y agoAs an aside, is there any dev community more prone to this kind of agonized introspection than the JavaScript community?
- epmatsw 10y agoSuper interesting. Lots of data there. Two things that stood out from a quick once-over: Vue is doing better than I expected. PostCSS is less adopted than I expected.
- fahrradflucht 10y agoI don't remember the phrasing of the question but it could very well be that a lot of the cssnext answers use PostCSS as well... That doesn't mean that it has huge usage anyway though.
- irrational 10y agoI just tried Vue 2.0 for the first time last week and I really really liked it.
- clivestaples 10y agoI had a similar experience with Vue about six months ago. I read the documentation and then gave myself an hour with it. By the end of the same day, I had re-factored a very complex dashboard and enjoyed every minute of it. My biggest complaint is that I love React/MobX and Vue which makes choosing one over the other really painful. What a great problem to have!
- Roboprog 10y agoAt least in Angular, I can make a template in a directive for styles, which solves the "put repeated stuff in a variable" problem, without bringing in yet another tool. (use a string for the template, not a file)
- antoniuschan99 10y agoI hope Vue is going to be quite popular. I haven't actually used it but have looked at the documentation and have heard so many people praise it. I have only heard of good things. It just doesn't have the support like Angular or React has from the big Companies.
- nogridbag 10y ago
- savanaly 10y agoGreat job on the interactive presentation.
- sgdesign 10y agoAuthor here, thanks!
- thisisblurry 10y agoI agree; it looks really nice! Minor nit: would you be open to using colorblind friendly color choices in the future? The current colors are pretty hard for me to differentiate between.
- sgdesign 10y agoReally sorry about that! I'll keep it in mind next time.
- meira 10y agoGreat report. I'm very satisfied with Clojurescript.
- bpicolo 10y agoBit weird that the "Web Framework" section didn't have any Clojurescript libs at all considering it was on the list, heh. Re-frame, Om... Mobx looks pretty based on reagent, heh
- grabcocque 10y agoThis seems to suggest the rate of framework churn has rather settled down. Are JS devs finally starting to be satisfied with their current tools and not needing to restart every 18 months?
- Touche 10y agoI don't think the churn has really settled down, what makes you think that? The idea that framework lifespan only lasts 6 months was always exaggerated.
- ng12 10y agoI see this same, tired old meme in every thread about web technologies. It's funny to me that certain people are so disdainful of the churn in web development on a forum dedicated to "hackers". Web application development is hard, and the reason why there's so much churn is because smart, inventive people are constantly finding better ways to do things. Things aren't just resetting from scratch every 18 months. The web apps I'm working on today are way more modular, composable, testable, and maintainable than the ones I was writing as little as two or three years ago. Just because Java systems development hasn't changed significantly in the last 5 years doesn't mean Java devs are any more or less reasonable developers than web folks.
- SeanDav 10y ago> "... the reason why there's so much churn is because smart, inventive people are constantly finding better ways to do things." It also follows that at some point, these smart, inventive people will come up with fairly stable frameworks that are sufficiently flexible and powerful to accommodate most of the problem space out there. It is reasonable to ask if such a point has been reached...
- tracker1 10y agoDepends on the space.. for example, Express has been pretty stable.. Angular 1.x has been as stable as anything else for the most part... Node's mostly been progressive additions, and features from engine updates since 0.10... npm has been pretty stable since node 0.10, though there's been significant advancements since npm 3 came out. Browserify -> Webpack has been noisy. Babel 5 -> 6 equally noisy, but better for moving forward Today, I think webpack, babel, react, redux and fetch cover a LOT of ground for client-side dev. There's a few other bits around that, and I think CSS tooling is starting the a similar shakeup to node's tooling options. In the end, almost all the JS features I care about seem to be at stage-3 now, so who knows when they'll be in the major browsers.
- golergka 10y agoAccording to the survey, 213 people that took it have never head of plain javascript.
- inputcoffee 10y agoGood observation. One possible explanation is they are not sure about what that means. As an example, to me that sounds like the Javascript used in the browser. Is that the same as the Javascript I get from NodeJS? Which is "plain javascript"? I think it represents semantic confusion and not experience. But that is just a guess.
- Aldo_MX 10y agoTo be fair, a side effect of JS Fatigue is the inability to tell whether "Plain JavaScript" is the newest kid on the block or if it really means "good old JavaScript (ES3)". Especially when the headline is "JavaScript Flavors".
- talmand 10y agoExactly, I've seen discussions about vanilla-js.com suggesting that people thought it was a real framework.
- hood_syntax 10y agoPoe's Law, maybe?
- Illniyar 10y agoI thought they were being sarcastic.
- civilian 10y agoPlainJS -- the hot new javascript dialect that transpiles Javascript 1.1 to ES6 so that your coworkers don't have to know that you don't know how the fuck Array.each works.
- zzguy 10y agoI really liked the "features" section. I've seen some weird things done in the wild to obtain some of these features. Like building a multi-SPA to obtain code-splitting where a site is split up into multiple pages each acting as their own SPA. But it does seem like things are settling down. Envious of all the people starting now. As someone who started web dev in 2010, anything I learned that was framework-specific then, is almost completely obsolete now lol.
- Roboprog 10y agoSome interesting things on the "Front End Frameworks" page: * 53% of the respondents used React, and would do so again. * 47% use "No framework", and would do so again. (hmm. that doesn't leave much room, unless you can use more than one tool depending on the situation) * 43% had "no interest" in Angular 2. One other thing to consider, of the "had used X, would/would-not use again" responses: there is of course a lot of selection bias of whether or not to even try X in the first place. ... My only experience with these so far is Angular 1. It's easy to get started with, but does get messy when you have a very large form (think "government work"). I don't have a "React" axe to grind, I'm just looking at the numbers. However, by the time I have to haul in Typescript transpiling, much of the appeal of Angular 1 is lost :-( (it feels like GWT, all over again, at least to some extent)
- Ensorceled 10y ago> (hmm. that doesn't leave much room, unless you can use more than one tool depending on the situation) Or: There are projects that they would use React for AND projects (presumably different) that they would use no framework for.
- morgante 10y agoThe way I read it is that each question is independent. So I can say I've used Angular and would never use it again while also saying I've used React and would use it again. This is really a pretty decisively positive stat for React. Very few of its users would never use it again, while a lot of people have tried Angular and abandoned it. (This certainly matches my experience and anecdotes I've heard in the community.)
- cloverich 10y ago> The way I read it is that each question is independent. Mine as well. I have two active work projects -- one is React, and one is plain Javascript. The latter is to keep the project extremely lean (mobile form single time use type thing) and I've enjoyed using no libraries in it (yet). So I would have responded positively to both of those questions.
- 10y ago
- VOYD 10y agoNice design.
- FrancoDiaz 10y agoES6, CoffeeScript, and TypeScript all have near-perfect awareness, which surprised me since TypeScript isn’t quite as popular as the other two yet. I take issue with that statement. Just anecdotal, but I think these days Typescript is much more "popular" than CoffeeScript
- bryanlarsen 10y agoAwareness just means "have heard of it". 99% have heard of Coffeescript but 14% want to use it in the future. 98% have heard of Typescript but 60% want to use it in the future.
- Roboprog 10y agoIt's got the Microsoft Seal of Approval(TM)! Yeah, doesn't mean much to me, but it does guarantee you can get tools that are compatible with it.
- tomatsu 10y agoAnecdotally, CS appears to have lost quite a bit of popularity while TS gained some. RedMonk seems to confirm these trends. TS grows while CS stagnates: Q1 2016: http://sogrady-media.redmonk.com/sogrady/files/2016/02/lang-rank-944px-wm.png http://sogrady-media.redmonk.com/sogrady/files/2016/02/lang-... Q3 2016: http://sogrady-media.redmonk.com/sogrady/files/2016/07/lang.rank_.Q316.plot-WM.png http://sogrady-media.redmonk.com/sogrady/files/2016/07/lang....
- davidjnelson 10y agoTs seems awesome but it looked like kind of a pain with separate ts and js files, mandatory type definitions not being present for lots of dependencies, and back when I looked at it seeming pretty all or nothing. I like flow. The people that built ts are brilliant too though. Curious if anyone has a good comparison between flow and ts. I've heard ts has improved a lot lately.
- bostonvaulter2 10y ago
- SadWebDeveloper 10y agoNever heard of the survey maybe the data is biased to only approach people on the silicon valley where technologies are used as if they were current season premium fashion cloths.
- joshowens 10y ago9k responses certainly weren't from SV alone. I know alot of the Spacedojo Slack channel took the survey and I think like 2 out of 300 live in SV. Would be fun to maybe turn ip addresses into lat/long and map out where the responses came from...
- SadWebDeveloper 10y agoexactly this is my point, maybe the data is biased to US developers mostly
- inputcoffee 10y agoI appreciate that for the next year when there is a framework war I will have a link to shut it down. Typically a newbie will ask about which framework they should learn. There will be a bunch of "it depends" and "try them out" responses, and then someone will take pity and pick a clear direction based on their experience. Well and good. But this way the newbie can learn from the actual experience of lots of other people. Data, for short.
- mholmes680 10y agoThe same, from my slightly different perspective: I've been away from JavaScript for 3 years, and it is awesome to have a resource to help navigate the way back in, and get the most bang-for-my-buck, so to speak. I can tell here what tech I need to focus on for my pet project, which will also improve my hirability looking forward.
- at-fates-hands 10y ago>> Typically a newbie will ask about which framework they should learn.. Honestly the easiest way to learn this is to contact your local recruiters and ask them to send you some openings for FED positions. In nearly every one, you will see which JS framework is the main one they use. In my recent experiences (the last two or three years) most corporate environments are using AngularJS, while the smaller startups are using React and some mix of various other libraries for their apps and sites. There are still a few agencies I know using BackboneJS, since it was in that first wave of JS frameworks and there's apps and sites out there which still need supporting.
- inputcoffee 10y agoInteresting approach, but I will note that even you have recommended three (Angular, React and Backbone). People generally put forward one of the following: Knockout (easy to learn), Ember, Backbone, Angular, React. Someone will invariably say no, use nothing but plain Javascript at first. This will lead to a little subthread about whether it is fair to include jquery. Every now and then someone will come up with meteor or vue as an alternative.
- 10y ago
- aidos 10y agoI'd love to hear more from people that expressed certain viewpoints - specifically those who used a library but wouldn't use it again... Specifically mobx :) I've played with most popular js libs now and I've found that for my use case I wasn't totally happy for one reason or another. I've been dabbling in mobx for that last few weeks and the ease with which it has allowed me resolve issues in my codebase is really promising. If anyone here is in the 58 people who wouldn't use it again, care to share what you ran in to?
- easong 10y agoI love mobx (definitely not one of the 58), but I would use redux on large apps (maybe, more than 15 pages?), especially if you don't care too much about performance. Redux has better debugging, forces more structure to the code, has a immutable data story, and there are more resources on the net if you need to bring developers up to speed. There are some configuration options for MobX that force the user to be more organized, but redux still feels more structured. That being said, MobX is absolutely my go-to state management library now - it's probably the easiest free FPS you'll find anywhere, it's ridiculously easy to write, and it results in fewer LOC.
- smac8 10y agoSecond that, MobX has been a total game changer for me. Used redux and really like the philosophy of it, but overall feel mobx is much easier to use while accomplishing just as much, and the simplicity and lack of boilerplate actually makes reasoning about state, testing, etc much easier than redux. I disagree about large apps (switched to mobx on a large app now), but I can roughly see what you are saying. Still, I think MobX is great on large apps
- acemarke 10y agoOut of curiosity, why do you say "don't care much about performance"? Redux can be _extremely_ performant, although it does take a bit of thinking about how your data is organized. I've got several articles discussing Redux performance [0] in my React/Redux links list [1]. In particular, check out Dan Abramov's PR to a MobX/Redux benchmark [2], and the article "High Performance Redux" [3]. Finally, the upcoming React-Redux v5 release shows noticeable improvements in a variety of scenarios [4]. Any specific issues with Redux performance that you've noticed? [0]: https://github.com/markerikson/react-redux-links https://github.com/markerikson/react-redux-links [1]: https://github.com/markerikson/react-redux-links/blob/master/react-performance.md#redux-performance https://github.com/markerikson/react-redux-links/blob/master... [2]: https://github.com/mweststrate/redux-todomvc/pull/1 https://github.com/mweststrate/redux-todomvc/pull/1 [3]: http://somebody32.github.io/high-performance-redux/ http://somebody32.github.io/high-performance-redux/ [4]: https://github.com/reactjs/react-redux/pull/416 https://github.com/reactjs/react-redux/pull/416
- andrewmcwatters 10y agoTL;DR: It's alright, everyone guesses.
- triangleman 10y agoI wish to register my complaint with the term "ES6" which has always been unofficial and refers to the official standard "EMCAScript2015".
- BinaryIdiot 10y agoSame. ECMA changed to using dates a while ago and people are still saying "ES6" and "ES7". I've also seen people refer to all new syntax and features as "ES6" including things that in ECMAScript2017. Honestly though I think ECMA has some of the blame for this. I don't think they do a very good job communicating changes and versioning.
- DarkTree 10y agoYeah I think there is just a lot of friction when moving from the concise "ES6" to the lengthy, and somewhat awkward "ECMAScript2015". The fact that so many people still use the terms ES6 and ES7 gives others even less incentive to use the official naming scheme. Hopefully, it will iron itself out in the future.
- joshowens 10y agoWhat did ES5 change to then? I never heard. Honestly, ES2015 just seems odd to me.
- cloverich 10y agoI think its not just the length but the concept: Every other language has a normal looking version (Rust 1.12 announced! Java 8, etc). They had that with ES3, ES5, ES6, then decided (perhaps for very good reasons) to change to a unique (?) version scheme.
- slavik81 10y agoC and C++ also use years. For example, C99 was standardized in 1999. C++11 was standardized in 2011.
- 10y ago
- morgante 10y agoIt's nice to see some love for Apollo here. It's leagues better than Relay and has definitely been the biggest boon to my development stack in a while. That being said, the article should make it clearer that Apollo is perfectly usable just as a frontend client—you don't have to adopt the backend at all. The Meteor team really deserves commendations for learning from some of the mistakes in building Meteor. Apollo specifically emphasizes incremental adoptability: you can drop it into an existing project and see benefits almost immediately, without having to refactor/rewrite any of your existing code. I'd also like to provide a counterpoint to the inevitable complaints about the complexity and low-productivity of a JavaScript. In my experience, once you've paid the initial cost of learning these tools you can become extremely productive. As a freelance developer who is paid a flat rate for projects, I'm directly incentivized to find an efficient stack and the modern JavaScript stack is definitely it. Specifically, my stack these days is Django + Graphene + React + Redux + Apollo. It's insanely high productivity: I can usually have the basics of an app built within a few hours of starting.
- k__ 10y agoI always thought relay was an alternative to redux
- morgante 10y agoNot really. Relay is mostly designed around querying a backend data store, not updating/managing client-side state.
- jameslk 10y agoRelay v2 will bring with it a way to manage client side state.
- morgante 10y agoInteresting. I didn't know that. If anything, that actually somewhat affirms my preference for Apollo. Since Apollo is built on top of Redux, you can use both in tandem without any problem instead of having to learn a whole new tool and refactor your application to use it.
- vlunkr 10y agoFor the life of me I can't understand why webpack has become the de facto build tool. It's so much more complex than anything else I've tried. I understand it's supposed to be faster, but still, I wouldn't bother with it until your build times actually start to become a nuisance.
- deleted 10y ago[deleted]
- fenomas 10y agoI don't think webpack is best considered as a build tool. It's primarily a dependency wrangler - it lets you define entry points, which can declare arbitrary dependencies on assets, which can then declare their own dependencies, forever and ever, and webpack will wrangle all that into a single JS file, a single CSS file, or whatever it is you need. As it happens one can also do build-tool stuff (transpiling, prefixing, etc) on the resulting files, but that's not where the magic is.
- djokkataja 10y agoI switched from browserify to webpack when I started writing ES6 on the client because the browserify build times with ES6 were slow enough that they felt disruptive to my workflow (somewhere between 10-30 seconds, I don't remember the exact amount). I'm not sure if that's improved now for Browserify, but it's the kind of thing that you're not likely to switch back from once you have a working setup.
- dwaltrip 10y agoI use watchify [1] for incremental builds. The initial build is still long (10 - 30 seconds, as you said), but with each change after that the build updates in < 1 second. [1] https://github.com/substack/watchify https://github.com/substack/watchify
- tboyd47 10y agoWebpack got swept along in the React zeitgeist. Few people who use it really take the time to understand it. It's a pretty slow way to build a project, but that's actually not the main sell. The main sell is in smart asset chunking, and it's pretty darn good at it. That alone earned it a place in my skillset.
- labrador 10y agoI would respect the JavaScript so much more if there wasn't so much faddishness - somehow JS devs have decided switch statements are bad, indenting with 2 spaces is the only way to go, semi-colons should be banished and "boilerplate" code should be hidden in libraries the magically wipe it away so your code looks "clean," if barely understandable without reading through a bunch of libs. Edit: forgot to add that these are my initial impressions after diving into front end development with node and browserify. I ended up avoiding a lot of pain by just using TypeScript and a make file. Who has time to wade through umpteen million build systems?
- BinaryIdiot 10y ago> somehow JS devs have decided switch statements are bad Nonsense. Though sometimes using an object can look cleaner depending on your use case. > indenting with 2 spaces is the only way to go I love 4 spaces and I use 4 in my JavaScript projects. Just because you've seen some subset of people use 2 doesn't mean it's the majority, what you have to use, etc. > semi-colons should be banished Absolutely, positively NO. Semi-colons are a requirement of the language. Some people elide them, incorrectly, because the JavaScript engines are good enough to still handle it. In my experience being playing a limited part in open source JavaScript eliding the semi colon seems to be a rarely done practice. Regardless it's incorrect no matter how you slice it. > "boilerplate" code should be hidden in libraries the magically wipe it away so your code looks "clean," This sounds more like a rails-ism than a JavaScript-ism. Though you'd be hard pressed to find libraries without implicit behaviors in every language. Some people take DRY way too far. This point just seems more anecdotal than anything else. > a make file. Who has time to wade through umpteen million build systems? A lot of JavaScript devs use make. Nothing wrong with that.
- labrador 10y agoI'm heartened by your comment. I'm glad to be wrong on this.
- Roboprog 10y agoI think the semicolon requirement is more for broken minifiers than actually making the unpacked code clear/correct. But that's just me, I guess, as I have worked with many line oriented languages, and have no reverence for C syntax.
- pauljaworski 10y ago>Overall, developers are not happy about JavaScript testing. This is because of the low percentage of devs in the survey who have used Jest. I can't begin to describe the joy of finally finding a JS test utility that just works and doesn't require a giant configuration file. If you aren't using Jest, make the switch now! It's likely a lot of your existing tests will work with Jest.
- timdorr 10y agoTotally agree. Just switched to it on Redux and this was all that was involved: https://github.com/reactjs/redux/pull/1951/files https://github.com/reactjs/redux/pull/1951/files Most of that is just find-and-replace kinds of changes. But we dropped 3 dependencies to one and sped everything up in the process. It's just a fantastic tool! I finally feel like I've got a good Rspec equivalent in the JS world.
- pauljaworski 10y agoI noticed that! I often refer to the Redux docs for examples and was glad to see you had also switched to Jest. You guys have some of the best documentation around, by the way. I wish you did the docs for Flow and Immutable as well! They could use some major improvement.
- solidr53 10y agoI used Jest early on, it was nice, but I quickly started to encounter problems related to how new it was. It's way better now, so maybe I will switch back to Jest from enzyme.
- crucialfelix 10y agoThe only things I found really annoying ... Completely disappeared in the last major update. Very clean to work with now.
- cpojer 10y agoYou can use Jest together with enzyme! We posted a big community update together with Jest 16 which should highlight a bunch of ways that you can test with Jest. https://facebook.github.io/jest/blog/2016/10/03/jest-16.html https://facebook.github.io/jest/blog/2016/10/03/jest-16.html
- z3t4 10y agoMore info about the participants would be nice. How where they chosen ?
- leshow 10y agoGives me hope for Elm, there are a lot of potential converts out there.
- inputcoffee 10y agoSo interesting I am still looking at it. Suggestion: Add an optional section on how the developer learned the technology I think you could do a really interesting meta-analysis where you could see a relationship between the way things were learned and the popularity of the tool. It would also be a great resource for people looking to learn a technology and want pointers on where to start.
- arxpoetica 10y agoAnyone feel like piping in why Aurelia? It pops out in the data, but unknown is satisfaction, etc.
- Illniyar 10y agoThe lead developer was involved with angular 2, and basically left to develop Aurelia because he did not agree with the way angular 2 eventually went with. Mostly it's a different take on the next step for Angular that many Angularists that are unhappy with how angular 2 turned out are putting hopes in.
- FrancoDiaz 10y agoMy first entry into the SPA world was Aurelia about 10 months ago. So my experience is colored from having to learn a whole bunch of new things - gulp, SystemJS/JSPM, npm, the "terminology" of SPAs, fighting Typescript declaration file issues, incomplete libraries like Validation, etc.. The Aurelia community on Gitter is outstanding. Just really helpful and friendly. I would have been in big trouble without them. I had actually done research on React, Angular 2 (still in Alpha), and Aurelia before I started the SPA. React seemed to weird and foreign to me a the time, and not enough of the community seemed to want to do React in Typescript which I had settled on as my front-end language. Probably the only reason I chose Aurelia over Angular 2 at the time was because it was painful to do dynamic, data-driven, components with Angular 2 at the time. Aurelia is probably the best of breed in the Model-ViewModel world. It's post 1.0 now. That said, I've just finished my second app in React, and my third app is going to be in React too. I just find composing UIs in React to be much more natural because you're using JavaScript instead of stringy expressions in attributes to say generate list items.
- nxtrafalgar 10y agoI also wrote my first SPA in Aurelia this year. As an introduction to the Javascript world, it has been pretty good (though I would never use JSPM again). Bugs are fixed in a timely fashion, the developers are responsive, and overall my developer experience has been positive.
- 10y ago
- deleted 10y ago[deleted]
- ahunt09 10y ago"the thing that stands out right away is how the React row just lights up compared to the other front-end frameworks. In other words, React users are more likely than average to have experimented with multiple other technologies." I believe the data wrongly indicates this because React, Redux and Webpack are used together to achieve things that both Angular 2 and Ember solve similarly internally.
- rajington 10y agotrue, but i think even a lot of the other non-coupled technologies have higher numbers, but it's hard to say if that's higher percentages
- wiremine 10y agoSide note: The web design reminds me of the late 1990s... funny how it comes around.
- nkassis 10y agoNoticed that under build tools, JSPM wasn't mentioned. Is it no longer popular? I've had a ok experience using it and systemjs been pretty good so far to get es6 module support and typescript working. I guess JSPM wouldn't fit quite in the build tool category but I see no dependency management section.
- andrewmcwatters 10y agoIt was never popular.
- shados 10y agoJSPM never picked up. Its call to fame was that it was more "future proof" using standards that were not actually standard, and had a pretty bad take on pre-building vs building in the browser and stuff. It was slow (and the ways to make it fast were very clunky) and generally, tools focusing on node/NPM entirely ended up winning out.
- xtiansimon 10y ago"It would also be a great resource for people looking to learn a technology and want pointers on where to start." Second that comment. It strikes me as a brilliant that open-source programming languages should have these sorts of statistics. I wish I could see every OSS language reported like this...hmmm. I would replace the stock market ticker in my phone with that!
- xirdstl 10y agoThis year's "Used it before, would use again" is next year's "Used it before, would not use again".
- brlewis 10y agoI don't have time to go into details at the moment, but I'm using, loving and recommending Mithril.
- dandare 10y agoWhat is meant by "Real-Time Operations"(http://stateofjs.com/2016/features/ http://stateofjs.com/2016/features/)? The description could not be more vague and Google does not know either.
- dvlsg 10y agoI assumed they meant something like websockets or server sent events when I took the survey.
- OhSoHumble 10y agoIt's really unfortunate that so many people aren't interested in learning Ember. I just started an internal IT tool in Rails and Ember and I'm really enjoying the simplicity of it. I want something that is easy to understand, easy to setup, and won't change for a while. I became more interested in Ember when I read something online about how they are focusing on stability in the long term instead of a bunch of features. There are also a couple of tools for "just get it hooked up to rails, stupid" that helped me move quickly. As a simple, simple guy - I really prize the "hey stupid I set it up for you" command line tools that give me a starting point. Then I can figure things out as I go along by making small, simple, controlled changes. This is in strong contrast to something like Elm. I have played around with Elm a bit but it's hard to wrap my head around some of the concepts and setting it up with the back-end frameworks that I'm familiar with has been meh. It's also changing rapidly so trying to figure out the concepts by looking at real world examples doesn't help because of a changing language specification. Going from changing the state of a counter to building out a larger application has been somewhat difficult for me and I feel overwhelmed every time I try to start a small project with it. I'm chipping away at that with an Elixir/Elm project, however. But the overall point is that progress is slow because it's such a different way of doing things and I get this gut feeling that I'm drifting away from KISS principles. I'm not a front end developer at all. I'm a systems engineer who dabbles in web application development because it's fun and allows me to build some nice internal tooling for other teams. However, because I don't have that deep web experience I tend to gravitate towards the "old but still good" concepts and frameworks. I'm much more likely to reach for jQuery and server side rendered templates than I am for React or whatever amalgamation of libraries that require an overcomplicated build tool.
- fatbird 10y agoVirtually every JS tool/lib/framework sells itself as "simplifying" something, and they usually do. It's the overhead of constantly simplifying that's murdering our productivity.
- OhSoHumble 10y agoI think it depends on how you quantify "simple." If you refer to simplicity as a small framework or library with very little moving parts, e.g react or sinatra, then that's one way to arrive at a definition. However, complexity in a designed problem arises when you need to take a large variety of 'simple' components and mesh them together to solve a problem. In this context, I'm defining simplicity as low barrier to entry and/or easy to understand ideas. I think of myself as a fairly average developer; that I'm not wholly intelligent or skilled. I want a framework that bosses me around and tells me what to do. Accomplishing simple tasks like mapping JSON returned from Rails to Ember routes and rendering that data into a table was very easy for me to understand and do. The simplicity I'm talking about was the setup, generation, and mechanics of the process. Ember, as another commenter pointed out, is not simple internally. It is glued together using evil magicks as far as I'm concerned. But I'm happy about that because when something does break, it means that I'm doing something that is going against convention or that something is truly broken. As far as the former, then I need to learn the convention. For the latter, then I need to post questions in forums, hit up IRC, etc. But the positive aspect about the second process is that my project is already fully set up and I'm comfortable with my framework enough that I don't feel completely out of water.
- novaleaf 10y agoWhy no section on server-side frameworks? I for one picked Hapi over Express a couple years ago and have been very happy with the switch. I'd love to know what has changed since then!
- platz 10y ago213 people put "never heard of it" for plain javascript
- soared 10y agoThats a surveyor because it sounds like an actual javascript flavor. CoffeScript, Plain Javascript, TypeScript are all flavors.
- carapace 10y ago(Thin sans-serif grey body text means you hate your readers.) ----- edit: I've tried to read it now and this site is crappy as hell. Does anyone have a link to a coherent write-up of these results? ----- Furthermore, I know it's bad form to mention your own downvotes but I dare you I DARE YOU to make a case for that horrible font choice. You can't because it's pure vanity. Style over substance. Thhhpppppt!
- bcheung 10y agoOne thing I have noticed over the years is that the front end community is becoming more and more a "let me google how to do it" kind of community. The tooling ecosystem is so burdensome. Just to get a hello world app with React, Redux, Webpack, esLint, and ES6 takes forever. Sure there are starter boiler plates but they all don't seem to do quite what you need. Before it felt more like a solidly engineered app, now it feels a lot more like glueing various snippets from StackOverflow together. I'm also finding the overhead from React / Redux very noisy. I have to do so much typing and define the same thing over and over across a bunch of different files just to do something simple. I really like how Elm basically implements all of this with much cleaner syntax and works out of the box. It's too bad it doesn't have as much community behind it. I'd like to use it more but find it doesn't have enough community for me to consider using it for anything outside of home projects.
- fbonetti 10y agoI'm not sure why you've been downvoted. I absolutely LOVE that Elm simplifies the boiler plate of a front-end app. Instead of needing a dozen different packages and tools, you basically just need the Elm core library and you're good to go.
- ng12 10y agoI would only use React/Redux for a complex app that's going to be touched by a lot of people. That's where it really shines. Elm is a non-starter in these situations -- I can't seriously propose it for a project because the learning curve is astronomical. Also, I think simple Hello Worlds are a dangerous thing. They convince you that a tool solves all your problems until three months later when you notice your foot's been blown off.
- gjolund 10y agoThe learning curve is a weekend of reading. Elm is much SIMPLER than js, but not as EASY for you because it is new. If you are at all familiar with compilers, types, and functional programming it should all be review anyways. If not then you are missing a big part of your education and I would question your capabilities as a programmer.
- ufmace 10y agoNice article. I started a new hobby Rails project a couple of months ago and was a little surprised to see that even Rails 5 still defaults to Coffeescript. Googled around a bit and decided to drop it, as it seems to be more or less abandoned these days, which this survey seems to confirm. I wonder if/when Rails will switch to ES6 or something?
- inimino 10y agoCoffeeScript was designed by and for Rubyists, so it makes sense that they'd be the last to drop it.
- deleted 10y ago[deleted]
- jaequery 10y agoAfter trying out Vue.js, I am pretty sure I will never go back to React.
- pacomerh 10y agoNever say never. Thats what I thought when I first used Backbone
- tiglionabbit 10y agoThis makes Firebase look wildly popular. But can you even use Firebase for an app where you don't trust every user to maintain your denormalized indexes properly? I asked this question on Stack Overflow to not much response: http://stackoverflow.com/questions/39800531/collaborating-with-malicious-users-in-firebase-is-denormalization-up-to-the-cl/39805623 http://stackoverflow.com/questions/39800531/collaborating-wi...
- adjkant 10y agoAs someone who doesn't work incredibly often with Javascript but has dabbled with MEAN and extensions of MEAN, I found one of the last questions a bit biased in its results: "I would like JavaScript to be my main programming language" (Rate 1 to 5) 49% (5) 35% (4-3) 16% - (2-1) If you've taken this survey, it means that you have done at least a decent amount of work with Javascript. Chances are, you have at least enjoyed something about it so far, or are absolutely required to use it for some reason. Of course many current Javascript users want it to be their main programming language. I love this survey for so many reasons, and this is an incredibly small point. Personally, I think that a good Javascript tool, framework, flavor, whatever, should be able to easily integrate with other technologies. I really enjoyed Angular for that reason (yet to dive into React). I think the idea of "JAVASCRIPT EVERYWHERE" is just really unneeded. Yes, we are stuck with Javascript as a language. Yes, it should be more than a simple afterthought on top of other tech. Making Javascript better and safer doesn't mean you have to do it everywhere, because ubiquitous Javascript doesn't matter if the different dependencies are completely different anyways. The last part is only my opinion, but I wanted to add it because I think the survey's nature is going to exclude many people with it.
- tolmasky 10y agoIts interesting because the reason I think "JAVASCRIPT EVERYWHERE" is valid is because I think "EVERYTHING EVERYWHERE" is valid. Don't get me wrong, some languages are incredibly domain specific and don't make a tremendous amount of sense at all parts of the stack (and some parts of the stack should have domain specific languages), but JavaScript is a general purpose language, that has some interesting things to offer different domains (whether it be server development, app development, etc), but most importantly... SO DO MOST OTHER LANGUAGES! I would love a world where I could choose from most general purpose languages for most tasks. I haven't found many reasons other than "why?" for being against JavaScript being everywhere. I know that if I was a Ruby guy I'd certainly like it if I could use Ruby in as much of the stack as possible, and I think that's totally reasonable. For example, I applaud transpile-to-JS languages so that you can use a language of your choice for the browser (vs thinking "why do we need Clojure everywhere!").
- DonHopkins 10y ago
- cstrat 10y agoI love Meteor and hope that it continues to grow! I've been using it since well before v1.0 and can understand peoples frustration around it. A lot of patterns and core themes have come and gone. Allow/deny, blaze, and now it is sounding more and more like mini-mongo might go the way of Blaze in lieu of Apollo. Like I said though, I really do hope that the core values of Meteor stick around in the framework and it continues to grow. I love it :)
- increment_i 10y agoFor me, the beauty of JS was in its simplicity - there were wacky edge cases for sure, but here was a C-like language that you could use to build a project that almost anyone could understand. When Node first came out I was over the moon - wow, I can run processes on the machine from JavaScript?! Unreal. It seems like I'm constantly keeping up with the complexity of the ecosystem, which is taking a toll on my productivity. This is probably my problem more than any specific failing of the evolution of the language, but, I like to ship. Just my 2 cents to the discussion.
- bbcbasic 10y agoI don't get this. You are not forced to use ES6 features or ReactJS if you don't want to. Just like you can use vanilla PHP, should you desire.
- nine_k 10y agoA "C-like language" is a very dubious compliment. Fortunately, JS is built around a different core. Unfortunately, it's built as haphazardly as C has been.
- increment_i 10y agoWhat I mean is that its syntax is classical. Its constructs will be very familiar to those who have taken basic education in modern programming. As far as your 'different core' argument I'm not too sure what you mean. If you're a Node dev, then JS is just your means of calling OS routines and giving work to threads (in C under the hood, to be sure). If you're a front end person, then JS is a very high level layer again, making calls various OS services, probably in C++ or C.
- Roboprog 10y agoI'm pretty sure the "core" reference refers to the "FP with OOP" core based on Scheme and Self, which is one of the best things about the (JS) language. Alas, "The Management" demanded that it be dressed up to look like Java (and thus like C++). This led to a bunch of people that were unhappy that Javascript was in fact NOT like Java when they tried to use it like Java. It's a very nice dynamic FP language, but people keep wanting to do static OOP with it :-(
- foo101 10y agoWhy are ES6 and JavaScript treated separately in this survey? I thought ES6 is just a new version of JavaScript (the ECMAScript standard)? I thought both are written using the same HTML <script> tag. Why is it necessary to consider ES6 different from JavaScript in this survey? Could you please throw some light on this?
- Aldo_MX 10y agoWhy shouldn't it? You still need to transpile ES6 to ES5
- foo101 10y agoThanks for the answer. I was not doubting the survey methodology or results. My question was simply out of curiosity. I would like to request more details on your answer. 1. What kind of ES6 requires transpiling to ES5. I mean, I once tried using Promise and something like Promise.resolve("foo") works just fine. Are there any ES6 constructs that would require transpiling, to work fine on, say, Chrome or Firefox? 2. Is ES6 not completely backward compatible with ES5? If yes, I would consider ES6 as the same (although upgraded version of) language as ES5. If no (e.g. Python 2 vs. Python 3), then it would be justified to consider ES6 to be different from ES5. What's your opinion? Disclaimer: I am not a JavaScript developer. I am a system programmer. But I do a little bit of web-designing once in a while, for example, to maintain my blog etc. That's why I would like to understand why ES6 is considered a different language than ES5.
- SiVal 10y agoHere's a little bit for you. Most people prefer the semantics of `let` to `var` for variable declarations in JavaScript. It's how JavaScript should have been designed from the start. It has been officially standard for a year or two and became available in some browsers even earlier. I want to use `let` (and `const`) for everything and never use `var` again, but I couldn't even do that on my own PRIVATE website (for me alone) until today, because I didn't upgrade my iPhone to iOS 10 until last night, and iOS Safari never supported `let` (or arrow functions or so many other things) before v10 (and Apple won't allow anyone to break their browser monopoly on their platform). I could just use Android, but I can't switch everyone else to Android, and LOTS of Android and Windows (and even Mac) users are stuck with even older browsers, because they don't know how to (or can't) upgrade. Are there any ES6 constructs that would require transpiling, to work fine on, say, Chrome or Firefox? Not on the latest Chrome or Firefox, but that hardly matters in a world where so many people aren't using the latest Chrome or Firefox. The question for a developer is not whether some in their market can run their software but whether some CAN'T. Is ES6 not completely backward compatible with ES5? It is (in practice) completely backward compatible, but I suspect you are a little confused about what that means. It doesn't mean "forward compatible". Backward compatible means that a new ES6 browser is still compatible with old ES5 code, which it is. Old ES5 code will keep working. It does NOT mean that my new ES6 code, full of `let` and arrow functions will run in an old ES5-only browser, and there are still plenty of them out there. As long as you choose to target a market that includes ES5-only browsers (and you may or may not, but if you do), the things that are new in ES6 (Google "what's new in ES6") have to be transpiled to ES5 to run in ES5-only browsers.
- jack9 10y agoWhen I finally ended on the IDE page, I realized how the vast majority of these "5-10"+ year veterans were very primitive developers. If you're using Sublime or Atom for Javascript development, I would say that you've spent too long working in and around these ever-changing tools without a useful IDE.
- erikpukinskis 10y agoI'm happy coding in WordPad, GEdit, etc, and use Sublime today. My view is that if you need an IDE to maintain your code effectively; if your volume of edits is such that macros and navigation tricks make a meaningful impact on your pace of development, then your code probably has serious architectural problems¹. You see all impediments to action as debilitating, but I think impediments, carefully curated, can provide useful constraints on my development process. Friction helps me see where my interfaces are getting strained. ¹ I feel bad writing this because I know, if I step back from my own preferences, that your approach to development probably works great too. But your claim was so insulting, I'll leave this as is to match your tenor.
- aws_ls 10y agoIts a great and useful survey. But would have liked to see a question(if not a complete section) on search engine optimization(SEO). Most important thing for internet apps. For enterprise apps it doesn't matter and for that you can safely use a framework like React. But its very crucial for Internet apps. Surprisingly, Google neglected building tools in that area, apart from guidelines via its webmaster blogs.
- zkhalique 10y agoI am going to mention our framework, since I think it's relevant, but it's not just a JS framework. It's a fully integrated platform: http://qbix.com/platform http://qbix.com/platform http://qbix.com/platform/features http://qbix.com/platform/features Would like to get some feedback on it, from anyone who looks through the features.