Although that doesn't work as well for laptops :( .
10,409 karma · joined March 3, 2015
Although that doesn't work as well for laptops :( .
And it should also be easy to make the keyboard controls customizable.
In other words, completely inaccessible to many people who would like a better life and are willing to work but lack opportunities in their native country.
Just because it was achievable for you doesn't mean it is achievable for everyone.
GP: python has baggage because it is old
P: that can be changed. Look at PHP
Me: PHP still has baggage, despite its evolution. You can't really get rid of it without making major breaking changes.
Mental "asylums" that were almost as bad (and sometimes worse) than prisons is clearly bad. But just leaving people to live on the streets or end up in actual prisons isn't strictly better.
I'm not saying we should bring back the asylums, at least the way they were, but there should be a better way to take care of people who aren't able to care for themselves.
Then why isn't it done more often? I suspect part of the reason is that most gui frameworks are not really designed for making dense economical interfaces.
> you probably don’t need a user interface on prod. You need a command line interface on prod that
I don't need one, but I often want one. Being able to run vim, htop, etc. on servers is quite useful. Also, it isn't just prod servers. It's also nice to run tuis on VMs and containers that don't have access to graphics.
> I’m not really building applications for other people to use. I’m building them for me. TUI affordances are an awfully big hit to take to get Linux users of programs I don’t even want to publish.
Ok. That's fine. But then why are you trying to convince other people not to make TUIs? If I make an app you find useful, wouldn't you prefer me to make a TUI you can run on your Mac to a linux-only GUI?
> A new version of the arrayref crate was published with a direct dependency on proc-macro1, which would execute a malicious build script.
> This compromised version was published on 2026-08-20 and removed approximately 86 minutes later, with no evidence of actual usage.
I don't know what more you want. Do you want the malicious version to continue to be available?
I think the sweet spot is having an ecosystem of "blessed" libraries that are reviewed for security and quality, but are versioned independently of the language, and maintained by subject matter experts.
They did that because a yanked package can still be used. And in this case there weren't any downloads, so it is unlikely the malicious package was actually used.