Let's Package jQuery: A Javascript Packaging Dystopian Novella
In which I blog about attempting to build one of the most basic building blocks of many modern sites, and reflections on what that might mean for packaging and deploying libre web applications.
Debacle, Stephen Michael Kellat, Charles Stanhope, Mike Linksvayer and 2 others likes this.
Stephen Michael Kellat, Olivier Mehani, Douglas Perkins, Douglas Perkins and 2 others shared this.
Show all 13 replies
@Claes Wallin (韋嘉誠) Yikes, I think you're right, I'm not sure how Guix can handle that nightmare scenario.
Is it trivial to do "guix light", i.e. a dependency tree that assumes you have some stuff on your system already and is not grounded in linux+glibc and pulls in a gigabyte of packages?
Perhaps on some level, the responsible thing if you're providing software is to host all your dependencies yourself, of course with proper references to the canonical locations. And if you're doing that, just make your own guix tree while you're at it. It will still dedup well with packages pulling things from other places, and third parties can still upgrade packages by playing with the package definitions.
Well, the "nightmare situation" is what the npm people consider a solution to dependency hell. People who have been to battle against Maven are properly jealous. It's a difficult problem and at least npm has a way to not solve it and still get your stuff.