News for hackers. Stuff that matters.
Re:Why you should NOT use NativeScript by JamesSwift on Monday April 12, 2021 @02:27PM (#26783148)
There is absolutely no way flutter unseats java/kotlin unless it abandons dart and adopts kotlin as its language. Its much more likely that flutter gets absorbed in some way by the android ecosystem.
Re:Why you should NOT use NativeScript by chairhairair on Monday April 12, 2021 @02:51PM (#26783490)
I don't see how it would make any sense whatsoever for Flutter to be "absorbed" by Android, it is entirely independent.

Also, I'd be curious to hear what major advantages Kotlin would have for Flutter. The Flutter team has commented heavily on Dart's useful properties for Flutter's goals (small comment here, there are well written full articles as well: flutter.dev/docs/resources/faq#why-did-flutter-choose-to-use-dart).

The internal investment in Flutter is well beyond the average tech project at Google. I don't expect it to be abandoned any time soon.

Re:Why you should NOT use NativeScript by robocat on Monday April 12, 2021 @04:25PM (#26784696)
From the FAQ “the LICENSE file is 54.3 KB (compressed)” - that is pretty large amount of uncompressed text! I couldn’t find the full licence file (presumably containing all the licences of library dependencies).
Re:Why you should NOT use NativeScript by pjmlp on Monday April 12, 2021 @02:50PM (#26783470)
Jetpack Compose was definitely a counter attack from Android team, with Ads being a big Flutter sponsor and the only reason Dart did not die when Chrome withdraw their support.

So if Ads, Pay and Search keep their support, Dart and Flutter are here to stay.

Re:Why you should NOT use NativeScript by schmorptron on Monday April 12, 2021 @04:11PM (#26784539)
Just to understand this correctly, are you talking about internal debates at google? Like the different teams embracing different technologies for building apps?
Re:Why you should NOT use NativeScript by eddiegroves on Monday April 12, 2021 @09:57PM (#26787379)
Yes, Flutter is “sponsored” by other money making teams inside Google. It is why resources have been spent on Flutter for Web, which no one asked for - the Ads team essentially bought the feature for their usage. This was also how React Native got its start in Facebook.

So my read of Flutter is it’s a way for talent to “ship and get promoted” inside Google or to support other Google product teams. Everyone else is a secondary priority.

Re:Why you should NOT use NativeScript by dragonwriter on Monday April 12, 2021 @10:03PM (#26787414)
> It is why resources have been spent on Flutter for Web, which no one asked for - the Ads team essentially bought the feature for their usage.

“the Ads team at Google” is a very strange thing to treat as equivalent to “no one”.

Re:Why you should NOT use NativeScript by karmakaze on Monday April 12, 2021 @07:30PM (#26786436)
Flutter does away with all the idiosyncrasies of the many Android APIs that differences between Dart and Kotlin seem relatively superficial.
Re:Why you should NOT use NativeScript by mkrishnan on Monday April 12, 2021 @04:29PM (#26784746)
+1 to the dart part.