3 ms·
>The best packager in any tech wave wins though, and wins big. Since this feels the like main point of the article: what makes the "best packager"? The only co
by ivanbakel 9y ago
>The best packager in any tech wave wins though, and wins big.
Since this feels the like main point of the article: what makes the "best packager"? The only complete stacks I've ever enjoyed using broke their own philosophy and let you integrate external tools, because that's what you're already using. Does the "best packager" somehow produce a package which is the best in all aspects, or do they make the most widely-used package - in which case, they'll shatter the monolith more often than not.
The example that comes to mind is Microsoft's VCS built into their TFS stack. It is a pain to use from personal experience, but the most grating thing was the centralisation - if you need a decentralised solution, you'll probably end up using Git, and MS support it for that reason. Does this make TFS good for being useful, or bad for failing to meet needs?
- flukus 9y agoWith TFS, integration seemed to be about the only selling point, every single component was mediocre at best. But the sales model of TFS was a bit different, they weren't selling to devs, they were selling to management, who only look at the big picture. Rather than being a better SVN, MS seems to have tried to build a better clear case. They weren't trying to be the best packager, they were trying to create the best monolith from scratch.