Using C# implies that you're running on a device powerful enough for a traditional GUI.
(And you really don't need much to run C#, just enough RAM / Disk for the framework and to handle the overhead of the garbage collector.)
Using C# implies that you're running on a device powerful enough for a traditional GUI.
(And you really don't need much to run C#, just enough RAM / Disk for the framework and to handle the overhead of the garbage collector.)
You can run SSH as a server on windows boxes easily now, and depending on your needs (or to standardize across a heterogeneous fleet of servers) it might make sense to have some good CLI/TUI utilities available that are cross-platform.
While I imagine most people won't jump to a TUI for Windows, it could also be a secondary interface for an application that's run on both Windows and Linux/BSD. If no GUI (or no Windows GUI) is detected, approximate the same display using a TUI. The guys of the application can be the same, and you don't have to ship two versions (assuming the rest of the internals area already portable).
Then maybe a cool project is an adapter to allow the text-based GUI to work natively when running in a GUI!
It's really useful to have things work in the shell directly.
I am not even an old fart. I am barely 30, but I feel completely backwards with regards to all developments in modern computer interaction. I hate smartphones. I hate the modern web. It all feels like one big distraction.
GUI's have their place, but damn is i3 + terminal super productive, no matter what the naysayers think.
In principle, all of these things could be done with a GUI, but in practice, they're not, and with the phoneification of software, the keyboard is an afterthought, not the main input mechanism.
Because the backbone of the modern computer's infrastructure is comprised of software running on headless systems accessed with remote shells.