Yes, you yourself can also suffer from that breakage, and worst of all, might no even notice it right away, so have a period of silent issues
Yes, you yourself can also suffer from that breakage, and worst of all, might no even notice it right away, so have a period of silent issues
But also, even in FOSS there can be projects that value stability and isolation, so if you fix some plugin that misbehaves you don't need to adapt because the underlying editor APIs that plugin relied on are stable and also isolated in a way where your changes can't break other users
> or something isn't working correctly.
the issue isn't whether a bug exists, it's whether/when you notice this
> Might this break some other deeply intertwined behavior someplace else? Probably
How do you know it didn't?
Someone may have observed it and fixed it someplace else, but from the point of OP it doesn't matter to them - their system still works "as desired". The world wasn't meant to be perfect for everyone, but you can certainly carve out your own "perfect" piece of it.
It seems you have only surface knowledge and little practice of using Emacs. You're not offering any evidence to your arguments and not suggesting any alternatives. Because there isn't a practical alternative that exists today to effectively replace Emacs. You're frantically trying to grasp for reasons not to use Emacs. Why are you looking for validation on an Emacs-themed thread? If you don't want to use Emacs, just don't. If you want to use Emacs but observing obstacles, then get more concrete, instead of complaining just for the sake of it.