61–70 of 123 posts
The future repeats the past. This looks much like the back-end systems I used to design on TurboPascal in the late 1980s / early 1990s. https://ilyabirman.net/meanwhile/pictures/tp-80.png
It seems like Python and Node are not good choices for command line tools. Rust or Go make a lot more sense as your end users won’t have to install any libs or package managers. Single binary distribution ftw.
pip is installed by default on mac and linux. For non posix experienced users, pip installing packages is actually easier than figuring out how to put a binary on the path. Not to mention, updates are just a command, you dont have to go find the url, redownload, and replace the binary.
Earlier quoted context omitted.
I miss the simplicity and utility of textual UIs. Nothing unneeded, and everything you need. No filler. No giant gaps between elements or wasted pixels. No fads which do silly things like hide scrollbars or other interactive elements. Except for CAD applications and some games, almost everything we do online today could be accomplished via textual UI. Almost the entire internet could be replaced with TUIs and a lot o…
Where's lynx when you need it? [0] [0] https://lynx.browser.org/ And I might add, it's the oldest web browser still being maintained. Since 1992.
Earlier quoted context omitted.
I miss the simplicity and utility of textual UIs. Nothing unneeded, and everything you need. No filler. No giant gaps between elements or wasted pixels. No fads which do silly things like hide scrollbars or other interactive elements. Except for CAD applications and some games, almost everything we do online today could be accomplished via textual UI. Almost the entire internet could be replaced with TUIs and a lot o…
> They're probably a lot easier for screen-readers, too. That might be true for more minimal TUIs, but I don't think most screen-readers can handle the multi-paneled ones like OP.
Emacs as a platform is a good example here - the TUI that you can achieve in it is similar to web GUIs made of standard components - in the the UI isn't just pixels on a 256-bit canvas, but it's made of building blocks that you can inspect, select, copy, and that gracefully enhance/degrade when you switch between graphical and terminal modes.
Earlier quoted context omitted.
Where's lynx when you need it? [0] [0] https://lynx.browser.org/ And I might add, it's the oldest web browser still being maintained. Since 1992.
Why does this website write "Un*x" as if it's some kind of swear word?
Earlier quoted context omitted.
I miss the simplicity and utility of textual UIs. Nothing unneeded, and everything you need. No filler. No giant gaps between elements or wasted pixels. No fads which do silly things like hide scrollbars or other interactive elements. Except for CAD applications and some games, almost everything we do online today could be accomplished via textual UI. Almost the entire internet could be replaced with TUIs and a lot o…
I agree with your claims about the potential advantages of a TUI, but in this case, almost all of these TUIs using Rich will be running as GUI graphics inside a GUI window on top of a GUI OS subsystem, driven by an interpreted Python subsystem, all on an OS juggling many other simultaneous deep-stack processes. In other words, it's a keyboard-driven GUI app making use of the GUI advantages to provide you with your ch…
In it, Mr Murray live-codes a simple program to display all 256 characters in the C64's character set, by directly poking them into video memory (that's close to the metal, right?).
Once in BASIC, and once in machine code, to show the contrast in speed. It's pretty impressive even now, and that's running on a 1-MHz 8-bit processor. :)
It seems like Python and Node are not good choices for command line tools. Rust or Go make a lot more sense as your end users won’t have to install any libs or package managers. Single binary distribution ftw.
Check https://github.com/fdehau/tui-rs for example.
Author of Rich here. Happy to answer any Rich related questions.