I'm quite opposite. I avoid any places that don't accept card payments, because it usually means they are avoiding taxes. And I don't have cash on me, or wallet. Only phone or sometimes only my garmin watch (with garmin pay).
Being behind Iron Curtain I sold (well, my parents, I was too young) my Atari 65 XE + tape reader (which I received as a gift in 1988) and got C64 (the original ovalish one) with 1541 in 1990, it was bundled together with a set of hundreds (pirated of course, that was the reality back then) of 5 1/4" discs with various software and games. It was like receiving internet in a package.
Entering incantations like: "LOAD .... 8,1" (I don't remember the middle part).
Or playing with assembly with LDA, STA (or same for X and Y) was fun.
> "LOAD .... 8,1" (I don't remember the middle part).
Interestingly this was sort of the beginning of the end of digital computers as an operator-centered environment. So, the LOAD command took three arguments: the first was a filename (which was typically the first/only file in the directory for commercial disks, so the wildcard "*" was typically used); the second was a device number on the bus (8 was the first floppy drive by convention, though you could set things up differently if you knew what you were doing), and the third was a flag that specified the file format (0 was a BASIC program, 1 was a binary file to be loaded at an internally-specified address).
Not too weird, but that's all you got in Commodore BASIC. Unlike other platforms, there was no "autoexec" or "boot sector" or whatnot to get the system/disk to do the right thing at power-on. You had to do a little work at the start to bootstrap the system, not unlike the console of a PDP-11 or whatnot.
But everyone hated it, no one wanted to learn it, and everyone just ended up typing the "incantations" in from the manual without bothering to learn the specifics, which obviously weren't important. The C64 was probably the last such system (or last popular system) shipped, where an "operator" was expected to do bootstrap work.
Oh sure, but that was a hack. The rest of the market (even in 1982) had already moved on, c.f. the ROM on the 1978 Disk II card that could load and run a boot sector automatically. Having an "operator" was a design paradigm, and my point was that it was already antiquated even then.
It depends, for me it is boring and has pretty dim graphics. I wanted to love it, but it is not fun. It looks like a Sims game, it lacks what e.g. factorio has, that "spark".
DF sounds like it might have that "spark", but I'm afraid to touch it.
Benefit of TUIs is that sometimes they are extension of CLI.
Sometimes I can use `du` to check what uses so much space, but sometimes ncdu is better for me.
And the best part - I can use both when I ssh to another machine, using the same command line, without thought. While GUIs need added thought, to switch from CLI to GUI on the remote one would need to use a different interface, or have X11 forwarding on (which is also a good option) and x11 libs on the other side.
Or use some other connectivity. ssh is simple, works on most servers I have access to.
> And the best part - I can use both when I ssh to another machine,
Exactly. I'm currently on vacation and has checked in on long running Claude Code sessions over ssh every few days. I could have used X11 forwarding or VNC if I needed a GUI app, but the connection I'm on is currently slow and unstable, and using text mode has been far more palatable, especially since I can use tmux (or in the case of Claude Code, just using "claude agents" and let it background the sessions itself).
Not so. GUIs absolutely should be keyboard-drivable, if they're written to the human interface specs of whichever platform they're hosted on. That doesn't mean they don't support being mouse-driven or even that mouse isn't the default, but in my experience if the developer has taken any sort of care with the interface then keyboard interaction will be at least as good, if not better, with the keyboard.
> And TUIs are only keyboard driven.
Not true either. There's a line in my .vimrc saying "set mouse-=a" specifically because I want to turn off the mouse in that particular TUI app. If a TUI app doesn't support the mouse they've just not added that support, it's not that it's not possible.
Keyboard-driven GUIs belong in the realm of a lost art called "accessibility", which enabled people with motor issues (amongst many others) to use applications without a mouse.
FWIW, most of Windows XP's utilities and included software was perfectly usable with a keyboard alone.
I have credit card only to be able to rent car on vacation. It is not used outside of that. For other payments I use debit card.
reply