> Nothing is stopping you from designing a dense and economical GUI. Then why isn't it done more often? I suspect part of the reason is that most gui frameworks are not really designed for making dense economical interfaces. > you probably don’t need a user interface on prod. You need a command line interface on prod that I don't need one, but I often want one. Being able to run vim, htop, etc. on servers is quite us…
> Then why isn't it done more often? Because it tends to require a lot of thought and effort along totally separate engineering pathways than most of the actual functional coding. Good UI design is not easy, and the skills to do it don't directly overlap with good coding skills. It's hard. > I suspect part of the reason is that most gui frameworks are not really designed for making dense economical interfaces. Don't…
Stop Making TUIs
471–480 of 580 posts
Re: Stop Making TUIs
#472Earlier quoted context omitted.
GUI programs can also use the keyboard.
A lot of us do the vast majority of our non-browser work on remote systems. GUIs are objectively bad for this
Re: Stop Making TUIs
#473Re: Stop Making TUIs
#474Earlier quoted context omitted.
GUI programs can also use the keyboard.
A lot of us do the vast majority of our non-browser work on remote systems. GUIs are objectively bad for this
Re: Stop Making TUIs
#475Earlier quoted context omitted.
A lot of us do the vast majority of our non-browser work on remote systems. GUIs are objectively bad for this
Terminal programs are GUIs. So you are using a GUI to access those remote systems. Thus, there's no reason why another GUI couldn't do the same. Everyone always acts like GUIs couldn't possibly make HTTP requests, interact over TCP or WebSockets, or do other remote communication. But they're actually, more often than not, more well suited for that than browsers for specific use cases, which are the use cases where yo…
Re: Stop Making TUIs
#476Earlier quoted context omitted.
TUIs run on any OS with minor patches to support quirks, GUI frameworks need a lot of work. TUIs don't need to follow any OS guidelines, cross-platform GUIs always look bad outside of the "main" platform. If you're only targeting macOS/Windows/Gnome/KDE then the solution is easy: just grab a GUI control set and go ham. Then there's remote access: you can spawn an X11 app through X forwarding and have a terrible laggy…
> TUIs don't need to follow any OS guidelines, cross-platform GUIs always look bad outside of the "main" platform. TUIs look bad everywhere, so that's strictly worse
I would definitely be pro minimalist unicode-character-themed GUIs for what it's worth. Where every graphical primitive is basically a unicode character, without the restriction on font size.
Re: Stop Making TUIs
#477Hard disagree. Make more TUIs! TUIs have downsides like accessibility, poor mouse support, but work really well if you focus on keyboard input. It is a better/faster input mode to begin with, especially for power users, but also for average people; you'd be surprised at how much more user-friendly an arrow-keys driven UI can be vs modern web interfaces. I've been building my own TUI framework [1] and getting amazing…
I'm very keyboard-driven but I never really got TUIs. A GUI litterly can have just as good keyboard support, but because it doesn't force the user to use it, they rarely take the time to learn it. It's just always tempting to take the path of least resistance. Especially becuase TUIs doesn't really have any of good properties that a CLI offers such as composebility. It's still a fixed UI with panes and menus which ha…
Re: Stop Making TUIs
#478The typical TUI fan is a nerd with no clue about typography so therefore they don't notice any problem with being shown elements that have no reason to be monospaced in monospace. i.e. ignorance is bliss in the world of typography.
Perhaps the average TUI fan is someone who correctly recognizes the negligible relevance of typography in optimizing their computing workflows, and prefers monospace fonts for purely functional reasons, which naturally take precedence over merely aesthetic concerns when working with functional tools. The total abandonment of the form-follows-function principle on the part of purely visual designers, who worry about w…
Just because there have been some crappy industry trends doesn't mean the answer is to turn away and permanently regress to the confines of a terminal emulator.
Re: Stop Making TUIs
#479Re: Stop Making TUIs
#480Earlier quoted context omitted.
> TUIs don't need to follow any OS guidelines, cross-platform GUIs always look bad outside of the "main" platform. TUIs look bad everywhere, so that's strictly worse
TUIs would be great if they didn't have to render all text the same size, for me that's the main win with GUIs, you have total freedom with what you can do with your pixels. I would definitely be pro minimalist unicode-character-themed GUIs for what it's worth. Where every graphical primitive is basically a unicode character, without the restriction on font size.