this post was submitted on 15 Sep 2023
2124 points (99.0% liked)
Technology
59398 readers
2555 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm pretty sure there are open source alternatives to this?
Anybody care to shine some light on which projects would be comparable, and how they stack up against unity?
There is, unreal besides being a product has its source available and Godot focus on the same niche most of unity games were. But the problem never was the lack of replacement, the problem is, a game with years of development on unity whould not easily switch to any alternative, they have assets from unity store, scripts made for unity, UIs using unity specific stuffs, even network protocols could be bounded with unity. Change this is an herculean task and most of the games are in barely maintenance mode, imagine a full rework. So these games should be pulled of the market and thrown in the garbage to avoid new installations.
Coders cost money and coding takes time.
This is true for most of software out there, but most of the game industry operates with a small margin, and when you look to games individually, most of the games that are still selling (think about GoG games) are not worth any developer time
The most valuable thing is an experienced team who thoroughly understand both the specifications and the implementation as well as the reasoning behind both. Written specifications are great as onboarding and reference material but there will always be gaps between the specifications and the code. ("The map is not the territory.") Even with solid specifications you can't just turn over maintenance of a codebase to a new team and expect them to immediately be productive with it.