This isn't to say that you're wrong about your main point. Steam is heavyweight to use just as an input profile selector at application launch. But you should be careful about details if you choose to include them.
3,851 karma · joined April 14, 2013
This isn't to say that you're wrong about your main point. Steam is heavyweight to use just as an input profile selector at application launch. But you should be careful about details if you choose to include them.
I know a fair number of people who still have to plan to that degree. It's not a foreign idea for them. It's their daily life.
(Yes, I understand that Wendy's claimed it was only ever going to be used for discounts. But frankly, I don't believe them. The temptation to increase prices is just too powerful to ignore for a profit-maximizing MBA.)
But if you're running a multiplayer game with random elements and aren't colluding, you don't have to let a malicious party set the RNG seed to whatever they like just because you agree on it at game start. There's any number of simple cryptographic protocols that allow each peer to contribute equally to the RNG state based on having a separate commitment phase. And it's a lot easier to run a quick cryptographic setup than it is to have constant input-driven adjustment.
They may have cases where they break down, but their net social impact is positive.
But Putin doesn't care about that, so the war will continue until something changes militarily.
Hash tables are O(log n) structures when you don't hand-wave away the "compute a hash" part. The thing is, search trees are far worse than that in practice and you aren't hand-waving away the "compare two elements" part. That's where the real speed savings come from.
So going back to the GP - pay for software where you're in the largest organized user class. That's how you get power. Paying alone doesn't suffice.
This is not software engineering. This is an appeal to faith. Software engineering requires precise semantics, not whatever the compiler feels like doing. You can't even declare that this feature has no semantics, because it actually introduces a vector for UB. This is the sort of "feature" that should not be in any language selling itself as an improved C. It would be far better to reduce the scope to the point where the feature can have precise semantics.
As a software developer, your job is to understand code and business constraints so you can solve problems the way most appropriate for the situation. If you aren't actually keeping up with those constraints as they change through time, you're not doing your job. And yeah, that's a kind of fraud. Maybe it's more on yourself than your employer most of the time, but... It's your job. If you don't want to do it, maybe it's more respectful of your own time, energy, and humanity to move on.