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

The State of JavaScript – Survey results

stateofjs.com

Post reply on HN
Print view View original

101–110 of 357 posts

Re: The State of JavaScript – Survey results

#101

Post by [deleted] »

dntrkv wrote: post #93
matthewmacleod wrote: post #40

Earlier quoted context omitted.

See, I'm not sure that's the case. When I started writing apps using Cocoa, for example, I had a pretty good experience. Yeah, I fought some of the tooling that I wasn't really used to, but given that it was quite different from my backgrounds in web and embedded development, I was overall quite pleased with how easy and more importantly how obvious everything was. I found this to be the same when I wrote application…

My experience is the opposite. I've been working on the web for over a decade now and only until a couple years ago have I really been happy with my stack. My usual stack looks something like: Express / React / Redux / Webpack / Enzyme / CSS Modules I do SSR / Universal JS whenever possible and it works great. The only problem on my stack nowadays is the CSS. Still haven't figured out a good flow. I currently use CSS…

[deleted]

Re: The State of JavaScript – Survey results

#102

Post by Swizec »

BinaryIdiot wrote: post #69
triangleman wrote: post #55

I wish to register my complaint with the term "ES6" which has always been unofficial and refers to the official standard "EMCAScript2015".

Same. ECMA changed to using dates a while ago and people are still saying "ES6" and "ES7". I've also seen people refer to all new syntax and features as "ES6" including things that in ECMAScript2017. Honestly though I think ECMA has some of the blame for this. I don't think they do a very good job communicating changes and versioning.

In my experience ES6 means "modern". Anything that wasn't there before 2015.

Considering we're encouraging everyone to use transpilers and features from the future, and that browsers will forever lag just a little bit behind, I don't think that's a super bad idea. Most programmers don't care exactly which features are in ECMAScript2015 and which are in ECMAScript2016 etc. All they care about is "Can I do this thing I saw in a code example? Oh cool, it works".

Detailed versioning is an implementation detail.

Re: The State of JavaScript – Survey results

#103

Post by drhayes9 »

vlunkr wrote: post #64

For the life of me I can't understand why webpack has become the de facto build tool. It's so much more complex than anything else I've tried. I understand it's supposed to be faster, but still, I wouldn't bother with it until your build times actually start to become a nuisance.

webpack allows some pretty sophisticated resource pipelines that go beyond what you can do with browserify, especially around binary resources.

One of my use cases is working on a HTML5 game. I pre-process all the tilemap levels to add unique IDs to the entities within the file, but only for those JSON files that look like tilemaps. Each of those files' names get mangled as a hash of their contents as well, so I get some cache-busting for free.

Similarly, I can pngcrush the image assets that pass a certain rule, etc.

Re: The State of JavaScript – Survey results

#104

Post by rpeden »

nekitamo wrote: post #91
wstrange wrote: post #79

Earlier quoted context omitted.

Give Dart a try. It has a single dependency management tool (pub), support for Angular 2, and is generally a joy to use. Material widgets for Angular 2 (the same ones Google uses internally to build Adwords) are expected to be announced at the Dart summit in October.

Correct me if I'm wrong, but I thought that the majority of the Adwords frontend is still written in GWT?

It appears that the new version of the new AdWords UI is created using Dart and Angular 2: http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dar...

I'm not a heavy AdWords user, so I can't say for certain that this represents all of the AdWords UI. But based on the linked interview, it sounds like they replaced a lot of GWT with Angular.

Re: The State of JavaScript – Survey results

#105

Post by TickleSteve »

davidw wrote: post #33
anamoulous wrote: post #24

I apologize if the predictability of this comment, but I just want to say, I recently started a new gig at a company that has undergone a full on embrace of Javascript for tooling and server side projects and it boggles my mind how much productivity is wasted on this ecosystem. There is an interesting amount of energy put into making asynchronous code read synchronously in situations where asynchronous code provides…

If you haven't seen it, you might find this entertaining: https://www.youtube.com/watch?v=bzkRVzciAZg I really wish gar1t would make some new videos, I love them.

