7,223 karma · joined November 6, 2011
Obviously the investment expense has been extremely high, which is what the replies are quibbling about.
The public side is extremely important for agents though. Agents need up to date public information to do their job. Every other service is going closed. Public information and activity should be a commons.
The main difference was atproto wanted to tackle scale, so we went with a servers & aggregation model. Radicle is going for device-to-device networking as a primary goal.
The simple answer is that atproto works like the web & search engines, where the apps aggregate from the distributed accounts. So the proper analogy here would be like yahoo going down in 1999.
This situation is being treated like a bad business decision. It’s not. It’s a new set of laws. It’s bigger than just Apple.
I recall the property passing model being a nasty abstraction breaker. HTML attributes are all strings, so if you wanted to pass objects or functions to children you had to do that via “props” instead of “attributes.”
I also recall the tag names of web components being a pain. Always need a dash, always need to be registered.
None of these problems broke it; they just made it irritating by comparison. There wasn’t really much upside either. No real performance gain or superior feature, and you got fewer features and a smaller ecosystem.