I have an app that I released a couple years ago (plus another legacy app that I maintain for one of my company’s clients). My game has a long-ish title, but it was fine until some asshat at Google decides that 33 characters is too long. On top of that, every time I’m forced to update the target SDK, I need to spend several hours figuring out a bunch of new build errors. This is not how I wanted to spend my vacation time.

  • @[email protected]
    link
    fedilink
    English
    31 year ago

    Customers won’t pay maintenence. And code can’t be maintained forever that isn’t bringing in money. This is just the harsh reality.

    • @ExtraMedicatedOP
      link
      English
      21 year ago

      Plus the code I wrote myself isn’t usually what I have a problem whith changing. It’s the various included packages and dependencies that in some cases may no longer be supported, and may not even have a similar replacement. I usually deal with this when updating an old web app that uses the Laravel framework. Some Composer packages are locked in to older versions. And when the client has a 20 hr/month budget, these types of updates can be tough to fit in the schedule.

      • @[email protected]
        link
        fedilink
        English
        11 year ago

        Yeah we have some tooling that isn’t up to API 33 yet… one app has been abandoned because of that - it’ll be ios only for a while until there’s resources for a rewrite.