the “just don’t do it” argument ignores the problem. it’s like replying “just don’t buy Apple products” to people complaining about right to repair. the key part is that regular people won’t know beforehand until they need to notice. by that point, it’s profitable enough to show other companies like Samsung and Motorolla that restrictions are profitable, so jumping around brands will also never work when the intention is to have your phone for a long time.
back in the context of game dev, add that to the part where not only people don’t anticipate the retroactive changes of a license they have to rely on when choosing an engine, but there’s the added weight of having to learn an entirely new library and oftentimes even an entire new programming language, so you have to commit to it if you want to make a commercial product or else you risk losing literal years of development just from rewriting the same thing over and over.
not to say that there’s a reason why a lot of people chose Unity. Godot may be in development since 2014 but they are still relatively new in popularity. not only they have less total instructions resources from the community due to it obviously being smaller than Unity’s, but people also look for already known games as one of the first factors when choosing something, which is something Godot is still catching up on. knowing legal jargon to even comprehend the difference between free and proprietary is the least of their worries when someone wants to jump into game development and build stuff with it.
I’m reminded of a post recently where someone asked how to get rid of a dialog in Windows and got swamped with replies saying to install Linux. It’s like getting a check engine light in your car and being told to buy a truck.
the key part is that regular people won’t know beforehand until they need to notice.
This isn’t regular people it’s game developers. I’m sure they knew the difference between proprietary and free software back in 2017 but probably decided not to care. Now face the consequences
the “just don’t do it” argument ignores the problem. it’s like replying “just don’t buy Apple products” to people complaining about right to repair. the key part is that regular people won’t know beforehand until they need to notice. by that point, it’s profitable enough to show other companies like Samsung and Motorolla that restrictions are profitable, so jumping around brands will also never work when the intention is to have your phone for a long time.
back in the context of game dev, add that to the part where not only people don’t anticipate the retroactive changes of a license they have to rely on when choosing an engine, but there’s the added weight of having to learn an entirely new library and oftentimes even an entire new programming language, so you have to commit to it if you want to make a commercial product or else you risk losing literal years of development just from rewriting the same thing over and over.
not to say that there’s a reason why a lot of people chose Unity. Godot may be in development since 2014 but they are still relatively new in popularity. not only they have less total instructions resources from the community due to it obviously being smaller than Unity’s, but people also look for already known games as one of the first factors when choosing something, which is something Godot is still catching up on. knowing legal jargon to even comprehend the difference between free and proprietary is the least of their worries when someone wants to jump into game development and build stuff with it.
I’m reminded of a post recently where someone asked how to get rid of a dialog in Windows and got swamped with replies saying to install Linux. It’s like getting a check engine light in your car and being told to buy a truck.
This isn’t regular people it’s game developers. I’m sure they knew the difference between proprietary and free software back in 2017 but probably decided not to care. Now face the consequences