So I've got a bsky acct, and y'all, their web app is everything I warn about. It's React (because they have capitulated to the App Store game via Expo and "need" React Native), but it's also web-as-afterthought-flavoured React. Which is going just about as well as you might expect for folks who don't own the latest devices:
Mastodon's React mistakes pale in comparison and, ofc, @nolan's pinafore.social blows them both out of the water. Failure this bad is a choice.
@nolan This is a choice, specifically, about class and inclusion. For the benefit of the enfranchised and the comfortable, Bluesky is making their service less accessible to folks who are less wealthy. The pushback I get when pointing out how utterly incompetent their web 2.4MB critical path JS bundle (and fonts served without compression) are is invariably a sort of reflexive defense about how they're "trying so hard" and "just a small team" (rinse, repeat).
And it's both true and telling.
@slightlyoff The "small team" defense is odd because I just saw this post by @danilo which points out how well-resourced Bluesky's team is compared to Mastodon's: https://hachyderm.io/@danilo/113488806508305304
And yet you said the official Mastodon web app isn't as bad, and of course you pointed out @nolan's work on Pinafore. But then, Nolan eventually quit working on Pinafore, which was after all a side project. Surely Bluesky's fully-funded, full-time team should have produced something as good as Pinafore.
@matt @slightlyoff @nolan I've long noticed a pattern with "well-resourced pseudo-underdogs" where the claimed team size and capabilities seem to change overnight depending on which size better suits the argument they're trying to make or the image they're trying to project.
Big team when they're trying to claim they are more competent than community initiatives, then suddenly it's a small team when accountability comes looking. npm (at least pre-acquisition) constantly pulled the same trick, for example.
