4 ms·
A bit off-topic, but this is what my folder looks like after `npm install`: Dev du -h -d 1 VueReactPerf/ 1,2G VueReactPerf/node_modules 2,0M Vu
by xgbi 10y ago
A bit off-topic, but this is what my folder looks like after `npm install`:
Dev du -h -d 1 VueReactPerf/
1,2G VueReactPerf/node_modules
2,0M VueReactPerf/dist
52K VueReactPerf/src
1,7M VueReactPerf/.git
1,2G VueReactPerf/
=> 1.2 GB of dependencies. What is happening to the JS ecosystem, where displaying a table in HTML needs 1.2 freaking Gigabytes ?
- petewailes 10y agoAnd this, children, is why we do a proper job. Because the JS landscape nowadays looks like a house of cards, with people who can't code treating modules like Lego to build things. Web dev has exciting things going on in it, but it feels mostly like a bunch of children with no concept of consequences running around desperately re-inventing wheels, rather than caring about quality, efficiency, diligence and professionalism. It's fucking disgraceful, and we should be ashamed of it.
- mikewhy 10y agoOnly ~130MB here $ git clone https://github.com/footballradar/VueReactPerf $ cd VueReactPerf/ $ npm install $ du -h -d 1 820K ./.git 1.9M ./dist 133M ./node_modules 16K ./src
- jventura 10y agoI just read another article here in HN how someone learned how to program (JS/Ruby/HTML and web things..) and got a job in web development in 5 months. I guess it says all about the current quality of this subfield. Unfortunately for me, I've been "selling" myself as full-stack web developer, so I think I'm screwed.. I've been playing with electron (unfortunately based on Node), and the "npm install" installs a lot of 20 line node packages to do really small things. I think these guys took the unix philosophy of do one thing and do it right to such an unpractical extreme.. But I guess that you can't do any better when all your formal studies were 5 months in codeacademy and the like..