Hacker News new | ask | show | jobs
by davkan 21 days ago
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.
4 comments

You can have ads in a terminal / CLI, for example Ubuntu put an ad for their Ubuntu Pro service when you run sudo apt upgrade: https://linuxiac.com/ubuntu-once-again-angered-users-by-plac... . But the worst thing they can do is to show a plain text
I remember some ops back in the day putting ads into /etc/motd (https://en.wikipedia.org/wiki/Message_of_the_day) for free/cheap servers/services too, 2-3 decades ago.
We'll they could also send your terminal a 0x07. And let me introduce you to ASCII art:

https://en.wikipedia.org/wiki/ASCII_art

"Calude agents" cli lauched recently

It was very poor UX (from the demos i saw) -- and i tried it myself in Windows native command terminal and the rendering was horribly broken (windows is a second class OS for dev tools).

A light weight GUI with keyboard shortcuts that mimic CLI experience would have been far better without taking anything away from power users of the terminal.

You do get ads, many time you can see other tools being referred (open-source), but even open-source, those tools can become commercial later-on. Advertising a free tool is still advertising.
Well powershell is a pointless and optical nausea redesign of a shell. I would not call it design per se .. or maybe it was. ?
PowerShell was great, if a little verbose. PowerShell's real strength though isn't as an interactive shell, its as a scripting language. You pass objects back and forth, not text. Its basically an interactive API explorer.

> 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...