Re:The Node ecosystem still has tooling problems
by xdennis on Saturday July 30, 2022 @11:51PM
(#32293000)
> I miss the days of the web where you could just load a page in under 25kb.
Ah, yes, the old web where there was "no design, no testing, no stability, no benchmarks".
Don't get me wrong. I liked the old days when content was just HTML, but when it comes to building applications, the old ways were just terrible. You could push JS files without even checking that it's valid syntax.
Re:The Node ecosystem still has tooling problems
by vbezhenar on Saturday July 30, 2022 @11:36PM
(#32292918)
Our node docker images are 600-1000 MB for relatively simple website (backend and frontend). 25 MB would be so good and lightweight.
Re:The Node ecosystem still has tooling problems
by interblag on Sunday July 31, 2022 @01:08AM
(#32293341)
Unless I'm massively misunderstanding your setup, that Docker image contains an entire OS and runtime, not just your website. Reasonable people can disagree about whether that entire paradigm is sensible but, having chosen to use Docker, complaining about image size in this way seems an odd choice. More to this point, most of what is in the image will be little to do with Node or its build systems..
Re:The Node ecosystem still has tooling problems
by toomanybeersies on Sunday July 31, 2022 @02:30AM
(#32293688)
The NodeJS alpine base image is only 40 MB.
Re:The Node ecosystem still has tooling problems
by lolive on Sunday July 31, 2022 @03:00AM
(#32293815)
Then you _npm install_ something, and BOOOM!
600MB !
Re:The Node ecosystem still has tooling problems
by Defman on Sunday July 31, 2022 @03:09AM
(#32293852)
You can use multi-stage builds [1] so your result image would be as small as possible by just copying the compiled JS from the build stage.
[1]: https://docs.docker.com/develop/develop-images/multistage-bu...
Re:The Node ecosystem still has tooling problems
by vbezhenar on Sunday July 31, 2022 @06:06AM
(#32294527)
You still need to download hundreds of megabytes of packages, unpack those into gigabyte of storage, "compile" it into a final form.
Also you need to keep those huge images, if you want to have any reasonable caching. Otherwise builds will take forever.
Re:The Node ecosystem still has tooling problems
by hinkley on Sunday July 31, 2022 @04:17AM
(#32294154)
Compiled JavaScript?
Re:The Node ecosystem still has tooling problems
by veyh on Sunday July 31, 2022 @06:17AM
(#32294572)
Bundled. With esbuild, for example.
Re:The Node ecosystem still has tooling problems
by Defman on Monday August 01, 2022 @05:56AM
(#32303866)
My bad, I meant "bundled".
Fixed it for you.
The node ecosystem embodies mediocrity. There is no design, no testing, no stability, no benchmarks, no RFCs, no plan to produce a coherent product. Instead, you're giving a half baked set of features that are abandoned within 8-12 months. Not invented here syndrome runs wild, and over-engineering any solution is seen as a mark of accomplishment.
Simple things, like displaying static text, now require 25mb of js files for whatever framework the author is currently playing around with as a hobby. I miss the days of the web where you could just load a page in under 25kb.