3 ms·
It's a bunch of work, often involving lawyers who bill by the very expensive hour, for basically no payoff. On top of that there's a secret in the industry thou
by fragmede 2y ago
It's a bunch of work, often involving lawyers who bill by the very expensive hour, for basically no payoff. On top of that there's a secret in the industry though: there's a lot of maybe not entirely legal code copying going on. Hiring someone who's made a similar game in the past can mean that they come with source code that could be copied to shortcut the time to write code for the new game. Releasing source would expose this teensy little problem.
- nomilk 2y agoYikes, never considered that! Interestingly, those required to sign off on release of source code (e.g. company execs) may not even be able to be certain the source doesn't contain such 'borrowed' code (since devs may have left the company a decade ago, and they likely wouldn't directly admit to 'borrowing' even if contacted/asked). Can see why it's risky.
- joezydeco 2y agoNot just lifted code but patent-violating code. Ever wonder why GPU makers don't open source their drivers?
- djbusby 2y agoImplying that GPU drivers are violating patents?
- deaddodo 2y agoI don't know any major GPU driver that can be shown to use any patent infringement. You would know if it support S3 features or unpaid h264, v9, etc functionality pretty easily. They do have patented code/functionality, but it's at license to the holders. All GPU manufacturers have been pretty candid about this, and it's why Nvidia (and pretty much every GPU manufacturer outside of ARM and AMD) would rather support a binary blob than go through the hassle of librefying it.
- userbinator 2y agoIntel isn't a GPU maker?
- bitwize 2y ago> Hiring someone who's made a similar game in the past can mean that they come with source code that could be copied to shortcut the time to write code for the new game. I'm to understand that back in the day, the common practice of Japanese game developers using funny nicknames (like "S.Miyahon" for Shigeru Miyamoto) was implemented by the game companies themselves to dissuade rival developers from poaching their top talent. Perhaps they were concerned about intellectual property leaks.
- ghaff 2y agoEven if they're in-house corporate lawyers, it's still a lot of work that is a distraction from their day jobs. And, yes, there may easily be some combination of proprietary libraries and other code that isn't entirely kosher to open source in some way. And, oh, you want the build system for that code? That's something else. In a lot of cases it would involve tossing an incomplete bunch of code over the wall with few instructions about actually using it. Which is probably not what the recipients had in mind. Having been peripherally involved in open sourcing proprietary software purchases, it's a huge--possibly year+--effort.
- saulrh 2y ago> In a lot of cases it would involve tossing an incomplete bunch of code over > the wall with few instructions about actually using it. Which is > probably not what the recipients had in mind. Minecraft modders deobfuscate and decompile the game every time Mojang publishes a new release so that mods have the symbols to link against. There are way more people out there who want to play old games and have the skills necessary to modernize a game's codebase than there are making those engines, and they have more time and better-aligned incentives. Essentially every game I know of that's been open-sourced has had someone put in the time to get it building again, even things that barely anyone played. Heck, popular frequently have full-blown from-scratch remakes, c.f. the Spring Engine, OpenTTD, OpenRCT2, StepMania.
- account42 2y ago> In a lot of cases it would involve tossing an incomplete bunch of code over the wall with few instructions about actually using it. Which is probably not what the recipients had in mind. The "recipients" don't mind this at all. Many source ports built from gutted releases speak to that.
- deaddodo 2y ago> On top of that there's a secret in the industry though: there's a lot of maybe not entirely legal code copying going on. Hiring someone who's made a similar game in the past can mean that they come with source code that could be copied to shortcut the time to write code for the new game. It would be pretty hard to drag code from other engineers with you, without outright bringing the source code along. If that happened, it would very much be illegal. What's more likely to happen (and something I, and most other engineers, have done) is use their own solutions from previous work experience to develop new features. This has been tested (at least in Federal and California courts) and been found to be completely fine, as long as it's not in the end goal of infringing on protected property (e.g. developing an h264 codec/hardware blob to avoid the license).