3 ms·
I sort of find it poetic. If you decide to build on a commercial platform like Unity's you're subject to the whims of Unity Technologies. It sucks, but game en
by andrewmcwatters 8y ago
I sort of find it poetic. If you decide to build on a commercial platform like Unity's you're subject to the whims of Unity Technologies.
It sucks, but game engines are by far one of the riskiest investments I've seen across technical subfields.
You have all of this engine-specific knowledge, and all of a sudden moving engines is near impossible. Tons of common things across major game engines, but in practice it's not so easy to move here or there.
It's not like a database, where maybe some data type quirks are a bit different, and hopefully you can just change the underlying implementation behind your DB abstraction. Change a connector or something of the sort.
With game engines, you'd have to reexport models from sources, textures might be treated a bit differently, map formats might have to be scrapped all together or converted using some at-the-moment nonexistent scene converter. There's a lot involved.
- thexa4 8y agoIsn't that always the case with frameworks vs libraries? A database can be seen as a library but you build your entire game on top of the engine which makes it like a framework.