• 0 Posts
  • 41 Comments
Joined 4 years ago
cake
Cake day: May 31st, 2020

help-circle
    • AFAB = assigned female at birth; basically because they happened to have a vagina at birth, so they were supposed to like pink and dolls and a lower paycheck and whatever else society has decided the female experience should be like.
    • AMAB = assigned male at birth
    • NB = non-binary; a person that identifies neither as male nor as female. They might be something in the middle, or they might be something completely different.
    • femme = basically the way women have traditionally looked or behaved (long hair, pink etc.)
    • fundie = fundamentalist Christian; basically very conservative, very eccentric people with world views they claim to be traditionally Christian
    • bussy = boy pussy; the anus of a man, or it may also be used to describe the vagina of a transmasc person
    • transmasc = transmasculine; a person who was assigned female at birth, but who rather identifies with masculinity and may have taken measures to be perceived as such (clothing, hormones, surgery etc.)

  • I mean, if we’re talking about all those problems, the no-type-annotations issue is rather specific for Python, JS/TS and Ruby.

    But in general, I feel like there’s somewhat of an old world vs. new world divide, which happened when package registries started accepting libraries from everyone and their cat.

    In C, for example, most libraries you’ll use will be quite well-documented, but you’ll also never hear of the library that Greg’s cat started writing for the niche thing that you’re trying to do.

    Unfortunately, Greg’s cat got distracted by a ball of yarn rolling by and then that was more fun than writing documentation.
    That’s the tradeoff, you get access to more libraries, but you just can’t expect all of them to be extremely high-quality…






  • The guy keeps on picking on Go, which is infamous for having terrible error handling, and then he has the nerve to even pick on the UNIX process return convention, which was designed in the 70s.
    The few times he mentions Rust, for whatever reason he keeps on assuming that .unwrap() is the only choice, which’s use is decidedly discouraged in production code.

    I do think there is room for debate here. But error handling is a hellishly complex topic, with different needs between among others:

    • short- vs. long-running processes
    • API vs. user-facing
    • small vs. big codebase
    • library vs. application code
    • prototyping vs. production phase

    And even if you pick out a specific field, the two concepts are not clearly separated.
    Error values in Rust usually have backtraces these days, for example (unless you’re doing embedded where this isn’t possible).
    Or Java makes you list exceptions in your function signature (except for unchecked exceptions), so you actually can’t just start throwing new exceptions in your little corner without the rest of the codebase knowing.
    I find it quite difficult to properly define the differences between the two.




  • Ephera@lemmy.mltoLemmy Moderators@lemmy.worldBanning Spree?
    link
    fedilink
    arrow-up
    5
    arrow-down
    4
    ·
    6 days ago

    I mean, the flipside could be just as true. I would be surprised, if there’s not some right-wing twats, who felt attacked in their manliness by the concept of veganism, and then started gaming the system by deploying tons of downvote bots. If you regularly downvoted posts without commenting, you might’ve looked like such a bot.







  • Ephera@lemmy.mltoScience Memes@mander.xyzBurning Up
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    6
    ·
    10 days ago

    What annoys me about that phrasing, is that “how water feels” is quite relevant to how humans feel.

    The obvious example is that if it’s below 0°C, it starts freezing, which causes slippery sidewalks, snow, dry air, all that stuff.
    But just in general having a feeling how much water will evaporate and later precipitate at certain temperatures, and even stuff like how hot beverages and cooking temperatures are, it’s all still relevant for humans…




  • If you’ve so far been able to do this stuff in Java, then presumably all your hardware has an OS and such and you don’t need this, but a colleague has been having a lot of fun with Rust and proper embedded development.

    It’s very different from regular development, as you’ve got no OS, no filesystem, no memory allocations, no logging. It can most definitely be a pain.
    But the guy always has the biggest grin on his face when he tells that he made a custom implementation of the CAN protocol (TCP is too complex for embedded 🙃) and that he had to integrate an LED to output error information and stuff like that. At the very least, it seems to be a lot less abstract, as you’re working directly with the hardware.