I keep wondering about what seems to be the most important component of Unix philosophy: write many small programs that do one thing well...
I keep wondering about what seems to be the most important component of Unix philosophy: write many small programs that do one thing well and interface using text streams! Yes, modularity is important. However, in some cases, this philosophy has resulted in the "tangled mess held together by duct tape" kind of systems architecture that no one dares to touch for fear of breaking things. I think Unix philosophy is struggling with a fundamental dilemma: On one hand, creating systems from programs written by different people requires stronger formal guarantees in order to make interfaces more reliable, stronger guarantees than interfaces within one large program written by one person or a small team would require. On the other hand, creating systems from programms written by different people requires more flexibile interfaces that can deal with versioning, backward and forward compatibility, etc, something that is extremely difficult to do across programming languages without heaping on massive complexity (CORBA, WS-deathstar, ...) I think HTTP has shown that it can be done. But HTTP is also quite heavy weight. It doesn't exactly favor very small programs. Handling HTTP error codes is not something you'd want to do on every other function call. In any event, I think Unix philosophy is a good place to start but needs a refresh in light of a couple of decades worth of experience.
Posted by fauigerzigerk on Jun 25, 2015, 11:16 AM
Tags
Related issues
- It’s such an annoying problem to solve.
- > My point is, the impression many people will unavoidably take away from "many recalls" is that the vehicle must me in the shop all the ...
- [Feature]: Ability to merge old runs with a new run
- Add `findManyAndCount()` to return count of queried items
- One of the best, and first, things we did when starting our machine learning platform was to design it using a plugin architecture.
- gh pr push
Raise real-world problems, find people facing the same issue, and discuss solutions.5,500 issues0 comments
ux (E-commerce)
It’s such an annoying problem to solve.
> My point is, the impression many people will unavoidably take away from "many recalls" is that the vehicle must me in the shop all the ...
[Feature]: Ability to merge old runs with a new run
Add `findManyAndCount()` to return count of queried items
One of the best, and first, things we did when starting our machine learning platform was to design it using a plugin architecture.
gh pr push
[feature]: Sync Collections with Git repo
Repeated SSH disconnects/reconnects that eventually stabilizes (large folder)
I keep wondering about what seems to be the most important component of Unix philosophy: write many small programs that do one thing well...
I keep wondering about what seems to be the most important component of Unix philosophy: write many small programs that do one thing well and interface using text streams! Yes, modularity is important. However, in some cases, this philosophy has resulted in the "tangled mess held together by duct tape" kind of systems architecture that no one dares to touch for fear of breaking things. I think Unix philosophy is struggling with a fundamental dilemma: On one hand, creating systems from programs written by different people requires stronger formal guarantees in order to make interfaces more reliable, stronger guarantees than interfaces within one large program written by one person or a small team would require. On the other hand, creating systems from programms written by different people requires more flexibile interfaces that can deal with versioning, backward and forward compatibility, etc, something that is extremely difficult to do across programming languages without heaping on massive complexity (CORBA, WS-deathstar, ...) I think HTTP has shown that it can be done. But HTTP is also quite heavy weight. It doesn't exactly favor very small programs. Handling HTTP error codes is not something you'd want to do on every other function call. In any event, I think Unix philosophy is a good place to start but needs a refresh in light of a couple of decades worth of experience.
Comments (0)
No comments yet. Start the discussion.