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

191–200 of 372 posts

Re: State of JavaScript 2019

#191

Post by tybit »

deckard1 wrote: post #136
azangru wrote: post #102

Earlier quoted context omitted.

> I could go on and on about the horror that is typescript In his talk Predicting the future of the web at the last ReactiveConf, Richard Feldman (not himself a typescript guy, but an Elm user) quoted an interesting statistic that most of developers who try typescript never go back to writing plain javascript. I do not remember where that statistic was from, but can attest that with me it is the case. So much for the…

> most of developers who try typescript never go back to writing plain javascript yes, most developers adhere to RDD. That is, resume driven development. You ever see developers going back to Ruby from Node? Or from any shiny new thing to the slightly older but perfectly fine thing? I predict people will move on from TypeScript within 5 years. Purely because everyone will know TS so the differentiating value of TS wi…

This is really condescending. I don’t like writing JavaScript, I find writing TypeScript ok.

I avoid both when possible but if the business needs some front end or someone else has chosen Node I’ll oblige, and I’ll be happier if it’s TypeScript.

Either way it’s not contributing to my resume in a meaningful way as a backend developer.

Re: State of JavaScript 2019

#192

Post by erokar »

734129837261 wrote: post #75
toastal wrote: post #12

It looks like more people need to learn about PureScript. I was happy to see it included this year though.

I really don't see the point of strong typed programming. JavaScript is fine without it. I've been working with TypeScript for a while now and I never think "this solves a problem I had!" On the contrary, I constantly think "why..." I feel strong typing JS is just a result of backend developers not questioning their upbringings and failing to use proper naming conventions, progressive enhancement in the form of JSDOC…

TS is definitely oversold. I like the typed function signatures, a little bit better autocompletion and some refactor support. Personally I also think typing can be fun. But it doesn't increase safety or productivity, and it comes with costs: build setup, having to import type, libs that have misleading types, having to cast when TS doesn't get it, etc.

Re: State of JavaScript 2019

#193

Post by codegladiator »

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…

> The separations of Model, View, and Control really don't make sense anymore. It's outdated.

What ? why ? care to elaborate please ? and what do you use instead ? MVVM ?

Re: State of JavaScript 2019

#194

Post by electrotype »

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…

Typescript is the only reason I am not shooting myself in the head, on projects at work based on Node.

Re: State of JavaScript 2019

#195

Post by HenriNext »

hellofunk wrote: post #154
HenriNext wrote: post #38

Earlier quoted context omitted.

3 out of 4 most liked technologies are actually from Facebook, so the name certainly doesn't seem to prevent success here..

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

Re: State of JavaScript 2019

#196

Post by Chyzwar »

BiteCode_dev wrote: post #181
Already__Taken wrote: post #156

Earlier quoted context omitted.

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

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

Re: State of JavaScript 2019

#197

Post by nkrisc »

tybit wrote: post #190
donkeyd wrote: post #104

Earlier quoted context omitted.

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.

They said the applicant had rated themselves on the resume. They weren't asked to rate themselves in the interview.

That's how I interpreted the comment and I'm pretty confident that's correct.

Re: State of JavaScript 2019

#198

Post by dmurray »

donkeyd wrote: post #143
fatbird wrote: post #114

Earlier quoted context omitted.

I'd say that the topic of "node.js" skill covers such a wide range of skills, experience and scenarios, that you'd need to be an expert already to judge how little you know. Someone who'd applied it to a single domain successfully can reasonably feel like they've got a good handle on it. Your question is essentially a proxy for server-side architectures and applications, not nodejs itself. It invites misrepresentatio…

I'm still not grasping how the question "what have you actually built with node?" is "a proxy for server-side architectures and applications, not nodejs itself." and "invites misrepresentation." I feel like you guys think I asked them to rate themselves 1-5 on the subject. I did not, I got their resume, where they themselves rated them on the subject. With my question I was just checking whether that self-assessment…

The self-rating is useful because it gives you a measure of their perceived proficiency in skills relative to each other. You still have to ask a question like you did, but now that you know that "3/5 stars in Node" means advanced beginner level, you have a good idea what to expect when they rate their SQL skills 5/5 or their CSS 2/5.

Re: State of JavaScript 2019

#199

Post by nailer »

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.

Re: State of JavaScript 2019

#200

Post by Scarblac »

azangru wrote: post #102
734129837261 wrote: post #67

Earlier quoted context omitted.

I've been taking job applications from other frontend developers in the Silicon Valley fortune 500 area of work. Most resumes that get past the initial recruiter interview and make it to a tech review and claim expert knowledge of CSS... They don't. They don't know shit. They can often not answer basic flexbox questions. Not to mention CSS grid questions. And if you start questioning them about CSS animation performa…

> I could go on and on about the horror that is typescript In his talk Predicting the future of the web at the last ReactiveConf, Richard Feldman (not himself a typescript guy, but an Elm user) quoted an interesting statistic that most of developers who try typescript never go back to writing plain javascript. I do not remember where that statistic was from, but can attest that with me it is the case. So much for the…

I also can't remember any technology that I've seen so few people complain about online. That was actually part of the reasons for us to start using it.
Post reply on HN