This was raised in bug trackers, and this Kitty's maintainer willfully decided to be an asshole about it. Briefly considered changing, but then didn't out some fit of pique.

Atto's default key bindings match Emacs, which is about as standard as you get for non-modal editing keys in older Unix traditions.

I would assert Wordstar style are equally as old.

But are mostly forgotten while emacs keybindings are still popular and found in all kinds of places you wouldn't expect, like MacOS textboxes.

Not when using joe, for example.

jmacs.

jmacs is a rather recent mode.

https://joe-editor.sourceforge.io/history.html

Hence the qualification in Unix traditions.

WordStar was for CP/M and MS-DOS, which was very much doing its own thing. Atto is for Unix.

> match Emacs

For many, it is indeed about what they call "muscle memory". Almost impossible to change after so many years. And therefore I hope everyone would provide keybinding alternatives generally (shouldn't be that hard).

and isn't at all beginner friendly

Emacs is probably older than me why should we care about what they used in 80s?

I see you’re using Latin characters...

It's 2026, why would anyone want to use an Intel architecture?

Or ARM? It's from the 1980s! So old!

Calculus is older than you. Does that mean you won't use calculus?

Depends, do you care about UNIX and C, as products from 1970's?

UNIX doesn't exist anymore, and C has lot of negative points (easy to create buffer overflows, integer overflows, use-after-free, and other vulnerabilities).

Then use Redox OS, or convince Torvalds to merge Asterinas' memory handling code into Linux.

It surely does, Linux distros, BSDs, Aix, z/UNIX are all alive and well.

Despite all those flaws, people keep writing new software in C every day, go figure.

The agent requirement is a symptom of a deeper potential issue: not using the system's ssh. Providing built-in as a fast-path option is fine, but ~/.ssh/config can do a lot of useful things, and providing an easy option to say "just use real ssh" lets people have their config just work.

Specifying identify files for specific hosts, using bastion hosts (ProxyJump), etc. For example, my laptop SSH config detects when I'm not on my university network or VPN and adds a ProxyJump through the department bastion host, but connects directly when I'm on the network. Configurations like that break when software makes too many assumptions about how ssh is configured.

oh wow, how can your ssh config change based on the network you're using?

ssh_config allows several ways to execute arbitrary shell commands, such as "Match exec" and "ProxyCommand". Specify a program that can detect networks and choose different connections. Then the config file itself wouldn't change.

If you want (4) and don't care about a web interface for managing repos, but do want Git-LFS, Soft Serve (https://github.com/charmbracelet/soft-serve/) works pretty well. I used it for self-hosted stuff until I started needing other features Forgejo offers.

Or just push to an S3 bucket with `gitsocial mirror <s3>`

Kraid is the shader compiler for Panfrost, the Mesa driver for Arm Mali GPUs: https://docs.mesa3d.org/drivers/panfrost.html

So Panfrost is an OpenGL ES implementation for Mali-type GPUs then? Thank you for that. Still confused about the role of a compiler here because I'm uninformed. So Kraid is a GLSL compiler that is specific to those GPUs? Neat.

Yes. In little-endian, the difference between short and long at a specific address is how many bytes you read from that address. In big-endian, to cast a long to a short, you have to jump forward 6 bytes to get to the 2 least-significant bytes.

Wow, I've been living life assuming that little endian was just the VHS of byte orders with no redeeming qualities whatsoever until today. This actually makes sense, thank you!

Mamba is fast, and Pixi is also fast + sands a lot of the rough edges off the Conda experience (with project/environment binding and native lock files).

Not perfect, but pretty good when uv isn't enough for a project or deployment scenario.

And readability. data.table is very capable, but the incantations to use it are far less obvious (both for reading and writing) than dplyr.

But you can have the best of both worlds with https://dtplyr.tidyverse.org/, using data.table's performance improvements with dplyr syntax.

The article is about a mechanism for the OS to validate focus requests. The application with the link requests a focus token, and passes it to the browser along with the open-link request, and the browser can then request focus.

It isn't perfect, because there's no way to know that the browser isn't using the token to request focus for something else, but maintaining and validating chain of custody for focus across applications is exactly the problem it looks like they are working on solving.

That was exactly the example given in the article, but somehow this isn't what I expected would happen if I click a link in say, my email client or chat program.

I imagined it more like: User clicks link in email program. Email program tells OS: "Here, open https://..." -- OS checks URL scheme registry and selects Firefox, OS brings Firefox to the front and throws the URL at it and says "Open this."

I guess perhaps my naïve way could falls down if the OS accepts URLs from apps that aren't in the foreground, so a random background process could activate any app it wants to steal focus.

Yep. With the solution discussed, as I understand it, the e-mail program just needs to be modified to request a focus token and send it along with the URL request to the browser or the OS browser dispatch service to keep the expected behavior.

This could be abstracted by libraries (e.g. a method in Qt to open a URL in the system browser automatically gets the token) so each application doesn't need to be updated separately, or possibly even OS services.

Describing this as a limit on "CS programs" is a common, but erroneous, understanding of the proposal limit.

This specific solicitation — CISE Core Programs — has a 2-proposal-per-year limit. However, that only applies to this solicitation, and only counts proposals submitted to this solicitation. CISE Core Programs is an important CS funding mechanism, but there are quite a few other funding vehicles within CISE (Robust Intelligence, RETTL, SATC, and many more, including CAREER). Each has its own limits, that generally don't count or count against the Core Programs limit.