• 0 Posts
  • 80 Comments
Joined 2 years ago
cake
Cake day: July 22nd, 2024

help-circle

  • For context: I am 29, 5 years in the workforce after university. Also German.

    For me it’s the pointlessness about all of it. I live with the expectancy of this world going to shit since my formative years. Nothing ever feels like it is getting better. If society is talking about my generation it’s either “sorry here is another burden we don’t want to take care of right now” or “this generation is too lazy, too weird, too something”.

    I am supposed to pay for 1/2 of someone that was allowed to stop working at 63 while I fully expect to work until I’m 70 or dead because of some war about water supply.

    I am also supposed to keep consuming because otherwise the economy will collapse.

    I am also supposed to keep my own stockpile of cash because probably the system won’t provide for me when I am old.

    I am also supposed to always keep learning because otherwise some AI will steal my job.

    All the while every tech company out there is hellbound to make me feel miserable because that is the best way of keeping me engaged to make them some profit either via ads or by selling my data or both.

    It’s just so… meh. And then the garbage bin is full again and all I can think about is “yeah be a good little cog in the machine and bring out the trash”







  • After writing this comment I noticed it became a bit ranty, sorry for that. Something about this article rubbed a bit in the wrong way.

    The relevant section seems to be this:

    Browser engines and garbage-collected runtimes are classic examples of code that fights the borrow checker. You’re constantly juggling different memory regions: per-page arenas, shared caches, temporary buffers, objects with complex interdependencies. These patterns don’t map cleanly to Rust’s ownership model. You end up either paying performance costs (using indices instead of pointers, unnecessary clones) or diving into unsafe code where raw pointer ergonomics are poor and Miri becomes your constant companion.

    The first half is obviously correct, this kind of data model doesn’t work well for the ownership model rust uses for its borrowchecker. I don’t like the conclusion though. Rust makes you pay the performance costs necessary to make your code safe. You would need to pay similar costs in other languages if you intend on writing safe code.

    Sure, if you are fine with potential memory corruption bugs, you don’t need these costs, but that’s not how I would want to code.

    The other thing bugging me is how miri being your companion is framed as something bad. Why? Miri is one the best things about rusts unsafe code tooling. It’s like valgrind, or sanitisers but better.

    Now, the raw pointer ergonomics could be better, I’ll give them that. But if you dive deep into what rust does with raw pointers, or rather what they are planning to do, is really really cool. Provenance and supporting cheri natively is just not possible for languages that chose the ergonomic of a raw integer over what rust does.




  • when the mutual benefit of the practice was to provide ample space for fire trucks and ambulances on the roads.

    This view weighs comfort of pedestrians against space for emergency vehicles and just takes it as granted that cars will and thus must be allowed to park there. It only asks “who do we discomfort with these cars” and not “can we stop discomforting people with all these cars”.

    How about: no parking where there isn’t enough room for emergency vehicles left and leave the sidewalk to the fucking pedestrians that deserve not just a 1,5m tunnel of steel and concrete but a sidewalk that is comfortable to use.

    Car owners shouldn’t be allowed to discomfort every pedestrian just because of their comfort of parking right in front of their house.