Re:Etcd, or, why modern software makes me sad
by swagonomixxx on Tuesday July 14, 2020 @05:44PM
(#23838349)
While this is technically true, using old, unsupported versions of software (such as etcd) in production is a recipe for disaster, especially when you start running into problems with it.
I think, in the case of etcd, it would have been better for the k8s folks to fork the project and add whichever features they felt were needed to be able to use it for k8s. Instead, it seems like they swarmed the original project and added a ton of features that made it a behemoth of complexity rather than the simple tool it once was.
Re:Etcd, or, why modern software makes me sad
by pdonis on Tuesday July 14, 2020 @06:52PM
(#23839074)
> I think, in the case of etcd, it would have been better for the k8s folks to fork the project
This would only make a difference if someone was willing to maintain the non-k8s fork. From what I understand, nobody was willing to take that on, so the k8s version became the only version by default.
The thing is that with free software the old software is almost never really long gone. It's still out there, free for your perusal. That is the beauty of free software, it's always additive process. But it does also put responsibility on the user to pick the patches they want, either themselves or by proxy. Ultimately you are responsible for the free code you are running, not some vague upstream dominated by fnaag et al.