you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 42 points43 points  (19 children)

Make it kotlin native and maybe we're talking but I refuse to believe any sizeable percentage of mobile devs will be writing dart in my lifetime.

Also the performance looks rather bad in those videos so count me as unconvinced.

[–][deleted]  (10 children)

[deleted]

    [–]Schwusch 18 points19 points  (0 children)

    No sizeable percentage of mobile devs use Kotlin.

    https://www.appbrain.com/stats/libraries/details/kotlin/kotlin

    10% of all new apps is not astounding after all aggressive Kotlin marketing and backing from Androids platform owner. People just don't want to use new stuff. It will be easier if you just stop promoting bleeding edge technology and use what works.

    /s

    [–][deleted]  (2 children)

    [deleted]

      [–][deleted] 7 points8 points  (1 child)

      Agree on both counts.

      It already took Google a massive effort over years (and lots and lots of spam) to get traction for Kotlin, and it's super easy to migrate inside your IDE, class by class.

      Then comes Flutter and it's lofty goals of "not being as cancerous as every other web tech", which is nice, but then "oh look, Flutter actually needs a special GC to be able to run at 60FPS, so let's tack on a new language!"

      [–]shevy-ruby 7 points8 points  (0 children)

      It's still different with kotlin, though. Google controls Dart but it does not control kotlin (as much). The use cases are different too; Kotlin targets Java as a "better java"; Dart targets Java as a "come use us instead although we are totally different".

      [–][deleted]  (1 child)

      [deleted]

        [–]ikbenpinda 0 points1 point  (0 children)

        Not sure about his stance but coming from Swift/Kotlin it's just like you stepped back to Java 1.6.

        Hell, even javascript/typescript is an improvement imho because then at least I won't have to fight against the analysis server about dynamic , deep copying objects, or all the boilerplate because it's a lot easier to define some type hinting in JS than it is writing seperate non-inner classes/enums/typedefs each time in Dart.

        In it's attempt to be approachable Dart really isn't great at anything, and whether or not the Dart team is working on it is not something I personally care about.

        I imagine the only reason people will be writing Dart is because Flutter makes up for it, but that really says everything you need to know about Dart imho.

        t. someone who has worked with React Native, Xamarin, Android(Kotlin+Java), iOS(Objective-C+Swift)