justbeast
1. Why no public forum or (heavens forfend) a standards body community group, for the spec?
2. For the data model, why not use the excellent ActivityStreams2? The actual data model that contains the posts etc (https://atproto.com/lexicons/bsky-app) is a serious step backwards from the event-log architecture of AS2.
3. Why reinvent gRPC/JSON-RPC? Seriously, of /all/ the things to reinvent, why RPC?
4. I wonder what the team will do for authentication and authorization? Will they go the ACL route? (In which case, are they going to include Solid-style client identity, in the ACLs?) Will they go the capabilities route? (UCANs / zCaps). This is the genuine hard part.
You're probably referring to the fact that there's an option to deploy the hello world PLUS the VM it runs on, in a single package. That's like saying "You can't give a Java hello world to someone under 50 MB". Yes, technically true, the couple of lines of Hello World source code don't work without a 50 MB JRE. But you're being disingenuous.
The Pharo community needs to knock it off, with that kind of arguments. (And I say that, being a part of that community).
Pharo is NOT too cool and too well designed for the mainstream. :( It /is/ cool, and has a lot of good work put into it. But it still needs a lot more work (especially in documentation and tutorials) before it's really useable by people without extensive Smalltalk experience. So, everybody shut up and roll up your sleeves and work. And be humble.
(If you think about it, Java apps like Eclipse and so on, are also a tiny bit strange and non-native. They've come a long way towards blending in with native apps, over the years. But they still feel a bit off, from a native icon and windowing perspective.)