4 ms·
> I won't install a new shell to generate a file list on my CI server. I won't install a new shell on remote machines. Ever. Uh... that's on you? Why do you in
by g15jv2dp 2y ago
> I won't install a new shell to generate a file list on my CI server. I won't install a new shell on remote machines. Ever.
Uh... that's on you? Why do you intentionally hinder yourself?
> These structured shells also require commands to be aware of them, either via some plugin that structures their raw I/O output or some convention. They solve _some_ command output structuring but not _all_ the general problem.
Okay. It doesn't solve literally every single problem, that is true. It's still miles ahead. And when interfacing with non-pwsh commands, you just fall back to text parsing/output.
- alganet 2y ago> Uh... that's on you? Why do you intentionally hinder yourself? Hinder myself? An ephemeral cloud machine would not keep my custom shell anyway. By having to install it _every single time I connect_ I just loose precious time. I want to be familiar with tools that are _already_ installed everywhere. The shell is supposed to be a bottom feeder, lowest common denominator, barely usable tool. That way, it can build soon and get stable real fast. That (unintentional) strategy placed it as a core infrastructural piece... everywhere. Of course, there's scripting and using it on the terminal. But we're talking about scripting, right? Parsing ls and stuff. I want the fast, lean, simple `dash` to parse my fast, lean simple scripts. pwsh is fine for the terminal leather seats.
- Kwpolska 2y agoEphemeral cloud machines are created from images. Build your own image with the tools you need.