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

What's New in JavaScript for 2019

developer.okta.com

Post reply on HN
Print view View original

71–80 of 85 posts

Re: What's New in JavaScript for 2019

#71

Post by root_axis »

westoque wrote: post #12

I might get heat for this but personally I find the JavaScript ecosystem to be a mess. There are so many changes to the language that are done aggressively which I think are done without much thought. For example, the promises API, now we also have async/await. The module system, with require(s), then import/export, and there's browser JS and system JS (node), and npm and now yarn, then your build system, with webpac…

I love TypeScript but I think it's funny that your answer to the woes of JS complexity is just another JS transpiler. It's a tool you're familiar with and one that you like so you give it a pass on all the complaints you leveled up front. Maybe... just maybe... in a similar vein to TypeScript, most of these other JS tools were built to solve real problems and not just to deliberately confuse you.

Re: What's New in JavaScript for 2019

#72

Post by dsego »

z3t4 wrote: post #64
gautamnarula wrote: post #42

Earlier quoted context omitted.

In my uneducated opinion, I think this is the direction things will go. Typescript will steadily supplant JavaScript and browsers will eventually roll out native support for it, and JS will be relegated to a legacy language.

Having TypeScript support in the browser doesn't make sense as the idea behind TypeScript is to add a compilation step so that type errors can be caught at compilation time. eg. before the code runs.

The browser still has to parse the JS code before executing it. It will complain if you get the syntax wrong, type checking is the same thing.

Re: What's New in JavaScript for 2019

#73

Post by ralmidani »

JS the language is great, and it becomes even better with TypeScript. But the ecosystem leaves a lot to be desired.

Having become proficient with Node/Express/Sequelize at Fullstack Academy and then used them for several months, I really miss Django and Django REST Framework. The ORM, serializers, effortless filtering and permissions, etc. are--with all due respect--simply unmatched in JS-Land.

As for the front-end, I learned and used Ember for over a year before picking up React (it was "cooler" and there were more jobs). So many decisions I've agonized over with React/Redux were solved years ago with Ember. But the problem with Ember is its proprietary object system and its lack of momentum.

If I have a choice, I will be starting new projects with Django on the server-side, and Ember only when an SPA is necessary. In the past, I hesitated to use Django for templates, but the lack of a robust client-side ORM has made that option more attractive.

Re: What's New in JavaScript for 2019

#74

Post by z3t4 »

westoque wrote: post #12

I might get heat for this but personally I find the JavaScript ecosystem to be a mess. There are so many changes to the language that are done aggressively which I think are done without much thought. For example, the promises API, now we also have async/await. The module system, with require(s), then import/export, and there's browser JS and system JS (node), and npm and now yarn, then your build system, with webpac…

You can sill use the "good parts" but you will probably be accused for being unfashionable.

Re: What's New in JavaScript for 2019

#75

Post by zaphirplane »

ng12 wrote: post #44
westoque wrote: post #12

I might get heat for this but personally I find the JavaScript ecosystem to be a mess. There are so many changes to the language that are done aggressively which I think are done without much thought. For example, the promises API, now we also have async/await. The module system, with require(s), then import/export, and there's browser JS and system JS (node), and npm and now yarn, then your build system, with webpac…

> I might get heat for this but... Some variant of this is the top-voted comment of every HN thread on modern JavaScript. > For example, the promises API, now we also have async/await. The module system, with require(s), then import/export, and there's browser JS and system JS (node), and npm and now yarn, then your build system, with webpacker, browserify, bower. Async/Await are essentially sugar on top of Promises…

My guess is there are too many options, and ways, to the casual person it’s a lot to learn/compare then choose, for people that don’t care to compare well there is always a bootstrap starter app

Re: What's New in JavaScript for 2019

#77

Post by krapp »

gautamnarula wrote: post #42
dsego wrote: post #34

At this point why not just have browsers run TypeScript natively? Remember the , maybe just put and be done with it.

In my uneducated opinion, I think this is the direction things will go. Typescript will steadily supplant JavaScript and browsers will eventually roll out native support for it, and JS will be relegated to a legacy language.

>Typescript will steadily supplant JavaScript and browsers will eventually roll out native support for it, and JS will be relegated to a legacy language.

Typescript can't supplant javascript or relegate it to a legacy language... because typescript doesn't compile to bytecode or machine language, but to javascript. Browsers that support typescript natively must by definition also support javascript natively, and the more of the former you have, the more of the latter you have.

Re: What's New in JavaScript for 2019

#78

Post by numbnuts »

westoque wrote: post #50
ng12 wrote: post #44

Earlier quoted context omitted.

> I might get heat for this but... Some variant of this is the top-voted comment of every HN thread on modern JavaScript. > For example, the promises API, now we also have async/await. The module system, with require(s), then import/export, and there's browser JS and system JS (node), and npm and now yarn, then your build system, with webpacker, browserify, bower. Async/Await are essentially sugar on top of Promises…

> All of this happened 3-4 years ago, if it's your job it's not hard to keep up. If it isn't your job there's plenty of guides out there to get you up to speed. I wouldn't expect to be able to jump back into Android dev after 5+ years away from it without doing some reading, I don't know why people expect web development to be so static. The thing is that the JavaScript language is so aggressively changed, unlike Rub…

After the big dump of new features in ES2015, I don't find the pace of planned updates to the language aggressive at all. JavaScript is still playing catch up.

People will complain if they don't add features. When they do add new features, people complain that they're "bloating" the language or moving too fast. Damned if you do, damned if you don't.

The JS ecosystem is a different matter.

Re: What's New in JavaScript for 2019

#79

Post by numbnuts »

westoque wrote: post #12

I might get heat for this but personally I find the JavaScript ecosystem to be a mess. There are so many changes to the language that are done aggressively which I think are done without much thought. For example, the promises API, now we also have async/await. The module system, with require(s), then import/export, and there's browser JS and system JS (node), and npm and now yarn, then your build system, with webpac…

Isn't TypeScript committed to implementing all stable ECMAScript features?

It being a superset with TypeScript-only features on top of ECMAScript, wouldn't the "aggressive changes" you complain about be worse?

Post reply on HN