3 ms·
That is the sorry reality of the bazaar Raymond praised in his book: a pile of old festering hacks, endlessly copied and pasted by a clueless generation of IT "
by EGreg 9y ago
That is the sorry reality of the bazaar Raymond praised in his book: a pile of old festering hacks, endlessly copied and pasted by a clueless generation of IT "professionals" who wouldn't recognize sound IT architecture if you hit them over the head with it. It is hard to believe today, but under this embarrassing mess lies the ruins of the beautiful cathedral of Unix, deservedly famous for its simplicity of design, its economy of features, and its elegance of execution. (Sic transit gloria mundi, etc.)
I can say that, for the last seven years, I ran our little company as a Cathedral and not as a Bazaar.
We didn't import many packagess in PHP. We wrote our own code and made sure it integrated well with everything else.
We didn't run package managers and didn't freeze versions. We wrote all our own stuff in the app layer.
I can tell you, it's been... interesting. We know at the end of the day we are responsible for fixing stuff if it breaks. Not waiting for someone else to approve our pull request.
Since Raymond's book, something major happened: DISTRIBUTED VERSION CONTROL SYSTEMS such as git became mainstream.
So now you can build cathedrals IN THE BAZAAR!
Anyone who wants to maintain package X can fork it and maintain it. Maintainers gossip their improvements in a sort of blockchain consensus protocol. If a maintainer falls behind, the package continues to be maintained by others.
What I would like to see is MORE emphasis on content-addressable streams of data with history, instead of on the domains / urls from which they are fetched.
In other words, more IPFS and less HTTP.
That is the best of both worlds, and I describe it here: https://github.com/Qbix/architecture/wiki/Internet-2.0 https://github.com/Qbix/architecture/wiki/Internet-2.0