|
|
|
|
|
by gravypod
3715 days ago
|
|
What is this intended on fixing? I don't think the solution to anything is to make the shell more user-friendly. The only solution is to make the graphical user-interface more user friendly and feature full. The only time it should be acceptable to be forced to use a shell, in my opinion, is if you are swapping out your desktop environment. Until that happens, Windows and OS X will rule the desktop and PC market. I'm fairly certain that Linux-based distributions will win out in the end if we can overcome this clingy gravitation to a command line. It's already happening already. Android is already winning against all of the major phone platforms and it's not because of it's award winning terminal emulator. |
|
There's only one feature that matters here, really: composability. Provide an environment in which I can compose simple tools into complicated workflows I can fling data through, and we might have a winner.
> The only time it should be acceptable to be forced to use a shell, in my opinion, is if you are swapping out your desktop environment.
Why should that be true? It's not at all obvious to me. I have yet to see a GUI that lets you express something like `grep '^127' /etc/hosts | awk '{print $2}'` in any sane fashion. The closest you get is something like LabView, but that's counted out here because it's a general purpose(ish) language.
If your response is that this type of task is artificially skewed towards a text-based, shell-centred environment, then you don't have the type of problem that this shell is intended to fix.