1 Obit
Seems to work real well here, On choosing React Native, Paul Frazee explains: “We knew we wanted to hit all of the major platforms right from the start, and given our Typescript focus, there was only one viable way to do that: React Native.  newsletter.pragmaticengineer.com/p/bluesky-en...
Inside Bluesky’s Engineering Culture
A deep dive into how a fully remote, open source-first, tech company is building a challenger social media platform. What can small teams learn from Bluesky about punching above your weight?
newsletter.pragmaticengineer.com
 1 2
Bossett
I don't think anyone would argue that RN isn't the fastest way to land a multi-platform app on a really tight schedule. But as they get bigger (and want to get 'good') there's always the slow, inexorable move toward mostly native controls
2 6
Samuel
@samuel.fm
I wish it were less boilerplate-y, but hopefully we'll get there eventually
2 3
Biscuit
no joke with SPM and like, 50 targets my work project takes 5-6 minutes to OPEN from a fresh git checkout (also every branch switch is another 3-4 minutes if I’m lucky and it doesn’t crash)
1 1
Biscuit
With Tuist caching (uses frameworks) the project actually opens in a normal amount of time now. I really wouldn’t wish the SPM Xcode integration on my worst enemy. It’s also wild that SPM on Windows/Linux has been actually running pretty well, which is honestly just another slap in the face lol
2
Bossett
yeah though that kinda matches the rest of the web - I don't think there are a lot of multi-purpose frameworks that do it well
2