[deleted]
The State of JavaScript – Survey results
121–130 of 357 posts
Re: The State of JavaScript – Survey results
#122Earlier quoted context omitted.
> 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. The better question is: are the apps someone with two or three fewer years of experience than you more modular, etc? My experience is on the backend rather than the frontend, but in that domain, at least, system quality is still way more about developer matu…
I think the problem was the hard-to-maintain lazy way was usually the most obvious. There was so much momentum behind the quick-and-dirty imperative DOM approach that it was hard to do anything else. For example, you could totally use Backbone to construct modular, refactorable views -- but in practice everything would devolve into DOM-munging event-driven spaghetti.
I think one reason why React is so popular is that it forced you into an object oriented approach whereas before many developers used innerHTML everywhere. It is possible to write object oriented, structured "class" based vanilla JavaScript with imperative DOM manipulations though, witch is more performant then popular frameworks.
Re: The State of JavaScript – Survey results
#123Anyone feel like piping in why Aurelia? It pops out in the data, but unknown is satisfaction, etc.
The 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.
Re: The State of JavaScript – Survey results
#124"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.
Re: The State of JavaScript – Survey results
#125I 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…
> somehow JS devs have decided switch statements are bad
huh. You obviously haven't played with Redux yet, it's basically switch statements all they way.
The JS community is the biggest programming community in the world, there is no way you can lump anything on the community as a whole.
Re: The State of JavaScript – Survey results
#126It'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 sp…
(Disclaimer: I work on Apollo)
Yes, it was a bit surprising to see "Apollo" separate from "GraphQL" here, since our primary focus is to enable people to take advantage of GraphQL no matter their frontend and backend architecture.
It makes the most sense to make a direct comparison between "Apollo" and "Relay", but they should both be considered a subset of "GraphQL", which is really the core technology that everyone is building on.
However, excited that people like it, and we're excited to collaborate with everyone to make it the best way to use GraphQL in an application!
Re: The State of JavaScript – Survey results
#127This 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?
I 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 w…
> Web application development is hard
Replace JavaScript with Java in all browsers and make it much easier, dependable, predictable and reliable.
Re: The State of JavaScript – Survey results
#128Side note: The web design reminds me of the late 1990s... funny how it comes around.
Re: The State of JavaScript – Survey results
#129Earlier quoted context omitted.
After using Mobx for a few weeks, I've come to question why anybody would use anything else. It is the only software I've ever used that was created for a dynamic language that has me trying to re-implement in my favored strong/static typed languages. Now I just point and laugh at anybody trying to make sense of their Redux global state atom with a bajillion reducers. So far, I've only found one common objection to i…
I'm really interested in what you're saying about UIs as state machines. Do you have any articles/references to back this up? Genuine curiousity here.
I second that. My experience shows it is a state machine, but I have not see any formal study of it.
Re: The State of JavaScript – Survey results
#130Earlier quoted context omitted.
I 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 w…
> "... 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...
JavaScript has been around since the 90's; a quick scan of this page reveals around 2 dozen JavaScript technologies. The only solution is to remove JavaScript from all browsers and replace it with Java.