Marzepansion

Because half-assing the implementation is the way to go

Let's deliver a broken version of accessibility in 10 minutes, that's much better.

No, simply adding "colour filters" isn't a fix either, and if that was the fix then a game wouldn't even need to do that, there are plenty of apps that can already do that, a game doesn't need to do anything for that (similar to how your screen warmth can change when it becomes night), reshade as an example of something that can do just that.

But thinking about the problem is ofcourse too hard, it's easier to whine about it and act like you know how simple it is. But when we implement accessibly we do think about it, because people with accessibility issues deserve to get something that actually helps rather than the "10 minute solution"

It's disingenuous to pass off ww2 as a current event though.

Pretty standard really. You don't want contributions to the codebase come under questionable copyright concerns, or the original creator to revoke the code 4 years later causing huge headaches potentially.

You typically have to sign these types of CLA's whenever you need to contribute to any serious project. I've had to do it for Google and Microsoft recently, and I've done it for various other open source projects as well.

Still that shouldn't concern users/gamedevs as they don't contribute to the engine code typically. Only if they want to upstream changes back into the engine publicly they would need to sign it ofcourse

I don't agree with what this proposal is aiming to do (and goes against prior EU related privacy rulings), but unfettered free speech isn't as "free" as the average American thinks it is, besides that the EU already doesn't have free speech. Many regions ban Nazi related speech for obvious historical reasons.

I'd reconsider using America's "free speech" as a model as they barely practice what they preach. Sure they have free speech, but they lack privacy protection mechanisms that then allow their police to skirt the rules and obtain evidence using tools that completely breach the veil of privacy, something many EU countries (including my own) have voted can never be used. The scope of intel gathering their intelligence community is capable of already is at a level where privacy no longer exist and all you're left with is the illusion of it.

What I'm saying is, sure this proposal is bad, but what we need isn't free speech, but protected privacy. Something the EU is having some decent success with already (compare to the US where this is conveniently forgotten as technology improves, see the earlier police argument to see what that leads to). Speech isn't going to be the only problem, as cameras achieve the ability to do facial recognition and track you everywhere (something I know EU is/has banned, see the "AI act"), and more technology allows for other types of tracking

You raised an issue that the other bulletpoint has the solution for, I really don't see how these are "key differences".

In Rust there always only one owner while in C++ you can leak ownership if you are using shared_ptr.

That's what unique_ptr would be for. If you don't want to leak ownership, unique pointer is exactly what you are looking for.

In Rust you can borrow references you do not own safely and in C++ there is no gurantee a unique_ptr can be shared safely.

Well yeah, because that's what shared_ptr is for. If you need to borrow references, then it's a shared lifetime. If the code doesn't participate in lifetime, then ofcourse you can pass a reference safely even to whatever a unique_ptr points to.

The last bulletpoint, sure that's a key difference, but it's partially incorrect. I deal with performance (as well as write Rust code professionally), this set of optimizations isn't so impactful in an average large codebase. There's no magical optimization that can be done to improve how fast objects get destroyed, but what you can optimize is aliasing issues, which languages like C++ and C have issues with (which is why vendor specific keywords like __restrict exists). This can have profound impact in very small segments of your codebase, though the average programmer is rarely ever going to run into that case.

I participated in this, have to say it was fun and it's been a thing I've said for years could make (at least) linear algebra lessons more interesting to young people. Shaders are the epitome of "imagery through math", and if something like this was included in my linear algebra classes I would have paid much more interest in school.

Funny now that this is my day job. I'm definitely looking forward to the video by IQ that is being made about this event.

To explain some of the error pixels: the way you got a pixel on the board was by elaborately writing down all operations in details (yes this included even simply multiplications), the goal wasn't if the pixel was correct or not, and depending on the location of your pixel the calculation could be a bit more complex, as long as you had written down your steps to get the result as detailed as possible.

More than likely simple mistakes were made in some of these people's calculations that made them take a wrong branch when dealing with conditionals. Hopefully the postmortem video will shed some light on these.

He's making a video as a post mortem to this experiment, so it might still be released. But I can see why it would be better not to share them (aside from privacy/legal concerns as there was no such release agreement), some of the contributors used their real names, I may be one of them. It could be a bit shameful to see this attached to your real name. They might have submitted their initial draft and then, due to circumstances, could not update the results in the several hour window that was afforded to you.

Luckily my pixels look correct though.

It's perhaps better that patch notes are written by programmers and not linguists. Incorrectly using a (harmless) phrase is perfectly okay. It doesn't detract from the important bits of the announcement at all.

edit: damn, that's a big reaction for an accidental mistake someone wrote in a patch notes highlight article.

Ah, I see now what you meant. I thought you were being sarcastic due to the italics, my bad!

Please re-read my opening sentence before responding. I'm clearly talking about the 'your shithole' part. I don't care if someone insults fascists. But it's racist to call a place "shithole", especially if the poster is from a 'first world country'.

If you read the linked post there you'll see that it's about devs discussing Serde's actions on the GH issue. How are they not related?

I try not to assume too much about the person on the other end, depending on the age he might just be an edgy teenager lashing out (yeah I know that's ironic with my previous statement). I know my upbringing glossed over certain "troubling" parts of my country's history, and that left me with certain messed up beliefs as well that I had to move past (and I luckily did)

In the end I hope they're someone who is just being edgy and ill-informed and my response at least plants a seed of doubt that is enough to prosper into acquiring the knowledge to move past their current beliefs

But you might be right, I might just be a tad overtly optimistic here. But for me Nazis are an existential threat, so I'd rather convert them early than deal with the repercussions if they ever get political power over people like myself again.