Live data from Hacker News

The State of JavaScript 2018

2018.stateofjs.com

141–150 of 286 posts

Re: The State of JavaScript 2018

#141

Earlier quoted context omitted.

> Angular is dead? Most don't even want to touch it again ( Great ). I don't get the Angular hate. I work with it daily and seems like a productive environment. I did some tests with React and Vue too and couldn't find any relevant advantage. Angular has batteries included tools for a lot of tasks: i18n, routing, isomorphic builds, web components, etc.. You get a cross platform mobile development environment too usin…

One major reason is that Ng is its own thing. It's not JavaScript, nor HTML. Also, "batteries included" means buying into the whole monolithic framework. The React ecosystem requires more decisions, but also benefits from ability to pick and choose the right libraries for a given project. That said, Angular has some great parts, eg TypeScript and RxJS.

I think people will grow "hating" React because of the ease of use. Just like JS and PHP.

I weep for the people that will maintain all the React mess that is being created. React is great, but the current ecosystem has too much liberty for too many junior dev using it.

Angular being a framework has a lot to offer in term of maintainability and good practices.

Re: The State of JavaScript 2018

#142
post #103

Earlier quoted context omitted.

as someone who tried Angular and was so relieved with the simplicity of React, I have no idea how they can come to that conclusion. But then again, I'm not very well know with the field of enterprise customers

React requires too much FP concepts for the typical average enterprise developer. It feels like doing Haskell with JavaScript.

You can write haskell style in any language. but you don’t have to.

function MyComponent(props) { return

Hello {props.name}

}

Re: The State of JavaScript 2018

#143
post #18

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

What's 'catastrophic' about Yarn?

Re: The State of JavaScript 2018

#145

Earlier quoted context omitted.

> So both have been growing at a similar pace. Don't know if you can compare these numbers that easily: one increased their userbase by 12%, the other by 45%.

I think that measuring relative numbers would make sense if we assume exponential growth. But looking at 2016,2017 and 2018, it seems to be rather linear: https://2018.stateofjs.com/front-end-frameworks/vuejs

Fair point. I genuinely wasn't sure how to best compare it (also, I'm sure that growth slows down once a majority of users is awawre of your product, further muddying the picture).

Re: The State of JavaScript 2018

#146

Earlier quoted context omitted.

I think that measuring relative numbers would make sense if we assume exponential growth. But looking at 2016,2017 and 2018, it seems to be rather linear: https://2018.stateofjs.com/front-end-frameworks/vuejs

Fair point. I genuinely wasn't sure how to best compare it (also, I'm sure that growth slows down once a majority of users is awawre of your product, further muddying the picture).

Agreed. If I was to place a bet on which framework will grow faster over the next year, I would pick Vue.

Re: The State of JavaScript 2018

#147
post #18

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…

Regarding GraphQL, I think the reason is at least partially that there aren't too many applications that actually benefit from the all-dynamic approach of it. It's neat and useful in certain applications, but I wouldn't use it everywhere. The tooling isn't quite there yet also in my opinion, but the friction will probably go away with time.

I agree that the dynamic querying aspect of it isn’t useful in most apps but the way graphql simplifies your API (and maybe your state management) compared to REST is by itself, I think, worth it. Tooling seems to be ramping up quickly but I agree, isn’t there yet.

Re: The State of JavaScript 2018

#148
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 data store. I'm really curious what the reasons for this are.

Re: The State of JavaScript 2018

#149
post #137
post #63

The State of JavaScript 2018 is inaccessible in IE. That seems about right.

It's hilarious. Doesn't work in IE, in Edge the button to start doesn't show and if you go directly to https://2018.stateofjs.com/introduction/ the navigation and styling is broken. And in 10 the floating squares don't even show up. And it doesn't have fall-back for browsers with no SVG support - really nitpicky but it is an actual problem.

Works just fine in Edge. And TBH that's good enough for me, I don't think supporting IE is necessary for a tech-enthusiast targeted site.
Post reply on HN