(if you're here for the software mentorship rant, click here to make sure you're seeing the whole thread. experimental cohosting is confusing right now)
this became a thread. For the sake of everyone’s feed, you’re gonna have to read-more instead of skim.
Read More
### does it work? yes, but. ### is it good? ... yes. ### does it break things you find intuitive? yes. ### are there productivity tools that only exist on it, that make people so efficient they cannot use anything else without a noticable slowdown? yes ### does it have behavior that only makes sense with 30 years of context? absolutelyso why use it
because if you need it to do something, with enough patience you can make it do it. Sure, you could have made a specific utility that could do it better, in less time. But you wanted it to be useable outside this one context.
unfortunately, your config has drifted so far from the standard that it is now a unique product, useable only to you, and you are writing plugins for that, and no longer the actual application
At least take this machete.
You'll need it when you find the trailhead someone else started and left unmaintained, forging a path only to let it disappear for those behind them.
and in the end?
You'll be powerless to stop it; who has the spare cycles? Your fork, then too, will be unmaintained. It's just the way of things.
Things move too fast.
After all, that's why you picked the wrong tool in the first place. It was there. Didn't need to get comfortable with something else, or grapple with standards, with maintainers.
it's not like there's a choice at the moment. It's also why there's some things locked in zsh that are now being reimplemented in fish and NuShell, even though having them be external would be even better. But that requires more time.
No one's got time for that.
But at some point we have to realize "If it sucks, hit da bricks" is the reason there's just guns pointed at feet lying everywhere.