4 ms·
Then you put all your dependencies on top and realise how large that is and that by bundling their dependencies with those dependencies security becomes a probl
by noir_lord 10y ago
Then you put all your dependencies on top and realise how large that is and that by bundling their dependencies with those dependencies security becomes a problem keeping everything up to date so someone comes up with the idea of sharing some of those dependencies and since they are common across multiple things they need a snappy name...hmm, sharing and re-usable how about..libraries, shared libraries in fact.
I jest but as an industry we do seem have an almost metronome-like tendency to lurch from one thing and back.
- walterbell 10y agoLurching is a proven technique for displacement of incumbents.
- pjmlp 10y agoYou can share libraries without having an underlying OS, a rich runtime playing OS role is enough. For example, all JEE containers allow for sharing libraries among applications, and they can be running bare metal for what I care. I can even control in which order they get loaded in each application.
- deleted 10y ago[deleted]
- MrBuddyCasino 10y agoOh the horror. Thank god we don't do that anymore.
- eveningcoffee 10y agoUnfortunately, or fortunately this is still what we do. Even on the web scale.