2 ms·
> Backward compatibility. Ripgrep, I'm looking at you Is that really that important? I do have a few POSIX incantations ingrained into my muscle memory, but it
by kaba0 5y ago
> Backward compatibility. Ripgrep, I'm looking at you
Is that really that important? I do have a few POSIX incantations ingrained into my muscle memory, but it’s not a good thing imo. Is that 4 God knows what flag and strange order really that important? Maybe add a separate backward compatible mode when issued through the old tool’s name, but I would like at least a partial revamp of the frankly, not too ergonomic POSIX tools. While Powershell can sometimes be more verbose, I would prefer a similar convention.
- throwawaybutwhy 5y agoDefinitely important. It is a damper on gung-ho, brazen disregard for existing code/user base. It prevents code base rot and saves money for corporations/governments. It forces developers to adhere to the principle of least surprise, and ensures smooth user experience. Mind you, Powershell beats POSIX on readability hands down, and autocompletion would make longer, more readable options much easier to write. Still, the easiest way to increase adoption is to meticulously copy conventions from predecessors. Compatibility mode would be enough for most purposes if it's maintained and not dropped three years later in the name of progress and limited maintainer attention span.