71–80 of 95 posts
Why are we emotionally tied to command line interfaces Desktop apps are a second class citizen that do not get feature parity Lot of actions on Claude Code seem much more suited for a thoughtfully designed GUI Even the chat responses and links therein can benefit from judicious use of rich text and formatting and real hyperlinks to other parts of the UI or elsewhere Favourite Skills can be toolbar buttons or menus if…
Why are we emotionally tied to command line interfaces Desktop apps are a second class citizen that do not get feature parity Lot of actions on Claude Code seem much more suited for a thoughtfully designed GUI Even the chat responses and links therein can benefit from judicious use of rich text and formatting and real hyperlinks to other parts of the UI or elsewhere Favourite Skills can be toolbar buttons or menus if…
For one I’m not sure if I’ve ever gotten an ad in my terminal or in a tui. That alone is probably enough. And it’s so much harder to ruin the terminal experience compared to a desktop app. They don’t get pointless redesigns. I can customize them however I want. The terminal is a like an oasis in the current climate. And that before getting into utility.
Earlier quoted context omitted.
It is an handicapped REPL, not really the same. Such statements can only be voiced by those that never experienced what using a proper REPL actually feels like. Not something that emulates a vt100 teletype.
The "vt100 teletype emulation" only concerns the protocol in which the program describes what to draw on the display. It might be inconvenient for the programmer, but for the user it is kinda irrelevant. > Such statements can only be voiced by those that never experienced what using a proper REPL actually feels like. Maybe. What do you mean with proper REPL? SBCL just runs fine in my terminal emulator. As do all othe…
Inline graphics from 1981,
https://youtu.be/o4-YnLpLgtk?t=376Or
Or using S-PACKAGE used to develop Nintendo 64.
https://www.youtube.com/watch?v=gV5obrYaogU
You are missing integration with live debugging, calling anything on the OS during a REPL session, e.g. OS APIs, calling into automation points of the OS,
Can try out directly on the browser, courtesy of WebAssembly and recovery of Xerox PARC software, https://interlisp.org.
Or get either Squeak or Pharo, and see how using the Transcript integrates with the whole platform
Windows, with either PowerShell ISE, or its new VSCode integration, are the closest to these kind of experiences.
To finalise with Xerox PARC view on UNIX, from 1989
"UNIX Needs A True Integrated Environment: CASE Closed"
https://www.bitsavers.org/pdf/xerox/parc/techReports/CSL-89-...
Earlier quoted context omitted.
Not everyone here is *nix-pilled (WSL aside). Despite W11's missteps, Windows isn't a completely terrible OS to work on and has some of the best window management outside of a full tiling WM.
I doubt it, Window management has been where MS Windows has been lacking for decades, at most they have caught up. Can you do "Always on top", "Always on the bottom" yet? That's a very basic and easy to implement feature.
Earlier quoted context omitted.
For one I’m not sure if I’ve ever gotten an ad in my terminal or in a tui. That alone is probably enough. And it’s so much harder to ruin the terminal experience compared to a desktop app. They don’t get pointless redesigns. I can customize them however I want. The terminal is a like an oasis in the current climate. And that before getting into utility.
Well powershell is a pointless and optical nausea redesign of a shell. I would not call it design per se .. or maybe it was. ?
> ps aux | awk '{if ($6 > 102400) print $11, $6}'
compared to
> Get-Process | Where WorkingSet -gt 100MB | Select Name, WorkingSet
doesn't matter how the output is formatted, you aren't manipulating text directly you're working with .NET objects.
Anyway, PowerShell is the way it is out of necessity of the OS. Microsoft did try to just port ksh to Windows at one point it obviously failed because Windows isn't text based, system state is stored in WMI, COM, etc not text files.
Snover talked about the creation of PowerShell on the Corecursive podcast a couple years ago, well worth a listen: https://corecursive.com/building-powershell-with-jeffrey-sno...
Earlier quoted context omitted.
I really don't get it. Started using computers when that was the only affordable way to use computers. For some reason, some people really love to live in 1970's with their expensive HiDPI monitors.
It might be overcompensation. I think UI, UX and GUIs got better up until the 90s, and early 2000s, but then somewhere GUIs suddenly got a lot worse. So a modern CLI is better and more standardized than a modern GUI.
Electron is the reason, and the elusive dream of "write once, run anywhere" that got us cross platform UIs that are bespoke and don't follow native OS conventions (or keyboard navigation), plus once marketing got involved and GUIs started needing to be branded instead of just fitting in with every other native app on that OS.
This is still better than trying to paste text, files or images in Linux. In latest Pop!_OS I have to keep the app I copy from open until I paste. To add insult to the injury, pasting in terminal produces weird characters.
Earlier quoted context omitted.
pass the url (local or otherwise) of the image to Claude code. Otherwise it's not the terminal's problem, please don't pressure Microsoft to introduce an attack vector to wsl for slop's sake.
The image in my clipboard doesn't have an url.
Why would anyone assume that pasting an image into a CLI interface would work? The fact that this is framed as a bug is wild to me (but very cool that there is a way to do it now)
1) It isn’t a matter of literally “pasting into a terminal” (with the terminal emulator shoveling bytes into the TUI’s stdin), rather it’s “a TUI key-binding tells TUI app to read system clipboard”. No different than any other app.
2) This works on macOS, Linux and Windows, but not WSL. Sounds fair game to call this a bug, or at the very least a feature disparity.