- The fastest code is the code you don't run.
Not really. The code can be slow, even if I do not run it. Also, sometimes additional code can do optimization (like caching), which is more code = faster. Or additional libraries, complexity and code paths can in example add multicore execution, which could speed up. So, I do not buy the less code is faster logic.
I think the guys starting the project were new. They might have hired experts along the way.
I use Thunderbirds built-in RSS reader.
I do not wait because of the state of the launch. I wait, because game will improve over time through updates. Like whatever bugs are ironed out, new features and balance changes and such. Rarely a single player game gets worse over time. In example FSR4 was added now, arguable making the game better than before, as this is the superior technology for this kind of thing on AMD hardware.
I guess it makes sense. What I struggled with is, as the type is unusable basically and I didn't like the idea it being a type. But for documentation reasons, it makes sense. Otherwise, it has no practical meaning. Even a comment could have the same effect.
To me it makes no sense. Because if it never returns, then it has no return value. Therefore it makes no sense to have a type for something that does not exist.
I don't think that's right. Nintendo cares about the lawyers cost, because that is huge. Especially the expensive ones Nintendo has, if it goes for a long time. Nintendo wants to settle this, not dragging it in court. Plus Nintendo losing in court would be very bad for them, because that signals others they can fight back. And worse, if they lose, then it becomes 100% legal everyone can point to.
Therefore Nintendo does that only if they are 100% certain, not just to intimidate like Rockstar does. And the brought up case of Yuzu does not apply here, because that was not just intimidation, that was because the Yuzu developers themselves shared Tears of the Kingdom millionth of times in Discord. And Nintendo collected this evidence against them. Yet, Nintendo did not go to court and wanted to do this with a settlement. Even in this case, Nintendo saves money and does not risk losing the battle.
And it's their first game. A truly WTF moment in gaming history... in a good way I mean.
I will be one of those who play the game later in its best state. Like I did with Cyberpunk 2077. :D I just wait until more features are added and bugs get fixed.
As said, there is nothing Nintendo can sue for. Therefore, what Cease and desist should it be?
Sued for what? There is nothing Nintendo can sue for. Also we talked about Cease and Desist before, not sueing. Also can you explain me, if you are right, why Nintendo didn't do that with prior decompilation projects of Mario and Zelda games that reached 100% and are played on a variety of systems now?
On a slightly different example, the suckless project has a huge emphasizes on lightweight code, which they call "suckless". I don't think in this case faster is the goal, but having less code and be simple as possible (not even configuration files allowed, you just recompile program) and almost no documentation in the code either. But the idea is the same, of having "lightweight" code.