4 ms·
Christ on a motorboat, this entire article is a poster boy for Chesterton's Fence. > To begin with, it's weird that versions are strings. Parsing versions is n
by masklinn 9y ago
Christ on a motorboat, this entire article is a poster boy for Chesterton's Fence.
> To begin with, it's weird that versions are strings. Parsing versions is non-trivial. Let's just make them a tuple. Instead of "3.0.2", we'll say "(3, 0, 2)".
3.0.2 alpha 6 says what?
> Next, move the major version to part of the name of a package. "Rails 5.1.4" becomes "Rails-5 (1, 4)". By following Rich Hickey's suggestion above, we also sidestep the question of what the default version should be. There's just no way to refer to a package without its major version.
And maintainers, being already loath to bump the major, start bumping only the minor on breaking changes.
> And that's it. Package managers should provide no options for version pinning.
And now if the maintainer breaks the package (either wilfully or without noticing) the user is shit out of luck and jolly well fucked.
> A package manager that followed such a proposal would foster an eco-system with greater care for introducing incompatibility.
I've got this very nice bridge you may be interested in.
> Packages that wantonly broke their consumers would "gain a reputation" and get out-competed by packages that didn't
There is literally no reason for that to happen any more than it currently does.
> The occasional unintentional breakage would necessitate people downstream cloning repositories and changing dependency URLs
So pinning would still exist except you'd have to fork the project you depend on, and would forget to update it ever after? Yeah that doesn't sound like a recipe for complete disaster.
> As a result, breaking changes wouldn't live so long that they gain new users.
Call me back about the bridge thing, you'd love it.
> if you change behavior, rename.
Unless you don't care, or don't notice, then don't, and the whole edifice falls down once again.