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

261–270 of 372 posts

Re: State of JavaScript 2019

#261

Post by yesimahuman »

Thorentis wrote: post #3

Sad to see Ionic in the avoid category. Their latest release I thought was quite polished, and I've enjoyed using Capacitor rather than Cordova. I think the key to further success is breaking away from Cordova entirely, and expanding the native features supported in Capacitor. Right now I find myself having to use both due to some things not being implemented in Capacitor yet.

We’re sad to see it as well, especially because our recent releases have been so well received. I fear people formed their opinion years ago, especially with the move to Angular 2, and it’s been harder to get those people back. Oh well, we’re focused on continuing to make improvements and moving harder toward Capacitor and so far the community has been responding very well.

The other thing happening with Ionic is that our enterprise business has been doing very well. We’ve added hundreds of enterprise customers in the last two years and have really built a solid offering for medium to large businesses. We’ve also seen more and more huge apps built on the platform.

I’m guessing our focus on enterprise has also cost us a bit in this survey. Been a learning experience how to balance that and convey to folks we are both an OSS and enterprise co

And seeing angular in the “analyze” category makes me think the sample of folks responding to this survey are in a certain bubble that does not map to the broader dev ecosystem we see every day, so there’s that.

Re: State of JavaScript 2019

#262

Post by leshow »

TomMarius wrote: post #171
allover wrote: post #159

Earlier quoted context omitted.

TypeScript is kind of in its heyday though, it's fairly unlikely many teams would be comfortable making a bold decision to "switch back to JS", even if they want to. Would need to be given more time for such a statistic to be meaningful, if it ever would be.

Not a single developer I know (I was in leadership position in a company with 300+ devs, now I lead a small startup dev team) cares about "heyday". They care about their experience during development being significantly worse with plain JS due to stupid ("we'll use TS because it checks names of properties") but also not so stupid ("we'll use TS because it checks that switches are exhaustive", "we'll use TS because it…

Most of the types you write in TS will be structural

Re: State of JavaScript 2019

#263

Post by s_y_n_t_a_x »

nailer wrote: post #199
bradchris wrote: post #95

Wow, just learned of Svelte from this. After reading their explanatory blog post and coming upon this blurb: That all changed with the advent of hooks [React and Vue], which handle state in a very different fashion. Many frameworks started experimenting with their own implementations of hooks, but we quickly concluded it wasn't a direction we wanted to go in ... We can just use the language. Updating some count value…

Yeah Svelte is the next thing. Backbone and Angular were great, but then came Vue and React. Vue and React were great, but then came Svelte. It's: - Simpler. You change values with `=` not some method call. - Faster, as the svelte compiler dynamically creates bindings at build time, vs a virtual DOM that has to dynamically track binding at run time - Smaller, since Svelte's output doesn't include Svelte.

Svelte is just a web framework, React is a software framework.

Then there's the missing Typescript support...

That's what happens when you create your own template syntax...again.

I'll continue to use React so I can simply use Typescript for my components, not some random syntax.

My styles are typed, my components are typed, my state is typed. Why would I ever go back?

Re: State of JavaScript 2019

#264

Post by cheapsteak »

kabes wrote: post #163
lgessler wrote: post #28

So sad to see Meteor solidly in the avoid quadrant, but it seems deserved. Meteor is what I learned how to do web development with back in 2015, and it was fun . It didn't take much to make stuff happen, and the baked-in live sync was like magic. I'm still eager to whip Meteor out for proof of concept prototyping because of how convenient it is to have a schemaless database and a framework that abstracts away HTTP, b…

I don't think it's deserved. If you don't need the kind of reactive queries Meteor offers (and IMO is still unbeaten in terms of developer productivity in case you do need them), then you can safely ignore that part. In the end Meteor is mainly a layer on top of nodejs. So you can do all your regular nodejs stuff and you can run Meteor without any of the mongo stuff these days. Then it still offers you a zero-config…

How would you compare it with Create React App in terms of ease of use and build/dev speed for front end projects?

Re: State of JavaScript 2019

#265

Post by idoubtit »

The data visualization is often awful and misleading. For instance, consider https://2019.stateofjs.com/javascript-flavors/

1. The first graph shows "Rankings". I strongly doubt rankings are more importants than values. When Clojurescript goes from 67% to 72%, this increase is shown as a ranking decrease because Reason was introduced at a higher ranking.

2. The meaning of the data is unclear, since the exact questions and proposed answers are not shown.

3. Some measures have varying populations, so ranking them is absurd. Supposing that 2% of people use A and 80% use B, what does ranking satisfaction with A above satisfaction with B mean? Since the uncertainty is huge on the A measure, the "real" ranking is not known.

4. Having to click in order to switch the measure shown is strange. The three measures should be display on three consecutive graphs.

5. The Categories graph is unreadable for a slightly color-blind like me.

6. The Categories segments aggregate data over 2 levels which makes them unreadable. First levels: Used, Heard, Unheard. Second levels should be computed relatively to their containers. Who cares if 1.8 % of users would not use Elm again? What is important is that ~28% (1.8/(4.7+1.8)) of those who used Elm would prefer not to do so again.

Re: State of JavaScript 2019

#267

Post by LocalPCGuy »

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.

I also (as seen in at least one of your other responses) that people associate AngularJS and Angular when doing rankings in surveys like this one. There are many people who will never try Angular because of their experience with AngularJS.

Also, this isn't a scientific random sample survey, it's people who self-selected to take it. And I think that Angular specifically suffers due to that because it is more likely to be used at enterprise or large companies where devs often tend not to follow Twitter/surveys/etc at least, not in the same numbers as some other groups. Just my opinion.

Re: State of JavaScript 2019

#268

Post by Supermancho »

ggregoire wrote: post #68
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.

It takes 1 afternoon to learn React and it never requires you to open the doc again. Angular, on the other hand...

> It takes 1 afternoon to learn React and it never requires you to open the doc again.

You are confusing your imagination with reality (or the history of your own experience).

Re: State of JavaScript 2019

#269

Post by LocalPCGuy »

WA wrote: post #174

Interesting. React is the thing. But some trends are weird: People ditch Cordova heavily, but also React Native and native apps. Electron rises to the top, although you can't build mobile apps with it that are distributed through the various stores. So, what's filling the void for app development, if everything just went down?

Definitely Flutter. It's pretty easy for JS devs to work with Dart, and the Flutter architecture is basically like React - component-based (called widgets in Flutter) + RxJS (Streams and RxDart).

Re: State of JavaScript 2019

#270

Post by jccalhoun »

pkalinowski wrote: post #52

Charts in this report are very misleading. In some cases 6% difference is 2 times bigger on chart than 5% difference. I’m aware they have no scale, are simplified etc, but chart format has very specific meaning and I believe that visualisations could be chosen in a better way.

I also noticed that on the Front End Frameworks awareness chart where react and angular flipped places from second to first even though they are both at 100% and then I saw that the vuejs was in 3rd place although it was also at 100%
Post reply on HN