3 ms·
The counterpoint is that every software project of reasonable complexity evolves its own language anyway. When that is layered on top of overly generic librari
by pavlov 7y ago
The counterpoint is that every software project of reasonable complexity evolves its own language anyway.
When that is layered on top of overly generic libraries/frameworks, you may end up using only parts of the underlying vocabulary. Now the project is stuck with two vocabularies. Learning the generic one doesn't get you far and may be actively misleading ("yeah, we never use features X and Y of the framework, instead we've overridden Z with our own implementation that does all this plus W").
- skybrian 7y agoYes, that's a problem with code sharing gone wrong. Another problem is framework churn where popular libraries aren't stable. When good, stable libraries aren't available then it may be better to reimplement than to use a bad one. But these problems are, in their way, a sign of success at the package management level. If you don't have good package management then people probably aren't having much success at sharing code. We should still aim for building and sharing stable, well-understood, high-quality code libraries. Unfortunately, sometimes the way to get there is to go through a period of instability.
- eckza 7y ago> We should still aim for building and sharing stable, well-understood, high-quality code libraries. And I agree with that 100% - but that isn't the solution to every single problem. That's all I'm saying.
- kharak 7y agoI'm also for a common vocabulary, but I wonder why you're getting downvoated for having another opinion.