Earlier quoted context omitted.
There is no way this was intentional. First you’d have to argue that only the top execs were aware of this, because a bunch of Unity employees quit due to this. Secondly, if it was a form of anchoring, they did it in the worst possible way. The problem wasn’t really the numbers, it was the base idea of using installs and having it apply retroactively. If they had just wanted to anchor they could have come out with a…
Agreed; Hanlon’s Razor applies here.
Unity's oldest community announces dissolution
391–400 of 465 posts
Re: Unity's oldest community announces dissolution
#392I keep saying it: the only way Unity will possibly convince the community that this was a mistake that won't happen again is by firing the CEO and whichever other C-levels involved in the affair. This signals that they understand this to be a fatal mistake, removes the people who has this distorted agenda, and makes it clear to future C-levels that other mistakes like this won't be tolerated.
Re: Unity's oldest community announces dissolution
#393Re: Unity's oldest community announces dissolution
#394Earlier quoted context omitted.
You don't need to innovate on the foundation of your product. It's a game engine: If it fulfilled your needs when you started, it's fulfilling your needs now. With open-source solutions A) you can't have the rug pulled from under you, as you have a perpetual license, and B) you can fix/modify/add things yourself if the business needs arise. With a proprietary solution, you might get A, but you have zero hope of B. It…
If my business is making games, I don't want to fix/modify/add things to a game engine. You do need to innovate on the foundation if you plan to maintain your game long term: new consoles support, new hardware support, obsolescence of old platforms, etc... You do not need to innovate if you plan to let your game rot and become unplayable 10-20 years later. Yes having a FOSS solution for the foundation would be ideal.…
Don't worry about it. Other people will literally solve that problem for you if they like your game enough no matter what you do. They won't even bother asking for permission.
Re: Unity's oldest community announces dissolution
#395Earlier quoted context omitted.
I have mixed feelings about the word "enshitification". Like a politician shutting down thought and debate by simply labeling something "socialism", half the people using the word don't really know what it means, or at least, they don't know the original meaning. The word comes to be fake form of intellectual sophistication. A politician says the word and people think "oh, he knows the fancy word, he must be right",…
"Enshittification" is not a hard word. It's describes itself: "En-" to make, "shit" bad, "-ification" the process of; in sum the process of making something bad. I think everyone understands that the products and services they use daily are getting worse and now they have a word to describe that experience. I think that by basing itself on the mild swear "shit" it actually distances itself from academic jargon or oth…
It's about making a product worse than it needs to be, by terrible pricing and ad infestation, in order to recoup the investment of years of underpricing to capture the market and kill competitors.
This is exactly what Unity has done.
Re: Unity's oldest community announces dissolution
#396Earlier quoted context omitted.
Providing these links without context, after claiming that MIT licensed engines won’t have any issues, sort of implies that open source engines can be used fine to target consoles. The fact developers have been able to ship Godot games on console doesn’t help much unless those developers are willing to share whatever proprietary engine-to-console-SDK-interface code they wrote. Unity and Unreal, in contrast, will happ…
> [...] sort of implies that open source engines can be used fine to target consoles. That was my intention. > The fact developers have been able to ship Godot games on console doesn’t help much [...] Well, it demonstrates that it's entirely possible, either via DIY, hiring an in-house specialist or contracting to one of the companies who has already implemented the functionality. > [...] unless those developers are…
Re: Unity's oldest community announces dissolution
#397Re: Unity's oldest community announces dissolution
#398Earlier quoted context omitted.
The stupid people are lawyers and they definitely seem to think they have a good reason.
All stupid people think they are right. Give me one concrete AGPL case that justifies their aversion. Anyway, it's their loss.
Re: Unity's oldest community announces dissolution
#399Earlier quoted context omitted.
They can't ever introduce any revenue sharing because they promised not to do that and would be immensely vulnerable to lawsuits if they ever went back on that promise. This was their attempt to do something that doesn't technically count as revenue sharing.
Now they kind of did though. Since you can pick between 2.5% and paying the install fee. Also I’m not sure how are “promises” legally binding unless they are part of a contract?
(IANAL)