Re:Basic Concepts in Unity for Software Engineers
by gentleman11 on Monday October 12, 2020 @11:23AM
(#24755332)
Unity also has a history of retroactively changing its license to revoke usage rights on assets you purchase. Eg, revoking you’re ability to let your freelancers use your asset licenses earlier this year. I just don’t trust the company as a partner after that stuff
[ Parent
| on HN ]
Re:Basic Concepts in Unity for Software Engineers
by gamblor956 on Monday October 12, 2020 @11:37AM
(#24755518)
That's one example, and it wasn't Unity retroactively revoking a license. It was Unity clarifying that the use case (of a purchased asset by a contractor) was never part of the rights granted in the first place.
Unity's licensing model has always been that developers or users must pay for their own license (for an asset or non-free subscription) unless they are part of an entity's license. Unity clarified that only employees of an entity, or subsidiaries of an entity and the subsidiary's employees, are covered by the license.
This is generally always how it works with software licensing: independent contractors, by virtue of being separate businesses, must pay for their own tools and licenses (and indeed, that is one of the factors in the independent contractor test under federal US law).
Re:Basic Concepts in Unity for Software Engineers
by gentleman11 on Saturday October 17, 2020 @12:17PM
(#24811044)
You are mistaken in this case. First, unity explicitly allowed such sharing before. Second, it’s not always how it works and unreal explicitly allows it