4 ms·
The tendency to go for most popular library/framework/etc, with all the assorted justifications (which are valid to a degree and thus misleading) is an indicati
by denoma 6y ago
The tendency to go for most popular library/framework/etc, with all the assorted justifications (which are valid to a degree and thus misleading) is an indication of just how rampant cargo culture is in software. Everybody always looking for the default thing to throw at the wall, hoping it solves their problem. And it’s fine, for prototyping and fast growth “products” (really mvps and demos) but with anything serious you must do the required legwork to figure out what is actually needed, and it’s often best to limit dependencies on external libraries and frameworks as much as possible.
- gridlockd 6y agoI disagree that this is cargo culture. I'm not arguing for people to follow the latest hype, or do what everyone else does, in the hopes of winning. I'm saying that if you have the choice between a handful of projects that solve more or less the same problem that you actually have, just going with the most popular one is probably going to be the best choice, because having all these other people in the same boat is valuable. I agree with limiting dependencies and points of failure, but that's orthogonal.