News for hackers. Stuff that matters.

A comment on Yarn's Future – v2 and beyond. Parent comment

Re:Yarn's Future – v2 and beyond by mrspeaker on Thursday January 24, 2019 @11:29AM (#18990115)
The comment stripping is optional (just for saving bytes on download). The goal is moving away from Babel, and any other unnecessary transpiling steps. Now that JavaScript has (a semi-working) module system, I find my projects having fewer and fewer dot files and far fewer dependencies.

If I can have a folder of plain JS that I know will work in a browser 20 years from now without having to resurrect an ancient/abandoned toolchain, then I'll do that!

[ Parent | on HN ]
Re:Yarn's Future – v2 and beyond by lmm on Thursday January 24, 2019 @04:59PM (#18993453)
Are you gonna hardcode all the HTML and CSS as well? I would expect resurrecting a 100% compatible toolchain for a mainstream source format 20 years from now will be easier than resurrecting a 100% compatible browser. Especially if that format is a stricter/less ambiguous one like typescript.
[ Parent | on HN ]