One of the big winners of the Unity debacle is the free and open source Godot Engine, which has seen its funding soar to a much more impressive level as Unity basically gave them free advertising.
Honestly, one thing I’m seeing frequently in comments about this is a bit frustrating. That is, people saying that they vow never to buy any games in Unity ever again on principle.
Vendor lock-in is a real thing, and part of the reason they actually tried this play. Many of these developers likely want to switch to a different engine, but don’t have the time or resources to do so. Honestly of all people hit by this situation, they probably need the help most.
Incidentally, if you are one of those devs reading this and feel you don’t know anything other than Unity, go learn something else. Diversify your portfolio. Learning a new engine isn’t hard if you know the fundamentals.
Unity dev here. Will switch on our next game, but don’t have the choice for the current game that we’ve already invested 4 years into.
Also, bevy looks nice code-wise but it desparately needs a proper editor and GUI to make it artist friendly
There is the blender_bevy_toolkit which aims to serve Blender as an editor for Bevy. I haven’t tried it myself, but definitely will when I get to more artistic phases of my projects.
That looks like an interesting project, but it seems it hasn’t been updated in over a year, and is only compatible with bevy 0.6. The current version is 0.11 or something. I’ve had my ass kicked before by relying on projects that didn’t have a lot of support available, so I would stay out of this one.
That’s a valid point. Games released in the next 2-3 years should be probably be given a pass. My admittedly layman’s perspective is that any indie game deep enough into development that switching engines isn’t feasible most likely wouldn’t require another 4 years to ship.
Honestly, one thing I’m seeing frequently in comments about this is a bit frustrating. That is, people saying that they vow never to buy any games in Unity ever again on principle.
Vendor lock-in is a real thing, and part of the reason they actually tried this play. Many of these developers likely want to switch to a different engine, but don’t have the time or resources to do so. Honestly of all people hit by this situation, they probably need the help most.
Incidentally, if you are one of those devs reading this and feel you don’t know anything other than Unity, go learn something else. Diversify your portfolio. Learning a new engine isn’t hard if you know the fundamentals.
Also, can we get more love for Bevy. :P
Unity dev here. Will switch on our next game, but don’t have the choice for the current game that we’ve already invested 4 years into.
Also, bevy looks nice code-wise but it desparately needs a proper editor and GUI to make it artist friendly
There is the blender_bevy_toolkit which aims to serve Blender as an editor for Bevy. I haven’t tried it myself, but definitely will when I get to more artistic phases of my projects.
That looks like an interesting project, but it seems it hasn’t been updated in over a year, and is only compatible with bevy 0.6. The current version is 0.11 or something. I’ve had my ass kicked before by relying on projects that didn’t have a lot of support available, so I would stay out of this one.
I’m learning Rust right now, Bevy is totally next on the menu for me after I learned webdev.
That’s a valid point. Games released in the next 2-3 years should be probably be given a pass. My admittedly layman’s perspective is that any indie game deep enough into development that switching engines isn’t feasible most likely wouldn’t require another 4 years to ship.