323
Google lays off staff from Flutter, Dart and Python teams weeks before its developer conference | TechCrunch (techcrunch.com)
submitted 2 years ago by to c/programming@programming.dev
92 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 20 points 2 years ago (14 children)

I'm mostly just biased because I do native mobile development but flutter has always seemed like a false economy to me. You're trying to build cross platform but it'll take more than 2x as long as building each platform to get the same quality of experience. So either you have a shittier experience or you take even longer than true native dev.

But I'm obviously very biased here.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 14 child comments
    •
  • [–] 14 points 2 years ago (10 children)

    I've used it before and it's got it's pros and cons. Ultimately the big thing is not all apps need to be the "killer app". Some apps are pretty simple, so a one size fits all can be nice. It's definitely not the same as developing natively, but for small teams/apps it's not too bad.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 4 points 2 years ago

    If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago

    If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago

    If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago

    If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago (4 children)

    If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 2 years ago* (last edited 2 years ago) (3 children)

    It looks like your reply got submitted multiple times.

    I agree with you now about preference for web apps, but that was not the case when Google started pushing Flutter.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 4 points 2 years ago

    Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.

    I think trying to go cheap on native apps was always kind of a fool's errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 2 years ago

    Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.

    I think trying to go cheap on native apps was always kind of a fool's errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 2 years ago

    Looks like my Lemmy-client of choice did some retrying when I had poor connection, sorry about that.

    I think trying to go cheap on native apps was always kind of a fool's errand, tbh. Cordova, Xamarin, React Native and so on - all pretty sub-par solutions leading to poor experience without actually materializing the desired savings.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 2 years ago

    If you're prioritizing cost, you should probably already be building a web application imo. There's very few cases where I would recommend cheaping out and building a native app, it's just kind of unsound.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 2 years ago (2 children)

    Flutter can be socialized for mobile OR desktop OR web. Having all three in a codebase requires lots of code and alternative layouts to properly handle each platform. It's not a "one size fits all" solution, actually to the absolute contrary it's a solution that you have to tailor to the UI you want to build.

    I'm making desktop apps with Flutter (it's awesome) and my apps can't ever possibly hope to run on mobile. I'd have to remake most of the damn thing in order to make layouts for mobile.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    Right but instead of a toy language there's Kotlin which is already multiplatform.

    I just struggle to see why another language needed to be invented to do this.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •