thelarkinn

Hey Sean from webpack, this was really just about our third party plugin ecosystem needing to catch up to v5. If you are feeling IRL Stress, then please don't update yet. Sometimes you have to break things to create progress and ship major versions+bring new features. You don't have to use them, you can just use webpack's zero config out of the box.

I never said there wasn't a cost. Every technical decision comes with trade-offs.

But costs don't hold us back from developing amazing new features [for developers and consumers] for the future. <3

On the Edge team and I can tell you, in no way, does supporting IE, hold back our development capabilities.

If anything, it enables more companies to adopt Edge without concern of breaking support for their legacy applications.

We see that Developers are the ones held back by older versions, and we see this as a huge win for them.

/* Looks to other top HN Posts */

A majority of consumers do not expect Google to track their activities (niemanlab.org)

Ironic?

Technically JavaScript is only ~7% slower then C++ to execute. But snipe away at that stats with real data.

No harm done <3

This is right, its more nativeish apis and webview for UI and friends. Worthy Snipe and misinformation on my part in thread.

Sorry I offended. These aren't rumors just things we've been blogging about, etc. and I'll own being unclear. The Electron and UWP bits are things we've tossed around internally. I don't want to give more details because then it's more then I really know, which is unfair to the teams really working on it, etc.

> JS would be unusable for projects of this scope

Blanket statements don't really make great arguments. That aside, in my experience (webpack for one), projects at scale with JavaScript, are harder to maintain without some type safety and are a bit more bug prone and slower to refactor.

But at the end of the day, its still compiled to JavaScript, whether you chose to slap a .ts file in there, or just use the typechecker standalone is a mere implementation detail.

Those are product decisions someone like me can't actually confirm right? I just know that the purpose or the goal is having a single code base, single toolchain, many targets. I just know I've heard of all of those targets being experimented with! A bit early to assume anything, especially from lowly me!

Could be! Didn't we just announce (and got meme'd to death by InfoSec world) that Excel is going to be able to _run_ JavaScript.

BTW this isn't breaking news, we have been talking about our love, bets, and use of ReactNative and ReactNativeWindows for a while now!

Yup, and that really was what the tweet was trying to portrait. JavaScript, and many scripting (or maybe author meant interpreted languages), are incredible languages to start with.

I have a love for the "sharper" langs like Rust, and AssemblyScript, however the ease of use, hyper backwards compatible, super super accessible package manager, and OSS Ecosystem for JavaScript are what make it world-eating. Plus its only 7-11% slower then C++ execution (last I checked).

If by "They" you mean me, someone who doesn't work on the project itself, but is advising over a toolchain for it.

Also, I do not know what the Linux plans are (but hey maybe a great time to voice that special love you have for Linus T. and his masterpiece)!

I don't think I mentioned Skype for Business anywhere did I? :-)