• demesisx@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Yes. Case in point: there are at least 10 Lemmy iOS apps. I’ll give you ten guesses on which ones are actually native Swift…

    There are a quite a few Android apps in progress too. How many are written in Kotlin?

    • alxhghs@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      1 year ago

      Voyager isn’t native and it’s good. I’m not totally sure what the hate is for React Native for apps like this. It’s an abstraction over Swift, it’s still Swift under the hood isn’t it?

      • demesisx@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        In my experience, Voyager is still pretty buggy too. For example, try editing a post then go to do anything else after the fact. I always have to restart the whole app when I go to edit a post I made. They have a ton more features than anyone else but there are still tons of bugs.

        react native is another layer and lags behind the dev of swift by at least a year. This is a huge problem for new api’s like SwiftUI, in my experience. Ps. Native is ALWAYS better than an approximation of native.

  • interolivary@beehaw.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    Everything is getting worse as companies are exclusively trying to squeeze more money out of everyone rather than build good products or services. Everything is done by fewer more overworked workers, with shittier components and features that are designed to extract money out of you rather than be useful or “good” (my favorite example is BMW’s subscription based seat warmers.)

    • Max-P@lemmy.max-p.me
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      That’s really what’s going on.

      Back in the days, people took the time it was necessary to write the software. And managers trusted the engineers to say when it’s ready or not.

      Nowadays, the software world is managers going “yes we know the database’s gonna blow up over the weekend without the query optimizations, but we want to build this new feature before the end of the week. We can deal with the database when it blows up over the weekend, that’s why you guys are on-call.”

      I did not make this up, I’ve actually heard this. This is why modern software is so fucked up, not because we can’t handle the complexity, because reliability and quality just isn’t prioritized at all anymore. Gotta dish out new features every day and you’re not allowed to work on fixing known critical bugs.

  • Digital Mark@lemmy.ml
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    1 year ago

    Yes. At least since late '90s, and certainly the last 2 decades.

    I blame the rise of frameworks, libraries, and IDEs. It’s easier for someone who knows nothing to throw some software together and ship it. In the good old days, all software had to be written by someone who knew what they were doing, often in difficult tools. You had to think ahead and write code correctly, because you couldn’t just ship patches every week.

    And as junior devs get replaced by AI, there won’t be any experience for any of them to learn how to do that.