• 1 Post
  • 50 Comments
Joined 1 year ago
cake
Cake day: September 24th, 2023

help-circle



  • asking the maintainers to lock down APIs which the C devs purposefully leave malleable, in part, to avoid binary blob drivers being feasible.

    No, they were asking them to define the semantics of the filesystem APIs. Those semantics are not encoded in the C API but the Rust devs wanted to encode them in the Rust API to avoid making mistakes.

    The C devs didn’t want to, not because of concerns about binary drivers, but because the semantics are already broken. Apparently different filesystem drivers assume different semantics for the same functions and it’s a whole mess. They don’t want to face up to this and certainly don’t want anyone pointing it out, so clearly it must be the Rust devs’ fault for wanting APIs to have consistent semantics.

    The rest of your comment is nonsense.


  • Totally depends what you end up working on as a programmer. If it’s web apps, you’ll be totally fine. All you need is basic arithmetic. Writing a game engine? You’ll need to know some basic to moderate matrix maths…

    If you’re doing formal verification using unbounded model checking… good fucking luck.

    On average I would say most programming tasks need very little maths. If you can add and multiply you’ll be fine. Definitely sounds like you’ll be ok.
















  • You missed the point. He understands all these things you tried to explain. The point is that your definition of the word “concurrency” is objectively wrong.

    You:

    you seem to be doing multiple things at the same time. In reality they are run little by little one after another

    The actual meaning of the word “concurrency”:

    The property or an instance of being concurrent; something that happens at the same time as something else.

    Wiktionary actually even disagrees with your pedantic definition even in computing!

    (computer science, by extension) A property of systems where several processes execute at the same time.

    I suspect that concurrency and parallelism were actually used interchangeably until multicore became common, and then someone noticed the distinction (which is usually irrelevant) and said “aha! I’m going to decide that the words have this precise meaning” and nerds love pedantic "ackshewally"s so it became popular.