clarry: You don't really seem to understand how software licensing and subscriptions work. I hope you don't get dragged to court one day, with that knowledge it can get quite expensive...
rtcvb32: So Hypothetical situation. I make a computer, and i install Windows 95 on it. It has a software license attached to it, but Microsoft let's say has revoked that and you have to accept the current Windows 12 license even for something put out in 1995/1996.
Is that right? Is that en-forcible? Or if i installed and never told them, would it even matter?
Please don't make hypothetical situations that are completely irrelevant to the case at hand.
The case is this: devs/publishers are selling/distributing the Unity runtime. The only thing that gives them the right to distribute Unity is the license (or the "terms of service" of the service they've subscribed to). Unity has reserved the right to update the terms. If devs/publishers don't accept new terms, they must immediately cease distribution -- they no longer have a license to copy and sell the software.
EDIT: Compare to the situation with GOG selling games. Rightsholder may withdraw their license, unless GOG somehow negotiated an irrevocable one. If that happens, GOG will delist and stop selling the game, and they have no rights to keep distributing the game on the basis that they once had a valid license.
This has nothing to do with software versions.
The WoTC case is also completely different, so I'm not commenting on it in this thread.
rtcvb32: If you can read it (
but can't modify it or compile it) and still have to pay for it, it's only slightly better than closed source code. (
course the open source part could be a farce and they use different versions of the source when compiling; but who knows)
Rrriiiigggghhhhtttt..... Again back to the OGL for WotC, the OGL shares a small subset of the system so everyone is on the same page, it was as many called it a 'gentleman's agreement', i agree to use the OGL you agree not to sue me.
Then they tried to change the OGL and hope no one was the wiser. Who could have seen that coming? I'll just pull out my crystal ball, and see...
The OGL language had some vague language, I would have not used that license myself. It's not surprising that gamers and the game industry would though, because they will never believe that corporations are out to screw you -- despite doing that all the time.
Meanwhile the free & open source software has gone through famous license litigations back in the 90s, everyone knows how it is. Well, some people keep forgetting and keep thinking that it's fine to start pushing proprietary shit.
Of course there have been "incidents": for example, GPL was often applied with the text that it is OK to distribute under GPLv2 or later, but when GPLv3 came out, there was outcry because not everyone liked the terms. You could say that is somewhat comparable to the WoTC case but the FSF never tried to "deauthorize" existing licenses or otherwise change the license of something someone else owns; they legally CANNOT. The "GPLv2 or later" text must have been selected by the rightsholders and if they did that, they should've seen the possibility of a new license coming out with terms they don't like.
I was always sceptical of the OGL and I guess that scepticism proved right. Likewise, I've never chosen "GPLv2 or later." And I don't do license assignment -- I've had to refuse maintainership of a piece of FSF software because they want to do license assignment (i.e. transfer copyright to FSF so they can do anything they wish, including change the license).
This is sarcasm. There's no knowing this was on the horizon, anymore than the FTC deciding to ban an entire frequency range making electronics you bought that were compliant suddenly not compliant and needing to buy all new hardware. (Yes this does happen from time to time)
You can't know exactly what someone is going to do, but you can know exactly what they can and cannot legally do (or what guarantees you have been given). You can prepare for that. Protip, don't do gentleman's agreements. Do black on white. Too bad the game industry is too stubborn to learn the lesson. Even now, how many will just switch to Unreal thinking another corporation won't screw you over exactly the same way the previous one did? Lol, I hope everyone who flocks to Unreal gets rekt.
Again, when choosing an engine and finding the features you want with the amount of work to get something working, you eventually select something. Berating a dev for choosing something because it was perfectly serviceable at the time but they were a dumbass for selecting it because of unforeseen changes is stupid.
Stupid is not thinknig ahead, not learning the lesson, not managing risk.
And why isn't case 2 relevant?
Because the question of relevance is here whether a game company was stupid enough to bet their livelihood on a proprietary product whose license could change any time. The game company is making that choice (and owning the consequences of it), the employee isn't.
You might as well say All employees who work with hardware required/needed for said job is stupid.
Choosing to work with unity is not a choice made by a lone employee! It is a choice made by the company. It's a choice that can screw them over.
The company doesn't NEED to use Unity. They chose to use unity, that's where their screwup starts.
The employee NEEDS to use Unity if the company demands that. But the employee isn't making that choice, so it is not the employee's problem, nor is it their stupidity. I think my employer is stupid for betting so hard on microsoft's garbage software, and I do run it because my employer needs me to, but it is the employer that should be berated for making the choice, not the lone employee who doesn't get to choose.
I don't understand what is so hard about this.