Yeah, I hope I'm wrong, but it feels a little bit like "planned project no longer has internal support, let's see if we can make it open-source to garner goodwill and recoup some of our investment." Which isn't the worst thing that can happen.
Being accessible to the intended users always matters. If you think it doesn't, that probably means it's currently accessible to those users (or that those who are it is inaccessible to have filtered themselves out, and are no longer users).
For example - in your debug UI, colorblind-friendly colors don't matter, until you hire your twelfth member of the team, who struggles to tell red and green apart.
Additionally the developer of this library is active in the indie game scene, so "twelfth member of the team" is hardly a relevant issue.
I find it so unfortunate how many of the criticisms raised here are mooted by simply glancing at the README.
There's an interesting conversation that could be had about the needs and limitations for debug UIs, and how to balance that with minimal code. (E.G. Would feeding this library's text-and-rectangles output into an accessible renderer be enough?) But blanket rejections and reflexive judgement aren't helpful.
Another stat I've heard, but can't cite at the moment, is that only 7% of Americans use ChatGPT daily - I think it is likely a bit older than 2025, though, so I wouldn't be surprised if it's closer to 10 or 20% now.
Everybody lives in their own bubble, and it can be easy to believe that you're in-touch with the public-at-large. That's why you gotta fact-check this stuff.
That includes a 58% majority of adults under 30.
has roughly doubled since summer 2023.
There are old people who might never use it. That said, my 70 year old parents use it sometimes.
My bubble is working adults, which is likely more represented by the 58% under 30 figure. However, this was a year ago. I'm guessing adoption has accelerated even more in a year. It wouldn't surprise me if it's 50% overall by now and 70-80% of adults under 30.
So these facts don't actually dispel my intuition.
With the one caveat that it does not (yet) support copy/paste buffers or copying from the scroll back buffer. It’s also adamant that you use a mouse to select/copy - anything more complex and you need to pipe everything into neovim (or whatever text editor you use) and do your work there. I love zellij - it feels like the future - but hard to give up keyboard based select/copy and pulling from my scrollback.
The thing you can do in the terminal that you can't do in a GUI, is glue together over 50 years of useful tools, no matter where you got them from or if the authors have ever heard of each other.
If your workflow fits entirely within a single app's GUI, then yeah, the terminal version of that app is not going to be as useful. But if that app doesn't exist yet, you can put together an 80% version of it for 20% of the work.
Historically, it's also a lot more resistant to rot. Brian Kernighan isn't going to start charging a subscription fee for AWK - and if he did, there are many forks and similar tools.
And, addressing a specific point - why would I want to view a code diff in a terminal? Sure, 'diff old.txt new.txt' is probably less useful than popping it open in a nice GUI with highlighting. But "diff old.txt new.txt | grep '^+'" will only show me added lines, or "| less" and type "/foobar" to jump to all mentions of foobar.
And this is like, the least you can do - the stuff you learn in the second class of "Using the Terminal 101". You can easily use this with git, as a building block to make a quick script to graph the number of changes over time in your repo. Yes, there's probably a GUI somewhere in your workflow that can show this (maybe you click around in Github to find it). But, maybe you also want to just filter that to changes in a specific module in the codebase, or an author, or quantify what module changed the most each month. If you've learnt the building blocks, the scriptability of the terminal lets you put that together quickly.
I've also seen this. It'll run 'strings' against the binary and then convince itself that the Makefile isn't working right, and there's some imaginary sandbox preventing the code from compiling properly. So it will compile it by hand, and never run strings against the new binary, and proceed happily.
If a government does not respond to the wishes of its people, violence is an inevitability. It is in the best interest of the state to be accommodating enough to placate the citizens.
Only if what those people want is something I agree with otherwise I think the state holds the monopoly on violence and we need to mobilize it against the wrong thinker.
reply