• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • 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”



  • 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.





  • As with all jokes it matters who the audience is. My friends can make off-colour jokes with me, I can reciprocate with off-jokes. But I would never do this with people not fully aware of my actual opinions. This also counts to clear misogynistic jokes.

    My closest female friends they would be fine with it, they’ve known me for years, I’ve supported them in their lowest and they know I would never mean the a horrible thing I say. They’ll happily reciprocate with some toxic male jokes, or some gay jokes. That said, even when I make them they are both clear intended to be jokes, but if they ever looked uncomfortable then it would be my guilt to bear, as at the end, as the audience they are meant to enjoy the joke, not be sad or hurt by it.

    Making them to strangers is a big no-no, and if strangers are in the room with you at the time (like a party) you also have to “match the energy” of your friend. That means don’t randomly do something misogynistic that they would understand to be a joke, but strangers would not. I think this is the hardest for most people as they don’t consider that strangers witnessing could also be accidental audiences.


  • we should be shooting: the millionaires who hire the poachers

    Damn, I was looking forward to eating them. :(

    But you’re entirely right. Obviously the poachers do the hunting, but there are people rich enough out there that put a price on rhinos to begin with, they are the real problem. They wouldn’t be hunted if there was no incentive.