JavaScript: The Modern Parts
amontalenti.com
JavaScript: The Modern Parts
1–10 of 122 posts
Re: JavaScript: The Modern Parts
#2Re: JavaScript: The Modern Parts
#3Gimme back my plain old browser Javascript. It was primitive, but at least it wasn't actively harmful.
Re: JavaScript: The Modern Parts
#4The "modern" Javascript parts make me almost physically sick. Gimme back my plain old browser Javascript. It was primitive, but at least it wasn't actively harmful.
"Modern" javascript runs just fine in your plain old browser.
Re: JavaScript: The Modern Parts
#5Re: JavaScript: The Modern Parts
#6Is that possible with the modern JavaScript tools?
Re: JavaScript: The Modern Parts
#7Re: JavaScript: The Modern Parts
#8The "modern" Javascript parts make me almost physically sick. Gimme back my plain old browser Javascript. It was primitive, but at least it wasn't actively harmful.
Care to elaborate? "Modern" javascript runs just fine in your plain old browser.
Re: JavaScript: The Modern Parts
#9I have some ES6 compliant JavaScript to run on the browser. Now I would like to compile it into web-assembly and serve that from a server to the browser, to make it faster to run and download. Is that possible with the modern JavaScript tools?
Re: JavaScript: The Modern Parts
#10Not sure how Webpack is being attributed as being a part of Javascript here. It's a bundler, with Javascript support being one small piece in a much larger puzzle. It's not even the only bundler out there, JSPM is currently in beta which goes in a different direction than Webpack, then you have Parcel and other options as well.
>Understanding babel, and why it’s important
Eh. I haven't used Babel in years since switching to TypeScript.
This doesn't seem very focused on Javascript, seems like a lot of emphasis being placed on tooling more than the language itself.