zamalek

> But I found that the 20-30 minute stops every 2h really improve how I feel after a day or two of driving.

I honestly started considering this a feature. I am a huge believer in "productive friction" - where some things are intentionally made annoying or hard so that humans avoid them - and this is a really good example.

> Like what does your polytree look like if you add a messaging pub/sub type system into it.

A message bus is often considered a clean way to deal with a cycle, and would exist outside the tree. I hear your point about the graph disappearing entirely if you use a message bus for everything, but this would probably either be for an exceptionally rare problem-space, or because of accidental complexity.

Message busses (implemented correctly) work because:

* If the recipient of the message is down the message will still get delivered when it comes back up. If we use REST calls for completion callbacks then the sender might have to do retries and whatnot over protracted periods.

* We can deal with poison messages. If a message is causing a crash or generally exceptional behavior (because of unintentional incompatible changes), we can mark it as poisoned and have a human look at it - instead of the whole system grinding to a halt as one service keeps trashing another.

REST/RPC should be for something that can provide an answer very quickly, or for starting work that will be signaled as complete in another way. Using a message bus for RPC is just as much of a smell as using RPC for eventing.

And, as always, it depends. The line may be somewhere completely different for you. But, and I have seen this multiple times, a directed cycle in a distributed system's architecture turns it into a distributed monolith: eventually you will reach a situation where everything needs to deploy at the same time. Many, many, engineers can talk about their lessons in this - and you are, as always, free to ignore people talking about the consequences of their mistakes.

I think that icons hold value so long as they have mostly distinct colors (which none of his examples do, so his point stands). At least for me, colors make vastly superior landmark than words do (once i know the interface).

I'm not sure what a typical ketamine dosage looks like, but I have discussed it with my psychiatrist as a fallback if TMS doesn't work out, and she said that ego death is one of the primary mechanisms (alongside reintegration therapy, spending a weekend tripping balls won't fix a thing - at least perpetually).

They mean to resell them in a different form: as part of their PaaS or SaaS. Per the article, OpenAI is just hoarding the wafers, not purchasing the final product.

Businesses/corporations are not people.

Thanks for the response, greatly appreciated!

Thanks for the AMA Peter!

Do you think there are risks involved with leaving (and hence returning to) the country on a Green Card?

Fundamentally I would be fine with this, the system exploits us so it's only fair to exploit it in return. Practically, however, my concern remains for people who need resources to support them.

> The students at America's elite universities are supposed to be the smartest, most promising young people in the country. And yet, shocking percentages of them are claiming academic accommodations designed for students with learning disabilities.

What the actual... Lack of journalistic integrity rears its head once again. Executive function and social challenges do not make a person "not smart."

Going back to the core of the problem, I feel that this does need to be controlled. It's one thing to disability signal online to gain clout, it's a completely different thing to drain resources from genuinely disabled folks. Disabilities need to come with diagnoses.

They are taking the gun out of USA's hand and unloading it, figuratively speaking. With this strategy they don't have the compete at full competency with the US, because everyone else will with cheaper models. If a cheaper model can do it, then why fork out for Opus?

Oof, you're completely right. I'm not sure where I got that wire crossed.

Exactly the caveat that they themselves disclose: some scenarios are too dynamic for static analysis.

It's sans-io at the language level, I like the concept.

So I did a bit of research into how this works in Zig under the hood, in terms of compilation.

First things first, Zig does compile async fns to a state machine: https://github.com/ziglang/zig/issues/23446

The compiler decides at compile time which color to compile the function as (potentially both). That's a neat idea, but... https://github.com/ziglang/zig/issues/23367

> It would be checked illegal behavior to make an indirect call through a pointer to a restricted function type when the value of that pointer is not in the set of possible callees that were analyzed during compilation.

That's... a pretty nasty trade-off. Object safety in Rust is really annoying for async, and this smells a lot like it. The main difference is that it's vaguely late-bound in a magical way; you might get an unexpected runtime error and - even worse - potentially not have the tools to force the compiler to add a fn to the set of callees.

I still think sans-io at the language level might be the future, but this isn't a complete solution. Maybe we should be simply compiling all fns to state machines (with the Rust polling implementation detail, a sans-io interface could be used to make such functions trivially sync - just do the syscall and return a completed future).

I coincidentally watched BasicallyHomeless's video on his 100+ day Linux experiment and he made a really good point: because everything on Linux can be done with the CLI, it also has a working natural language interface (Claude Code). He ran into several issues, such as sound (allegedly that's no surprise, but not my experience), and Claude fixed them all.

