nycticorax
Joined 16 years ago
Joined 16 years ago
But I can't agree with the claim that "nan is almost always a mistake". Certainly if you're doing floating-point computation on large arrays, the last thing you want is e.g. for an error to be thrown in a elementwise division just because two corresponding elements both happen to be zero.
It's true that nan!=nan is one of the more 'controversial' parts of the standard, that possibly would have been decided the other way in a perfect world. But it was also a reasonable pragmatic decision at the time the standard was developed. See here: https://stackoverflow.com/a/1573715/1013442
But I'm not sure I really understand what happened. AFAICT, Valve had a contract with Blue Systems, specifically a subunit of Blue Systems that does KDE development. Blue Systems decided to sell that subunit to Techpaladin, Nate Graham's company. Riddell was unhappy about this, and proposed that... I guess that Blue Systems not sell to Techpaladin? Or that Techpaladin reorganize itself into a worker-owned company? And then when Graham declined to do this, stuff happened, and eventually Riddell got fired from Techpaladin, or not hired by Techpaladin, and now Riddell is not getting paid to work on KDE. So Riddell has (not unreasonably) decided to stop working on KDE. And the other people who once worked for Blue Systems and now work for Techpaladin have decided to keep working for Techpaladin.
Am I missing something? Being unfair to someone?