10 ms·
Think about all those dependency management systems (npm, Maven, NuGet). Look at a project with huge number of dependencies, picking on piece of functionality f
by jpalomaki 10y ago
Think about all those dependency management systems (npm, Maven, NuGet). Look at a project with huge number of dependencies, picking on piece of functionality from one library, something else from another. All tied together with some depedencies file and maybe with some additional dependency injection magic. Not backed up by version control, but instead the package repository.
Not that many projects add a real DSL, but I think you can end up pretty close also with just objects and language features.
And where do you then run this system? Of course in Docker container, probably picking up Linux components with apt-get from left and right.
- AgentME 10y agoThe bad things in the article were the inner-platform effect and that the inner-platform was especially terrible (no comment support, tons of boilerplate, abuse of the project's own source control, lack of dev/production split). I really don't think the concept of versioned dependencies was one of the bad parts.
- emsy 10y agoSure dependencies can become absurd (like the NPM left-pad story). But should we on the other hand always code everything from scratch? Where does it end?