Live data from Hacker News

The State of JavaScript – Survey results

stateofjs.com

211–220 of 357 posts

Re: The State of JavaScript – Survey results

#212

I wish to register my complaint with the term "ES6" which has always been unofficial and refers to the official standard "EMCAScript2015".

I think it's better to address complaints to not so smart decision of renaming well-known and widely adopted terms.

Re: The State of JavaScript – Survey results

#213

Anyone feel like piping in why Aurelia? It pops out in the data, but unknown is satisfaction, etc.

I 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.

Re: The State of JavaScript – Survey results

#214

Earlier quoted context omitted.

For the record, you don't need to use Typescript for Angular 2, you can just use regular JS (or Dart for that matter). The documentation is definitely biased toward Typescript at the moment, but I anticipate the situation improving as the framework matures.

That's technically true, but realistically false. Just like people used to say that you don't need to use JSX to write React. What's the point of using a heavy duty, opinionated framework without embracing it completely? that's just bound to get you into a whole lot of hurt.

You broke my hope to start using React. JSX smells too much for me. But thanks for the info, anyway.

Re: The State of JavaScript – Survey results

#215

It'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 featur…

I suspect that we didn't get enough Ember responders, because I do think they have a reasonable sized community. 9k responses is likely not enough to draw a reasonable conclusion that it isn't popular. I wish we could have paired up npm downloads or some other stat besides some of this data...

Re: The State of JavaScript – Survey results

#216

I 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…

Give Dart a try. It has a single dependency management tool (pub), support for Angular 2, and is generally a joy to use. Material widgets for Angular 2 (the same ones Google uses internally to build Adwords) are expected to be announced at the Dart summit in October.

JSON support is awful, "optional types" means "no types". Thanks, but even TS is better.

Re: The State of JavaScript – Survey results

#217
post #61

Earlier quoted context omitted.

I always thought relay was an alternative to redux

Not really. Relay is mostly designed around querying a backend data store, not updating/managing client-side state.

Relay already is a replacement for Redux. It wraps React components and it has a store. How could you even use Relay and Redux together?

Re: The State of JavaScript – Survey results

#218

It'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 featur…

I suspect that we didn't get enough Ember responders, because I do think they have a reasonable sized community. 9k responses is likely not enough to draw a reasonable conclusion that it isn't popular. I wish we could have paired up npm downloads or some other stat besides some of this data...

Here are some npm download comparisons : http://npmcharts.com/compare/backbone,react,angular,ember-cl...

Trouble is with angular 1 is a lot of people are probably still installing via bower, angular 2 might have a lot of people installing via jspm, elm uses scoped packages which still don't have stats...

Re: The State of JavaScript – Survey results

#219

It'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…

Respectfully disagree--I like Relay better. And Relay 2 is including client-side state, so you don't need Redux. It has a steep learning curve and some initial setup overhead; but from a long-range perspective--I think it will have better performance and code comprehensibility. Maybe Apollo is better suited for freelancers though.

I thought Relay already had client side state? Also what's Relay 2? Where are you finding information about it?

My opinion of Relay right now is that it has way too many needless complications. It looks like it brought a ton of baggage from being used in Facebook that just gets in the way of general use. So I'm interested in an alternative.

However, the real problem with all of this stuff is cache management. Properly managing the cache in the face of mutations is very complicated and it's impossible to be perfect anyway without some sort of pubsub.

Re: The State of JavaScript – Survey results

#220

It'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 featur…

Huh? Why should I use Ember instead of React or Polymer? Does it have a better story for cache management or something?
Post reply on HN