If you have a host system where you want to expose APIs in an language-agnostic way, IDLs are the best way to do that.

You're also conflating the core WebAssembly work with the WASI work. There is some overlap in people, but WASI is developed separately.

The point of a component model is interoperability, so the more runtimes that support it the better.

"The woke mind virus" really? You used that non-ironically? This is not something a serious or sane person would say for real.

And that's just the Bluesky-like apps. Other non-microblog atproto apps use their own PDS, or store data on yours.

After reading the blog post I clicked the update button and the whole app was replaced, without much warning, with this conversation UI. It was even more jarring than I expected from the post because I figured there must be some messaging about what would happen and some way to just get to my files... but nope!

Then I downloaded the Antigravity IDE (as opposed to just Antigravity) and when I went to install it, it turns out I already had it installed!

So Google actually did an arguably ok thing with the apps - they split them into an IDE and an agent coordinator, and they kept the IDE installed so you can use it right after the update - but they didn't tell you what they were doing!!

If they had just said "Antigravity is now two apps. Which would you like to open?" everything would have been fine.

Why would it be good if Perplexity does it, but bad if Google does it? What are the principles at play here?

atproto apps also tend to separate the PDS form the app view, so you can easily use the same data with different front ends.

And, atproto's identity model is much better. Rather than being tied to a server like the data, it's DID-based and you can use it with multiple PDSes.

https://tangled.org/

With the atproto approach you don't have to worry about reserving usernames specifically for one forge or another - usernames are atproto handles, your Bluesky handle, custom domain, etc.

I'm not sure if Tangled itself is the right incarnation of these ideas, but a protocol for PRs, issues, forks, and activity is the right direction for the industry.

High oil prices only accelerate China's transition to renewables, and rewards them for all the investment they've made so far, both in national energy production and in selling panels and EVs to the world.

It hurts the US far more, especially with this admin's anti wind and solar policies.

If the car comes to a road covered with water, and that road is in the database, and the water level appears low compared to the historical level of the road in the DB, then the car could cross. if the road is not in the DB, then a different decision might be made.

This is similar to humans: you might make different decisions depending on whether you know the road well or not.