3 ms·
I agree, it's a beautifully expressive and safe language. Being tied so closely to iOS, thus limiting its impact for eg backend work, really is a pity. I know y
by chubs 4y ago
I agree, it's a beautifully expressive and safe language. Being tied so closely to iOS, thus limiting its impact for eg backend work, really is a pity. I know you technically can use it for backend work but the ecosystem just isn't there, I think people just consider it ios-only unfortunately. To workaround the small ecosystem, you can bridge to existing C libraries but the impedance mismatch makes it very difficult (eg UnsafeMutableBufferPointer<T>).
I do worry about its future however: dual-native mobile apps are less and less popular with product owners with every passing year, the market seems to be moving to flutter. Which is a pity! It's such a great language.
- newZWhoDis 4y agoJust wait, Google will abandon flutter and everyone who built their apps on top of it will be hosed.
- chubs 4y agoHonestly that's a very real concern. From what I hear, the Android team does not speak glowingly of the Flutter team at IO. Also there appears to be a power struggle between the Flutter and Jetpack Compose teams to become the next 'official' way of developing Android apps, in parallel to Apple bringing out SwiftUI. Time will tell. Given what we've all been reading lately about Google's LPA cycle (launch, get promoted, abandon) it seems likely that flutter will end up like React Native: kinda usable, but never really polished enough, it seems they just stopped most work on it before the finish line.