3 ms·
IMHO it's really the way Linux and other Unix-likes do dynamic linking that's "not a good thing", as well as the "hypermodularisation" that Linus alludes to (th
by userbinator 6y ago
IMHO it's really the way Linux and other Unix-likes do dynamic linking that's "not a good thing", as well as the "hypermodularisation" that Linus alludes to (the left-pad fiasco would be an extreme example of that.)
- incrudible 6y agoLeft-pad wasn't really a fiasco. It briefly broke a couple of people's build. If anything, it showed how resilient the system is. People are actually starting to use NPM as a system package manager. Meanwhile, dependency hell on Linux distributions keeps people stuck on outdated versions of software, because some piece somewhere is either too old or too new.
- VWWHFSfQ 6y ago> It briefly broke a couple of people's build. do you think this is an accurate characterization of what happened
- incrudible 6y agoIt's an accurate representation of the actual technical fallout. As for the "this is a sign of the end times" narrative that has been spun around it, it's mostly just for the headlines. I wouldn't even disagree that it is a sign of the end times, but practically speaking, it just wasn't a big deal.
- marcus_holmes 6y agoWindows does DLL's too
- gsich 6y agoTrue, but I have seen software where the DLL files are in the directory where the EXE lies. So copy+paste from another computer works just fine (in most cases). This does not really work in Linux.
- heavyset_go 6y ago.so, .bundle, and .dylib files also exist on macOS.
- TeMPOraL 6y agoWindows prioritizes DLLs sitting next to the application over ones installed system-wide, so you can ship your DLLs with your app, gaining all the benefits of static linking while not losing the benefits of dynamic linking.