3 ms·
Thanks to the author for posting this. Thoughts, in no particular order: Repeatability: - We already have a dataflow graph, it's called makefiles - Going fro
by throwawaybutwhy 5y ago
Thanks to the author for posting this. Thoughts, in no particular order:
Repeatability:
- We already have a dataflow graph, it's called makefiles
- Going from shell commands to Ansible playbooks can be made easier
- Declarative, idempotent commands
- Integration with version control
User friendliness:
- GNU standards. If I cannot use --help and --version, I get angry
- Backward compatibility. Ripgrep, I'm looking at you
- Autocompletion is still in its infancy. Co-operative autocompletion is easy, and can be done by utility authors. What are the options (no pun intended) when the author would not update an autocompletion script? fzf and its kin greatly enhance user experience
- Performance. Accidentally quadratic stuff is a Cthulhu-scaled abomination
- Fancier prompts without needing to install extra software or add a bunch of PS1/PS2 scripts
'Novelties' (not so much, other OSes have had them before):
- Coprocs
- Easier parallelization
- Improvement in job control - freezing and thawing jobs, moving jobs to other hosts etc. K8s/kubeflow and friends
Security:
- Better integration with secret managers
- History cleanup when passwords are passed on the command line
- 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.
- burntsushi 5y ago> Backward compatibility. Ripgrep, I'm looking at you What specific backward incompatibilities have caused you problems?