Excellent! someone in this world has their head screwed on right!

(you're getting downvoted unfairly I think, probably a bit politically incorrect in this neighbourhood).

Re: The State of JavaScript – Survey results

#106

Post by cloverich »

DarkTree wrote: post #82
BinaryIdiot wrote: post #69

Earlier quoted context omitted.

Same. ECMA changed to using dates a while ago and people are still saying "ES6" and "ES7". I've also seen people refer to all new syntax and features as "ES6" including things that in ECMAScript2017. Honestly though I think ECMA has some of the blame for this. I don't think they do a very good job communicating changes and versioning.

Yeah I think there is just a lot of friction when moving from the concise "ES6" to the lengthy, and somewhat awkward "ECMAScript2015". The fact that so many people still use the terms ES6 and ES7 gives others even less incentive to use the official naming scheme. Hopefully, it will iron itself out in the future.

I think its not just the length but the concept: Every other language has a normal looking version (Rust 1.12 announced! Java 8, etc). They had that with ES3, ES5, ES6, then decided (perhaps for very good reasons) to change to a unique (?) version scheme.

Re: The State of JavaScript – Survey results

#107

Post by austincheney »

triangleman wrote: post #55

I wish to register my complaint with the term "ES6" which has always been unofficial and refers to the official standard "EMCAScript2015".

ES6 refers to ECMAScript version 6, which was the official name of the latest version up until around December 2014. I believe ECMAScript 2015 was coined by Dominic Denicola to put additional pressure on TC39 to publish that year.

Re: The State of JavaScript – Survey results

#108

Post by wstrange »

nekitamo wrote: post #91
wstrange wrote: post #79

Earlier quoted context omitted.

Give Dart a try. It has a single dependency management tool (pub), support for Angular 2, and is generally a joy to use. Material widgets for Angular 2 (the same ones Google uses internally to build Adwords) are expected to be announced at the Dart summit in October.

Correct me if I'm wrong, but I thought that the majority of the Adwords frontend is still written in GWT?

The new Adwords is built with Dart.

Source: http://news.dartlang.org/2016/03/the-new-adwords-ui-uses-dar...

Re: The State of JavaScript – Survey results

#109

Post by pauljaworski »

timdorr wrote: post #97
pauljaworski wrote: post #89

>Overall, developers are not happy about JavaScript testing. This is because of the low percentage of devs in the survey who have used Jest. I can't begin to describe the joy of finally finding a JS test utility that just works and doesn't require a giant configuration file. If you aren't using Jest, make the switch now! It's likely a lot of your existing tests will work with Jest.

Totally agree. Just switched to it on Redux and this was all that was involved: https://github.com/reactjs/redux/pull/1951/files Most of that is just find-and-replace kinds of changes. But we dropped 3 dependencies to one and sped everything up in the process. It's just a fantastic tool! I finally feel like I've got a good Rspec equivalent in the JS world.

I noticed that! I often refer to the Redux docs for examples and was glad to see you had also switched to Jest. You guys have some of the best documentation around, by the way. I wish you did the docs for Flow and Immutable as well! They could use some major improvement.

Re: The State of JavaScript – Survey results

#110

Post by davidw »

TickleSteve wrote: post #105
davidw wrote: post #33

Earlier quoted context omitted.

If you haven't seen it, you might find this entertaining: https://www.youtube.com/watch?v=bzkRVzciAZg I really wish gar1t would make some new videos, I love them.

Excellent! someone in this world has their head screwed on right! (you're getting downvoted unfairly I think, probably a bit politically incorrect in this neighbourhood).

I don't care about downvotes, I thought that video was hilarious and enjoy sharing it. He's the same guy behind "MongoDB is web scale" and "Erlang the Movie II", which I'd also highly recommend:

http://www.mongodb-is-web-scale.com/

https://www.youtube.com/watch?v=rRbY3TMUcgQ

Post reply on HN