3 ms·
well expanding on that analogy, if you don't have your own workshop and/or don't want to spend time setting one up, then getting use of a shared community works
by jemmyw 2y ago
well expanding on that analogy, if you don't have your own workshop and/or don't want to spend time setting one up, then getting use of a shared community workshop would be fine. Especially if all the drawers are labelled, and it has all those peculiar machines you didn't think you'd need but actually turned out to be very useful. Yes, others made some decisions and now you have to follow those, but that is more often a positive thing than a burden.
- elric 2y agoI feel like I'm stretching the analogy beyond credulity here, but there's also a lock on the workshop and you can't leave it without finding a pair of bolt cutters. I mean I do think the original article is an exaggeration (as is this analogy), and there are lots of tradeoffs to be made. E.g. in the Java ecosystem it's much easier to find a Spring Boot developer than someone who is willing to set up a project from scratch. Maybe that's a good thing for your project, but maybe it's not.
- jemmyw 2y ago> I feel like I'm stretching the analogy Maybe more apt would be that the stuff you built in the workshop doesn't fit out the door so you'd need to take it all apart to rebuild it somewhere else. Still, the article is insensible. Frameworks are not evil. They do not have malicious aims. I think the worst we can say in that direction is that people get tribal about this kind of thing and insist their framework or way is the best and lose objectivity.