Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

State of JavaScript 2019

2019.stateofjs.com

Post reply on HN
Print view View original

231–240 of 372 posts

Re: State of JavaScript 2019

#231

Post by codingdave »

samspenc wrote: post #61

I'm surprised to see Angular drop in ratings and rank so poorly compared to React. I personally prefer Angular myself because it's (a) opiniated and (b) has everything included (HTTP REST calls, Material UI, etc). Just curious why so many people prefer React and mark it so positively.

> Just curious why so many people prefer React and mark it so positively.

For the exact same reasons you stated -- Angular is opinionated and has everything. React is just a framework - you get to make your own opinions and are not handed the whole ball of wax, so you can make your own choices.

Re: State of JavaScript 2019

#232

Post by lllr_finger »

734129837261 wrote: post #94
hacker_9 wrote: post #84

Earlier quoted context omitted.

Typescript doesn't make things easier, and react is intuitive? You know April fool's is still a few months away right?

TypeScript slows down a project. Nobody seems to ever point out what benefits it supposedly offers. My claim: TypeScript offers no benefit. Ever. That's 2 years of fulltime TS experience talking and 18 years of fulltime JavaScript experience, on top of a whole bunch of full stack (Java and .Net with C#) experience. I think the popularity of TS is going to decline. And I think it's only popular because of the influx o…

Yes, it slows you down because you need to think about your domain and how that maps into types (whether you think those types exist or not, they do).

Having that opinion isn't backend bias - it's likely being exposed to a variety of programming languages and having first-hand experience with the pros/cons of static vs dynamic typing.

Re: State of JavaScript 2019

#233

Post by epmatsw »

taurath wrote: post #121

I wish “salary” wasn’t the way people were asked about pay. Everyone I know who’s over 200k only has 1xxk salary and like 100% of that in stock compensation. It’d give a different picture of what more people are making.

True. I wasn't sure how to interpret that section either. Compensation (or Total Compensation) might be a more interesting measure

Re: State of JavaScript 2019

#235

Post by kabes »

Aeolun wrote: post #208
kabes wrote: post #166

Earlier quoted context omitted.

Meteor 0.8 was released in 2014, and I'm sure your app would still work on the latest Meteor release without much changes, while in the meantime offering all the latest JS features (JS in 2014 was a completely different world). How many other JS build tools & frameworks from 2014 can say the same?

How many JS build tools from 2014 exist? And how many are still used? I think both will be fairly close to zero.

That's my point. Other people had to rewrite their software for new build tools, while our Meteor app started 5 years ago never needed any big changes, while we could gradually adopt ES6+ features, modules, dynamic imports, ...

Re: State of JavaScript 2019

#236

Post by hellofunk »

HenriNext wrote: post #195
hellofunk wrote: post #154

Earlier quoted context omitted.

I said if there are no alternatives. There was no alternative to React for a long time, and it gained much popularity and momentum. But there are many alternatives to Flow.

> There was no alternative to React for a long time Angular is 4 years older than React, and generally speaking front-end frameworks have been probably the single most competed/overcrowded area...

There was absolutely nothing like react at the time it came out, angular had none of its key features.

Today we have Vue and others are forming in other languages, but still today angular takes a very different approach to the front end. But react’s breakthrough in the virtual dom management was totally new and really changed a lot of things in our industry.

Re: State of JavaScript 2019

#237

Post by irrational »

Chyzwar wrote: post #196
BiteCode_dev wrote: post #181

Earlier quoted context omitted.

It's not just the people, some topics leads to that. E.g you can get far with just a few git commands, but one day, you will encounter a situation that is like a brick wall because you have no idea what's going on inside. Today, most JS devs don't know how "this" works, most python devs never used pdb, most git users picture a branch like a diverging chain of commits and not a moving label, etc. Again it's not the pe…

That ok, but these people need to stop labelling themself as experts. It makes difficult for true experts to stand out.

Maybe experts don't call them selves experts.

I have a friend that had some home remodeling work done, poorly. The friend said to me, "But, they were professionals!" I responded, "Well, that's the problem. A professional is someone who will do the least amount of work in the least amount of time for the most amount of money. If you want someone who actually cares about the work, hire a craftsman instead of a professional."

Re: State of JavaScript 2019

#238

Post by irrational »

DavidPP wrote: post #224
donkeyd wrote: post #89

Earlier quoted context omitted.

I got a resume a while ago where the applicant rated their skills 1-5 stars. They has rated themselves either 3 or 4 out of 5 in Node.js. When asking what they actually did with node, they explained they built some proof of concept once. I got to see the code and it was maybe 4 weeks of work for a beginner... At that time I was leading a small Node.js dev team and I would maybe rate myself 3/5 in Node. We didn't end…

I interviews interns from a school where they all ask their students to rates themselves like that. At first I was put off, but now I interpret it as their own personal scale, with 5 being what they the best at, and not as "I know everything about this". But even then, the best candidates are usually the ones who rated themselves the lowest.

That makes sense. The more I know about a topic, the more I know about how much I do not know. If I know a topic very well, I also know how very little I really do know, so I'd rate myself much lower.

Re: State of JavaScript 2019

#239

Post by jessaustin »

shabbyrobe wrote: post #15

I find it kinda strange that Flow has been relegated to the write-in "Other Flavours" section so soon. I know that it has been trending downwards for a while (as TypeScript trends upwards), but it feels like that story's not quite over just yet even if the conclusion is foregone.

Maybe I'm misreading the numbers but ISTM that Flow, Coffeescript, and Dart could have moved up to the main list and the things they outnumber like Purescript could have moved down to the others? I guess when one sets up a survey one can set it up however one wants.

Re: State of JavaScript 2019

#240

Post by smashface »

geewee wrote: post #47

All the content aside, I just want to say that the presentation in State of JavaScript is magnificent. Some of these charts are superbly designed.

Some of them look good but some of them are terribly designed. The rankings for testing graph shows storybook visually trending down when it actually increased in satisfaction.
Post reply on HN