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

181–190 of 372 posts

Re: State of JavaScript 2019

#181

Post by BiteCode_dev »

Already__Taken wrote: post #156
BiteCode_dev wrote: post #76

Earlier quoted context omitted.

Half of my income is from training people in JS and Python. I have 50% of those missions that are requested to be "advanced" courses. The vast majority of the participants are not up to the task. They are paid professionnals, but they consistently overestimate they level, skills and needs. They often are not very good, and of course, they don't know what they don't know. So I always check for that first, and rewrite…

If I've learnt anything from teaching kids it's the ones really good at it when we start are completely dwarfed by the kids who sucked at it. You can get kinda far without really understanding what's going on, but if you stop and have to learn something really fundamental the "good" kids just seems to manage. Once things pick up they can excel because the have truly moved on. the previously "good" ones are still copy…

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 people's fault: they are required to be productive very quickly. There is competitive pressure. So they aim for what's good enough to make things that looks right. Can you blame them ?

Few jobs pay devs to update their skill on company time, and not everyone will spend an hour a day learning new things instead of playing with the kids, doing exercice or going out with friends.

Re: State of JavaScript 2019

#182

Post by gherkinnn »

Zarel wrote: post #134
bakuninsbart wrote: post #99

Earlier quoted context omitted.

In my experience, people who have been experts on JS before TypeScript became a thing hate it. - It doesn't give them any advantages, while severely limiting their options and workflow. For newer developers with background in other languages it is quite nice though.

I was an expert on JS way before TypeScript. I was kind of slow to adopt it because "the type hints are optimized away and can't even be used to boost runtime performance", but when I did start using it, I loved it and wish I had earlier. The linked article says the vast majority love TypeScript, too. I think the real dividing line is probably that people who haven't had to maintain a large project hate TypeScript. (…

Good point. I too only saw the point after being burnt by a large JS application.

Re: State of JavaScript 2019

#183

Post by verttii »

CrazyDave wrote: post #115
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 think the comments in this thread captures it pretty well. If someone doesn't see the benefits of typed languages, TypeScript will just be something that slows them down for no apparent reason. Same goes with RxJs, dependency injection, unit testing, and modules.

But Typescript is not a "typed language", rather a "language with types". Because of having to maintain JS compatibility it lacks the inherent type safety that other similar languages like Dart provide.

Re: State of JavaScript 2019

#184

Post by Alonski »

assholefucker wrote: post #151
deathtrader666 wrote: post #6

EmberJS should not be in the "avoid' section.. it is one of the most well thought-out framework which just gets the job done.. and it is a bit contra-indicatory that Ember guys are the highest paid.

I like ember except for actions/closure actions. Functions are first class in js, let's just send them instead of by namespace.

In modern Ember it is possible and even recommended to use normal functions :) In Ember Octane with Native Classes and Decorators it is possible to use normal functions and if they need to have access to the this context of the class then they are decorated with the @action decorator.

Re: State of JavaScript 2019

#185

Post by jamil7 »

tehbeard wrote: post #175
jamil7 wrote: post #133

Earlier quoted context omitted.

Until you need a router or state management ect, then you've got a few tabs of docs open and a case of anlysis paralisis and a bunch of glue code to write.

The same will happen when you fall off the happy path with ordained choice of any particular framework.

Absolutely, I'm not rooting for either framework to be honest just pointing out that the comparison is somewhat unfair.

Re: State of JavaScript 2019

#186

Post by erokar »

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?

Flutter.

Re: State of JavaScript 2019

#187

Post by BiteCode_dev »

OceanSunfish wrote: post #179
BiteCode_dev wrote: post #76

Earlier quoted context omitted.

Half of my income is from training people in JS and Python. I have 50% of those missions that are requested to be "advanced" courses. The vast majority of the participants are not up to the task. They are paid professionnals, but they consistently overestimate they level, skills and needs. They often are not very good, and of course, they don't know what they don't know. So I always check for that first, and rewrite…

> you wanna learn react and you never used an arrow function, wtf At least in the early days, using React was the first time most people would be exposed to webpack/babel, so it was also their first exposure to the newer JS features.

But you didn't need arrow functions at the time because createClass autobind this and you used methods. Now with extends and hooks, it would be a pain.

Besides, it's alright to learn es6 and 7 with react if you have time, but if your company pays a $10k react training in a 3 days session, you better have the pre-requisites right.

And at the very least, don't pretend to be "an expert" in 2019 if you don't know es6. Every tutorials for beginers include them now. Every docs of every libs use them.

You don't have to be an expert. It's legitimate. I don't advertise myself as a JS expert despite being pretty good at it.

But it looks better on the resume, and once you are hired on that assumption, you can't go back. Next time the company asks, you say expert again.

Re: State of JavaScript 2019

#188

Post by jgresty »

734129837261 wrote: post #74
deathtrader666 wrote: post #6

EmberJS should not be in the "avoid' section.. it is one of the most well thought-out framework which just gets the job done.. and it is a bit contra-indicatory that Ember guys are the highest paid.

Just the fact it uses Handlebars templates disqualifies it as a viable option for me. Handlebars is terrible to work with, especially once you're used to JSX type of options. HBS = restrictive for nonsense reasons. The separations of Model, View, and Control really don't make sense anymore. It's outdated. I've worked with it for years and I consider myself familiar with it up until 3 years ago, but I would never go b…

I'm curious to know why you think separations don't really make sense any more. Care to elaborate?

Personally I prefer anything that is restrictive, I would take the price of less flexibility for the ability to stop people doing stupid things.

Re: State of JavaScript 2019

#189

Post by codegladiator »

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 stay away from angular (I don't do react either, prefer vue as long as I have a choice) mainly because of major time I invested in angular 1 and then they completely ditched it and kept the same name.

Re: State of JavaScript 2019

#190

Post by tybit »

donkeyd wrote: post #104
tybit wrote: post #97

Earlier quoted context omitted.

To be honest the problem here is the question not the answer. It’s a bad question and shouldn’t be asked.

Why is it bad to ask about the actual experience someone had with something that I will be hiring them for? That makes no sense to me.

Asking them about their actual experience is a fantastic question. Sounds like you got a good picture of their prior experience doing so.

Asking them to self rate themselves is useless however, as their answer showed.

Post reply on HN