←back to thread

320 points IroncladDev | 1 comments | | HN request time: 0s | source
Show context
rollcat ◴[] No.43670593[source]
I don't understand the obsession with 1980s terminals. They're even less powerful than the contemporary 8-bit home computers. It's perfectly OK to be a retro enthusiast, it's another thing to claim that this is the peak tech to power our modern CLIs, or a solid foundation for portable UIs.

From the docs:

    Stop thinking in standard CSS units like px, em, rem, %
    Start thinking in Character Cells for spacing, sizing, and positioning
A VT102 already has a character grid, but it needs a serial protocol to allow applications on the mainframe to talk to it. You can loop around this and use the raw mode to address individual cells.

The web browser has an insanely powerful typographic and layout engine. Now we're looping back into character cells. Something went wrong here, at least once.

That said, I like the aesthetic and the default color palette. It's quirky, but it has its places.

replies(13): >>43670672 #>>43670690 #>>43671003 #>>43671094 #>>43671420 #>>43671663 #>>43672234 #>>43673068 #>>43673112 #>>43674448 #>>43675035 #>>43676127 #>>43678300 #
sgt ◴[] No.43673068[source]
Occasionally when you see someone using a point of sale terminal that is terminal based, the operator usually flies through the interface like it's nothing.

So there's something to be said about those types of interfaces - it may look simple and be text based, but it's the most user friendly for the qualified operator to get things done.

replies(9): >>43673184 #>>43673437 #>>43674068 #>>43674162 #>>43674856 #>>43675041 #>>43675287 #>>43676230 #>>43715667 #
kmeisthax ◴[] No.43674162[source]
Good GUI apps have shittons of keyboard shortcuts to achieve the same result. The ideal is that the qualified operator keeps their hands on the keyboard for anything that isn't an actual pointing operation. For example, in a video editing app, you can rough-cut with a handful of keys[0] for setting in and out points, jogging through the source material, and inserting into the current active timeline. The keyboard isn't a mere text input device, it's a large-ish macro pad with a huge number of redefineable keys, and it will always be faster to press a button with a known location versus opening a menu and clicking an option by name.

Related: I really liked Blender's text-searchable menus and I wish every GUI app had searchable menus. It's faster than hunting through a static hierarchy. In fact, one of the few criticisms I have of the 4.x era Blender UI is just that it's mildly harder to invoke search.

[0] Which is how linear video edit consoles worked before modern NLEs, mind.

replies(2): >>43674288 #>>43674612 #
geocar ◴[] No.43674288{3}[source]
> every GUI app had searchable menus

They do on mac: shift+⌘+? opens a "search menu" menu.

replies(3): >>43674742 #>>43675095 #>>43675235 #
1. kmeisthax ◴[] No.43675095{4}[source]
OH MY GOD. I never knew about that.