lots of licensed or bought code in development in general, but knowing that you’ll have to provide code to the public eventually, means that you’ll have to take this into consideration when starting a project.
codifying in law that your customers must be able to run a server for your game, when you stop running them has the consequence, that you’ll have to buy licenses that allow you to give binaries or code for those things to your customers. every middleware or library that does not allow that won’t be a viable product anymore. It’s not more dev work, it will change how licensing in game development for middleware and such will be done.
Because you can buy other people’s code for cheaper than developing it yourself, as long as you use it within the restrictions of the license you paid for.
It doesn’t, that’s why companies rarely open-source their code. If you want to publish it you have to make sure you have all the rights to do so, you have to code in a way that’s readable for outside users, you have to make sure people can reproduce your build process, and ideally you provide support.
On the other hand, if you’re not developing the source for publication, you can leave undocumented dirty hacks, only have to make sure it builds on your machine, and include third-party proprietary code wherever you want. That’s faster and cheaper, so naturally companies will prefer it.
There’s no requirement that the open source code released after EoL has to be pretty or maintained, just functional to meet legal requirements. Using other 3rd party code would be a hurdle to get over I suppose. It would definitely take a different approach to design, but after the initial shock of changing, it wouldn’t be more difficult to do long term.
lots of licensed or bought code in development in general, but knowing that you’ll have to provide code to the public eventually, means that you’ll have to take this into consideration when starting a project.
Which is doable, but is additional time and money.
Making games online is also additional time and money.
Yes, but that’s immediately profitable, which is why so many companies do it.
codifying in law that your customers must be able to run a server for your game, when you stop running them has the consequence, that you’ll have to buy licenses that allow you to give binaries or code for those things to your customers. every middleware or library that does not allow that won’t be a viable product anymore. It’s not more dev work, it will change how licensing in game development for middleware and such will be done.
Why would coding something with less restrictions take more time and money?
Because you can buy other people’s code for cheaper than developing it yourself, as long as you use it within the restrictions of the license you paid for.
The thing is either that license model changes, or those other companies selling the code cease to exist when nobody buys something they can’t use.
It doesn’t, that’s why companies rarely open-source their code. If you want to publish it you have to make sure you have all the rights to do so, you have to code in a way that’s readable for outside users, you have to make sure people can reproduce your build process, and ideally you provide support.
On the other hand, if you’re not developing the source for publication, you can leave undocumented dirty hacks, only have to make sure it builds on your machine, and include third-party proprietary code wherever you want. That’s faster and cheaper, so naturally companies will prefer it.
There’s no requirement that the open source code released after EoL has to be pretty or maintained, just functional to meet legal requirements. Using other 3rd party code would be a hurdle to get over I suppose. It would definitely take a different approach to design, but after the initial shock of changing, it wouldn’t be more difficult to do long term.