It’s more of a hello import the world.
Re:Why we switched from Webpack to Vite
by thunderbong on Wednesday April 28, 2021 @08:51PM
(#26976158)
Or is it the other way around!
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.
Would you count the size of the JVM when you do Hello World in Java?
Re:Why we switched from Webpack to Vite
by hombre_fatal on Wednesday April 28, 2021 @06:33PM
(#26975096)
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.
Re:Why we switched from Webpack to Vite
by Scarbutt on Wednesday April 28, 2021 @06:46PM
(#26975213)
No because they are not counting the size of the browser or nodejs
Re:Why we switched from Webpack to Vite
by valdiorn on Wednesday April 28, 2021 @07:37PM
(#26975589)
you could and it would still be much smaller.
Re:Why we switched from Webpack to Vite
by callmeal on Wednesday April 28, 2021 @08:18PM
(#26975885)
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!
Well they can't get worse than now... 234mb for a friggin hello world app