• monk@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 year ago

    This is nowhere near reality.

    Even if you could just “translate” code from one language to another, that ignores asset pipelines, asset store libraries, and all the build pipelines that allow you to ship cross-platform.

    You also need to now train your entire dev team on a new tech stack.

    Switching engines is an enormous effort

    • CookieJarObserver
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      3
      ·
      1 year ago

      If you can do it with databases you can do it with most other code. Shure it won’t be problem free but way better than bankruptcy. And users will understand that it might be buggy for some time if you explain it to them.

      And yes you have to retrain your staff but its their job.

      And of course there will be library issues but there will be someone making new libraries.

        • CookieJarObserver
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          3
          ·
          1 year ago

          Im not exactly that sorry for most tbh, there have been many other languages and engines that aren’t unity, they have been doing shit for years now, people could have switched already. This now is just tip of the iceberg basically.

          Im only sorry about small studios and indie devs that worked on something for years and now that.

          • sugar_in_your_tea
            link
            fedilink
            English
            arrow-up
            5
            ·
            1 year ago

            But Unity mostly targets smaller devs. The big AAA studios don’t generally use Unity, they usually use Unreal or something home grown.

            It’s mostly AA and indie studios that use Unity.