I'm curious if this also means they'll be able to demand more aggressively for redacted/omitted Epstein-related documents too.

My hopes are about as low as they can get with this, but I hope I'm pleasantly surprised (assuming anything gets released).

JavaScript takes yet another approach. It doesn't have an equivalent of the Character.isWhitespace() method, but we can use the \s character class in a regular expression

\s might be the most obvious whitespace test, but the expectations are a bit more ambiguous when it comes to regex. Every regex runtime is different, so without looking it up, you're going to end up with behavior you might not expect.

Instead, if you want to match Unicode whitespace, you should use \p{White_Space} in Unicode-aware mode (u or v flag).

I haven't looked through any other runtimes, but something tells me the inconsistencies won't stop at these three.

According to the docs, Rust's char::is_whitespace checks if the value has the White_Space property, and regex does the same in Unicode mode (which is the default).

I liked Zed a bit, but I ran into some bugs that made me switch back to my previous editor. I think I'll give it more of a shot in the future once it's a bit more mature. Otherwise, I enjoyed how responsive it felt, and having a single toggle to completely turn off AI features was nice.

For Kate, I view it as an alternative to Notepad++. It's quite a bit more powerful than N++, but to me feels like it fits in around the same place you described between simple text editor and advanced coding IDE. It's a great default for people who tend to modify a lot of config files.

If they're all generals who happen to be attorneys, then I guess.

States employ attorneys general, though.

Should be "Attorneys General", not "Attorney Generals". There are multiple attorneys, not generals :P

The LLM when you tell it to rewrite it in Rust.

This seems like a problem that can be approached entirely in embedding space. Find embeddings for words that you want to avoid, then filter your dictionary to remove anything too close to those.

No need to go through full text gen or anything, though if you want to go that route, a classifier like Jev (or OpenJev/etc) would be best.

the classic language models before LLMs existed

Which models are you referring to here? Earlier versions of GPT (like GPT-2)?

There are small LLMs like Phi 4 Mini that you could look at. Those were part of the "small language model" craze (SLMs).

If you want meaningful commit messages though, nothing beats handwritten messages. Commit frequently and the messages should be short and easy to come up with.

We've been together for more than 10 years and the single most important thing is communication.

As others have emphasized, focus on improving how you communicate with each other. Always assume good faith from your partner, and in turn, always speak in good faith. If you're feeling emotional and you're worried you might say something you shouldn't, then just say you need a minute, and take that time to settle down and figure out how to communicate what it is you want to say. Be patient with each other, and if she says something that makes you upset, understand that she made a mistake with communication and didn't intend to attack you.

If this doesn't work and there's some other underlying issue, then it'd be good to share what that issue is with each other. For this, you might want to consider a mediator of some sort.

"Guns cause a lot of shootings, so let's ban guns"

~ any reasonable country on the planet

Breaking news: software written from the ground up in 2026 opens faster than software that's been developed, extended, bloated, and maintained for over two decades.

Steam releasing a performance patch so soon after makes it even funnier.