4 ms·

>Super excited about the future of JavaScript tooling ecosystem with more focus on efficiency and speed. Well they can't get worse than now... 234mb for a frig

• koolba 5y ago
  It’s more of a hello import the world.
  • thunderbong 5y ago
    Or is it the other way around!
• spoiler 5y ago
  It's worth noting that the tooling and build systems are that big. They include type definitions, binaries, scss preprocessors, typescript compiler, linter, and a lot of other tools to enhance DX. Some of them might include other non-code resources. The hello world app is not going to be this big.
• ng12 5y ago
  Would you count the size of the JVM when you do Hello World in Java?
  • Scarbutt 5y ago
    No because they are not counting the size of the browser or nodejs
  • deleted 5y ago
    [deleted]
  • hombre_fatal 5y ago
    You could, since it’s a runtime dep. But a better comparison would be to the client dev tool chains in other ecosystems, like Xcode (11GB), though still not very interesting. Turns out client dev is hard and it doesn’t make much sense hand wringing over dev tool size metrics. Better to look at how well they solve their problem space.
  • valdiorn 5y ago
    you could and it would still be much smaller.
  • callmeal 5y ago
    Java HelloWorld runs in 1mb: 20:18:01 /tmp > echo 'public class HelloWorld {public static void main(String[] args) {System.out.println("Hello World!");}}' > HelloWorld.java 20:18:09 /tmp > javac HelloWorld.java 20:18:14 /tmp > java -Xmx1m HelloWorld Hello World!