I doubt that, devs can switch Code, Shure some game devs need to remake already written code but i think there will be someone making a code translator right now.
One of the biggest appeals of modern gane engines is that you barely need any code but that also means everything is centered entirely around the game engine, I doubt there is any way to transition that, it probaly means devs have to start from scratch and reimplement the mechanics.
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.
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.
That’s a normal thing to happen after you decide to bankrupt your business partners. (But do we know it already? I thought Reddit wasn’t public.)
But Unity here decided to bankrupt their customers, so I do expect their numbers to change much more quickly.
They will just bankrupt themselves.
Hum, that “just” is really undeserved here. I’m sure they will drag many of their customers with them.
I doubt that, devs can switch Code, Shure some game devs need to remake already written code but i think there will be someone making a code translator right now.
One of the biggest appeals of modern gane engines is that you barely need any code but that also means everything is centered entirely around the game engine, I doubt there is any way to transition that, it probaly means devs have to start from scratch and reimplement the mechanics.
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
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.
Right, just make a database and then draw the rest of the fucking owl.