> The people that keep arguing for TUIs for everything seem like religious fundamentalists that can't be convinced with any argument that user interfaces should be about the user, and need to adapt to the task at hand.
We are users.
> Why can't developers understanding that GUIs and TUIs both have their usage, it just depends on the task?
Isn't that the case for most TUI apps? They tend to serve quite specific purposes. Nobody writes a WYSIWYG word processor in a TUI. Because you can't and even if you could somehow with sixels it would work horribly bad.
In a dual role, I would say that the most impactful aspect (being a developer) matters more.
> Nobody writes a WYSIWYG word processor in a TUI.
But at the same time people write all sorts of other apps that could hugely benefit from a GUI. I seems like if the output itself is not graphical, TUI-enthusiasts won't acknowledge the advantages of a GUI layer, while only bringing in arguments why they can implemented poorly.
GUIs have a much higher surface to be done wrong, so standards are higher. But there's still a decision that needs to be weighed carefully, and many developers seems to simply jump on the TUI bandwagon just because it's easier.
I don't think a TUI is easier tbh. It's certainly more economical on resources, that's for sure. Really amazing programs running in 35k or so, compared to hundreds of MB for a whole electron stack. The more decent platform native and Qt apps are nicely in the middle but they are kinda becoming extinct. Even Microsoft is just serving us electron slop these days (though they call it something else)
But a TUI needs dedicated understanding of terminal toolkits. That's not easy. A GUI is much more easy mode with electron, a bit of javascript and a GUI toolkit to design the UI, easy peasy. To me the TUI is the hard option.
I really enjoy TUIs though. I wish there was something like vscode in TUI. I like the responsiveness and the no-nonsense. No logos and other commercial bullshit, no huge amounts of whitespace that UX designers consider "best practice", just highly dense data.
Also, I've worked with some of these designers and their holy best industry practices have nothing to do with anything that benefits the user. They're all like: "Is the logo clear enough", "Does the user get drawn to the parts that make us the most money (like ads or premium articles)", "Is the user finding the thing we want to promote".
To me all websites should look like Hacker News does. Not like a "modern" newspaper site does.
We are users.
> Why can't developers understanding that GUIs and TUIs both have their usage, it just depends on the task?
Isn't that the case for most TUI apps? They tend to serve quite specific purposes. Nobody writes a WYSIWYG word processor in a TUI. Because you can't and even if you could somehow with sixels it would work horribly bad.