- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
You must log in or # to comment.
laughs in Cargo
./targetCame here to say this, but I was delayed by having to clean my cargo target folder.
2012 called, they want their meme back
That’s the one that’s like Yarn’s global cache, but without compression, right?
Not sure, but probably. I only used yarn 1. Never got around to trying yarn 2+ as migrating our fairly large monorepo project at the time felt like a pretty large and complicated ordeal. By the time I switched jobs npm was already a whole lot better in the ways most important to me.
The little I’ve read about and used pnpm so far it seems a lot more plug n play than yarn while bringing big benefits. Even workspaces seems a lot simpler than it ever was with yarn (at least when I used it). Love the idea of non-flat node_modules and simplified lock files as well.
Time will tell if npm incorporates enough of pnpm’s features to make it obsolete eventually but for now I can understand why it seems so widely adopted.
I mean, the essential difference of no node_modules is shared, as are workspaces.
I think pnpm is more manual, but therefore less magic than yarn. More compatible, less stuff just works
the only JS package manager I have on my system.
for unruly projects, I just pass –shamefully-hoist
Somewhere to the right has to be unity’s Library folder
those devs understand why their assets are so large. but if you ask a js dev why they webpack instead of compiling they just start crying and run away
It depends. If you switch between different branches a lot, Library just grows to infinite sizes due to storing everything from each branch that is unique to those branches. I once had to clear about 600 gigs of library lol.
