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

help-circle




  • And it is not possible to “visualize 4D”

    Sure it is.

    • 3 spatial dimensions + time
    • 3 spatial dimensions + 1 color dimension (grayscale)
    • 2 spatial dimensions + 2 color dimensions
    • etc

    And that’s not even counting projection. All the time we interact with 3D data that’s projected to 2D (almost every photo you’ve ever looked at). There are similar ways to project 4D to 2D.

    (Not defending the video or anything, just pointing out that visualizing higher dimensions is something we know about for ages.)





  • [S]hareholders said they learned that CrowdStrike’s assurances about its technology were materially false and misleading when a flawed software update disrupted airlines, banks, hospitals and emergency lines around the world.

    I don’t see how they can make this argument.

    Falcon is a kernel module. When kernel modules fuck up, you get kernel panics.

    Sure, the layperson may not know enough about computers to recognize this, but it’s a basic enough fact about operating systems that an investor in a company like this should take the time to learn. It’s not like they hid that fact.

    If you invested in a company without knowing how their product works, that’s on you.



  • cbarrick@lemmy.worldtoLinux@lemmy.mlLinus Torvalds and Richard Stallman
    link
    fedilink
    English
    arrow-up
    82
    arrow-down
    1
    ·
    4 months ago

    However, Linus’s kernel was more elaborate than GNU Hurd, so it was incorporated.

    Quite the opposite.

    GNU Hurd was a microkernel, using lots of cutting edge research, and necessitating a lot of additional complexity in userspace. This complexity also made it very difficult to get good performance.

    Linux, on the other hand, was just a bog standard Unix monolithic kernel. Once they got a libc working on it, most existing Unix userspace, including the GNU userspace, was easy to port.

    Linux won because it was simple, not elaborate.



  • cbarrick@lemmy.worldtoRust@programming.devDioxus Labs + “High-level Rust
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    2
    ·
    4 months ago

    Fair. But unwrap versus expect isn’t really the point. Sure one has a better error message printed to your backtrace. But IMO that’s not what I’m looking for when I’m looking at a backtrace. I don’t mind plain unwraps or assertions without messages.

    From my experience, when people say “don’t unwrap in production code” they really mean “don’t call panic! in production code.” And that’s a bad take.

    Annotating unreachable branches with a panic is the right thing to do; mucking up your interfaces to propagate errors that can’t actually happen is the wrong thing to do.


  • cbarrick@lemmy.worldtoRust@programming.devDioxus Labs + “High-level Rust
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    2
    ·
    4 months ago

    Unwrap should literally never appear in production code

    Unwrap comes up all the time in the standard library.

    For example, if you know you’re popping from a non-empty vector, unwrap is totally the right too for the job. There are tons of circumstances where you know at higher levels that edge cases defended against at lower levels with Option cannot occur.







  • cbarrick@lemmy.worldtoPython@programming.devNumPy 2.0.0 released
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    5 months ago

    Huh. This got me curious.

    Yes, I did just type a bare URL. Every mature markdown parser I’ve used turns this into a link, and appropriately handles trailing punctuation.

    So I went to the spec, and it’s explicitly called out that this is not an autolink. Autolinks must be explicitly surrounded with angle brackets <>.

    So yeah \shrug.

    https://spec.commonmark.org/0.31.2/#autolinks

    Edit to be clear: This means that both of our markdown parsers are wrong relative to the commonmark spec. But I’ll argue that if a parser is going to attempt to autolink this, then handling trailing punctuation is better than not.