3 ms·
Most of the build tooling gets installed along the way. The compiled JS is hundreds of bytes at most, usually because React creates a bunch of boilerplate for
by nine_k 6y ago
Most of the build tooling gets installed along the way.
The compiled JS is hundreds of bytes at most, usually because React creates a bunch of boilerplate for you (a basic CSS file, an application, a web worker, etc) which you may remove.
- XorNot 6y agoBut why would you? This is the silliest way to judge something ever: what practical web application is anyone routinely building with no CSS, web workers etc.
- Zarel 6y agoYou would because you're comparing it to a "Hello world" command-line program in another language which also doesn't have CSS, web workers, etc.
- lhorie 6y agoWell, that's part of the jab: that you ostensibly don't need build tooling for an interpreted language, and further, that you don't even need an interpreted language in the first place considering we're talking about a platform that can do UI out of the box via a declarative language. (Obviously, that's neither here or there when we're talking about baselines for SPAs)
- nine_k 6y agoES6 is a compile target. The actual languages are often Typescript and jsx, to say nothing of the Svelte compiler or Elm. You can write vanilla JS without all that, of course.