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

The State of JavaScript 2018

2018.stateofjs.com

Post reply on HN
Print view View original

121–130 of 286 posts

Re: The State of JavaScript 2018

#121

Post by userbinator »

gagege wrote: post #119
bryanrasmussen wrote: post #30

Earlier quoted context omitted.

I'm reminded of back in 1997 (maybe 98, anyway long time ago), I had been on a JavaScript course with a British guy, and went over to his house. He showed me the little cv site he'd been working on, it had quite a nice design, much better than I would ever do if asked to design something. I looked at the code - it was all tables, so I decided to show him CSS at the end of which he thunderously proclaimed "That's what…

I think he kind of had a good point. It would be nice to have a single set of tools that can always get the job done no matter what.

Not long ago I had to write some JS (had to, not wanted to) to do something on a site, and got something working based on what I knew, only to be derided by a "real JS developer" that my code was "deprecated", "not following best practices", "not modern", etc.

He gave me his version which was around 10x more code and only worked in a subset of the latest browsers, while mine not only did but would probably work in everything since maybe IE5 or so...

Maybe that's considered a bug, but I don't want any of this trend-chasing. I write code to get things done. My users don't care, and they want to get things done too.

Re: The State of JavaScript 2018

#122

Post by userbinator »

pferde wrote: post #37
bigiain wrote: post #8

I guess people with javascript turned off are not the target market for this site, but I found this humorous: http://tinypic.com/view.php?pic=2v31s94&s=9#.W_KD0idx2Rs

I find it amusing that your post links to a page which itself doesn't work without javascript. :)

Fortunately there is a direct link to the image there. http://i64.tinypic.com/2v31s94.jpg

Re: The State of JavaScript 2018

#123

Post by daliusd »

krona wrote: post #102
jaxondu wrote: post #86

Earlier quoted context omitted.

Don’t have to take the survey so seriously. It’s not representative of all JS community. My circle of JS hackers don’t even bother to participate.

Is there any reason to suspect Flow users are less likely to do the survey than, say, TypeScript users?

I can speculate here a little bit. Majority of survey users has less than 10 years of experience. That makes them susceptible of being Visual Studio Code users. VSC - Microsoft product. Typescript is Microsoft product as well.

Re: The State of JavaScript 2018

#124

Post by andai »

kabacha wrote: post #36
IloveHN84 wrote: post #27

Earlier quoted context omitted.

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

As much as I dislike Javascript OP is right. The latest stack overflow survey[1] puts #7 on most loved languages and it's not even in top 25 most dreaded ones. [1] - https://insights.stackoverflow.com/survey/2018#most-loved-dr...

And #2 in most wanted, right after Python.

Re: The State of JavaScript 2018

#125

Post by daxterspeed »

nailer wrote: post #100

As a survey completer, they still don't include ES8 as an option: https://2018.stateofjs.com/javascript-flavors/overview/ 'await' is a game changer for JavaScript: major libraries like Stripe and Hapi are rebuilding their docs too be ES8 based.

I believe the survey uses ES6 (which officially is named ES2015) to refer to the "current version" of ECMAScript (which I suppose is ES2017).

I don't know if the solution is to include each yearly release of ECMAScript since ES6, or to simply add an "ES.Current" option, which would just be the latest proper release.

Re: The State of JavaScript 2018

#126

Post by userbinator »

bigiain wrote: post #8

I guess people with javascript turned off are not the target market for this site, but I found this humorous: http://tinypic.com/view.php?pic=2v31s94&s=9#.W_KD0idx2Rs

I'd say that nicely sums up the "State of JavaScript in 2018": you'll need it even to view a non-app information-oriented page. :-(

Re: The State of JavaScript 2018

#127

Post by thrower123 »

bryanrasmussen wrote: post #30
LandR wrote: post #12

> JavaScript is always changing. New libraries, new frameworks, new languages… It's part of the fun, No.. NO, it isn't.

I'm reminded of back in 1997 (maybe 98, anyway long time ago), I had been on a JavaScript course with a British guy, and went over to his house. He showed me the little cv site he'd been working on, it had quite a nice design, much better than I would ever do if asked to design something. I looked at the code - it was all tables, so I decided to show him CSS at the end of which he thunderously proclaimed "That's what…

The funny thing is, we've just been finding more and more complicated ways to make table-based layouts ever since, but they're better because they are CSS based? I dunno, I don't have to squint hard at CSS-Grid to see old table layouts peeking back at me.

Re: The State of JavaScript 2018

#128

Post by suprfnk »

ksec wrote: 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…

> I really wish other languages communities do a similar survey, Python, PHP, Ruby, Java, Rust etc... It will be interesting to see the trend and big picture.

2018 state of Haskell survey results:

https://taylor.fausak.me/2018/11/18/2018-state-of-haskell-su...

Re: The State of JavaScript 2018

#129

Post by deltron3030 »

sgdesign wrote: post #2

Co-author of the survey here, thanks for posting! Happy to answer any questions :) (As long as the question is not something along the lines of "My favorite library Foo.js is doing pretty poorly in your survey, surely there must be an issue with your methodology?")

Are you surprised by the low percentage of solo devs and small teams (startups) in your survey?

How do you think does this bias towards "enterprise" affect more full featured solutions like Meteor, that are more geared towards small teams and indie hackers?

Post reply on HN