If it doesn't wipe your drive.

Still, interesting thought.

Right, it could be a lack of competition in the direction of the reactor. It's a giant petri dish for anything able to withstand radiation.

AI is currently summoning market activity during what should be a recession. Now this bubble isn't only filled with hot air, it's also filled with sewage.

Short-term gains are great, though!

"By your logic" is usually a canary for strawman, and it's needlessly combative on top of that. Best to step back and reconsider if you find yourself penning that.

The only thing I was saying was exactly what I said, within the context of XMPP, XML compresses really well - I was reinforcing the parent comment. How that relates to metrics in other contexts wasn't what I was talking about at all. I generally avoid XML nowadays, and so your argument with me isn't something I would dedicate thought to in the first place. I see no point in taking anything from this nonsense.

Where in my original argument did I suggest making the tags longer?

That's a strawman. I am not arguing that we make the tag names longer, I am arguing that there is little benefit to a more concise format.

If you are so bandwidth constrained that deflated XML won't do, then I doubt deflated JSON would be good enough either (and that exists anyway, Matrix).

Exactly? What's your point? Things have to be low entropy/contain a lot of redundancy in order to compress well.

Is that from its reference or ours? We'll observe it pass one light day one day after it actually does so.

XML compresses really well.

> Much credit to Valve for pushing that out as FOSS.

Cynical: Valve doesn't sell hardware or operating systems, they sell games. These devices are merely another storefront.

Optimistic: Valve has also figured out how to turn good will into a commodity. Blowing cash on Steam sales is a bit of a cultural centerpiece of the PC gaming community.

Gabe has proven that you can make stupid amounts of money by [mostly] doing right by the consumer. I'm not sure if there's more to the secret source, her sauce, because we've yet to see another CEO pull their head out of their arse far enough to see how lucrative this approach can be: consumerism is fickle, fanaticism is loyal.

For Linux-native games (there aren't many) it uses what I described, making the system look a lot like Ubuntu to the game. Proton is for Windows (PE/exe) binaries, not Linux (ELF).

Jonathan Blow is sharpshooting and being intentionally difficult in order to sound smart (he really needs to engage in that behavior less, he's smart enough as-is). Virtually nobody bothers with Linux-native binaries for games. Compile your game for Windows, test it on Linux+Proton, find that it probably works fine, it's not hard.

Steam works around this using a chroot (container-like) into an environment with controlled libs. That being said, I have never seen it work: I always end up enabling Proton.

There is the school of thought that Wine is merely the Linux gaming ABI, and I largely agree. Native Linux binaries "feels" better but doesn't bring much from a practical standpoint.

> Forgejo is more busy managing ideals, than creating software.

How many Elastic Searches will it take for people to realize that this is mandatory. Linux would not be where it is today were it not for some ideals wrangling.

My guess: possibly co-evolution. The article subsequently describes the genetics behind things becoming cute - which would have been completely benign to our ancestors (the core of your question). However, those of our ancestors who completed domestication of these animals (by random chance) would have enjoyed more protection from predators, rodents, etc. Those of our ancestors who attempted to domesticate things without the mutations might have had bad companions at best, and would have been predated at worst. This would have provided evolutionary pressure to adopt animals that were showing early signs of domestication. What we call "cute" is merely "likely to cooperate with us."

Or intentional and awesome.

This is normal for Microsoft. It's as though status is owned and controlled by either marketing or accounting, not engineering.