I think they will lose some already established studios that can afford to retool and reskill on another engine. But I think the vast vast majority of current unity developers are breathing a sigh of relief that they /dont/ need to reskill or retool on another engine.
Unity is still on shaky ground, but they have been since they went public. They need revenue, and their big ad revenue plan got ruined by dastardly apple protecting users’ privacy. Couple that with an upstart and promising engine following in Blenders footsteps. In five years, they might have lost every hand they had left to play. Irregardless of the missteps of the last week.
Every indie dev I’m following on YouTube has basically made a “My thoughts on the situation”-type videos where they talk about how they’ve “won against Unity” despite Unity basically doing a textbook of the “Door in the face” technique to pass changes that would’ve been unpopular before this whole mess.
As soon as I heard Unity was back pedaling, I thought “there’s part 2 of the plan”
1: release abusive payment scheme to see just how much push back they get. If push back is minimal or losses are acceptable, end here and enjoy the profit.
2: if push back is strong, implement the actual payment policy that is still a significant increase, but less significant than the one above. And wait until the controversy blows over, which it will.
Yes, lots of developers will leave, lots of developers will choose a different engine for their new games, but there are a ton that will decide that it isn’t feasible to switch engines and plenty that will just eat the added cost. The thing that remains to be seen is just how much damage Unity has done in terms of new projects choosing other engines over theirs.
Yeah, very few studios would retool an existing project. The real question is whether any of them will be picking unity for their next project. And will young people getting into game dev choose Unity over others? I don’t expect to see a sharp decrease in the number of Unity projects in the next year, but rather a slow descent, while Godot picks up steam and Unreal further cements itself as the professional’s tool.
All the tutorials and learning resources are hyper unity focused. That’s why so many game devs pick it up. That’s why they cornered the less than AAA industry. A young person will choose unity over the others for the same reason as they did last year. The endless resources to teach.
It’s likely almost all developers will pick unity for the next project too. All their knowledge is in unity, not Godot or unreal. We have this problem in other software industries too, some languages and frameworks are just better, but you can’t use them in your project because there are only five people in the industry that know how to use it well.
…which engine is the upstart and promising engine following in Blender’s footsteps? Do you mean what Unity was supposed to be until they ruined it, or did you forget to drop the name of the engine in question?
I think they will lose some already established studios that can afford to retool and reskill on another engine. But I think the vast vast majority of current unity developers are breathing a sigh of relief that they /dont/ need to reskill or retool on another engine.
Unity is still on shaky ground, but they have been since they went public. They need revenue, and their big ad revenue plan got ruined by dastardly apple protecting users’ privacy. Couple that with an upstart and promising engine following in Blenders footsteps. In five years, they might have lost every hand they had left to play. Irregardless of the missteps of the last week.
Every indie dev I’m following on YouTube has basically made a “My thoughts on the situation”-type videos where they talk about how they’ve “won against Unity” despite Unity basically doing a textbook of the “Door in the face” technique to pass changes that would’ve been unpopular before this whole mess.
As soon as I heard Unity was back pedaling, I thought “there’s part 2 of the plan”
1: release abusive payment scheme to see just how much push back they get. If push back is minimal or losses are acceptable, end here and enjoy the profit.
2: if push back is strong, implement the actual payment policy that is still a significant increase, but less significant than the one above. And wait until the controversy blows over, which it will.
Yes, lots of developers will leave, lots of developers will choose a different engine for their new games, but there are a ton that will decide that it isn’t feasible to switch engines and plenty that will just eat the added cost. The thing that remains to be seen is just how much damage Unity has done in terms of new projects choosing other engines over theirs.
Yeah, very few studios would retool an existing project. The real question is whether any of them will be picking unity for their next project. And will young people getting into game dev choose Unity over others? I don’t expect to see a sharp decrease in the number of Unity projects in the next year, but rather a slow descent, while Godot picks up steam and Unreal further cements itself as the professional’s tool.
All the tutorials and learning resources are hyper unity focused. That’s why so many game devs pick it up. That’s why they cornered the less than AAA industry. A young person will choose unity over the others for the same reason as they did last year. The endless resources to teach.
It’s likely almost all developers will pick unity for the next project too. All their knowledge is in unity, not Godot or unreal. We have this problem in other software industries too, some languages and frameworks are just better, but you can’t use them in your project because there are only five people in the industry that know how to use it well.
…which engine is the upstart and promising engine following in Blender’s footsteps? Do you mean what Unity was supposed to be until they ruined it, or did you forget to drop the name of the engine in question?
The engine following in Blender’s footsteps would most likely be Godot.
Unity was never open source and thus could never follow blender’s path. They’re almost certainly referring to Godot.