• 0 Posts
  • 693 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle


  • I just replaced my windshield wipers last night and it was a nightmare. The wipers I got are supposed to be universal, which means the little plastic bit that connects to the wiper arms has a bunch of little sub parts that you’re supposed to remove based on what wiper arm connection your car uses. Well, considering I’m not well versed in modern wiper arm connection standards, and I’m also stubborn and don’t think you should need to dig out your car manual just to change your fucking wipers, coupled with the fact that the instructions that came with the wipers are just 6 wordless diagrams vaguely showing you what bits to remove based on which esoteric wiper style your car uses, I struggled with those sons of bitches for like 20 minutes in below freezing weather.




  • Doing something distro-specific in an install script for a single binary seems a bit overcomplicated to me, and definitely not something I want to blindly pipe into my shell.

    The bun install script in this post determines what platform you’re on, defines a bunch of logging convenience functions, downloads the latest bun release zip file from GitHub, extracts and manually places the binary in the right spot, then determines what shell you’re using and installs autocompletion scripts.

    Like, c’mon. That’s a shitload of unnecessary stuff to ask the user to blindly pipe into their shell, all of which could be avoided by putting a couple sentences into a readme. Bare minimum, that script should just be checked into their git repo and documented in their Readme/user docs, but they shouldn’t encourage anyone to pipe it into their shell.




  • Great explanation, but I have a tiny, tiny, minor nit-pick

    Basically what he said is incoherent to anybody who has worked with larger data.

    I’m being pedantic, but I disagree with your wording. As a backend dev, I work with relational databases a ton, and what Musk said wasn’t incomprehensible to me, it just sounded like something a first year engineer fresh out of college would say.

    Again, the rest of your explanation is spot on, absolutely no notes, but I do think the distinction between “adult making up incomprehensible bullshit” and “adult cosplaying as a baby engineer who thinks he’s hot shit but doesn’t know anything beyond surface level stuff” is important.






  • C’mon man, this is just a textbook fallacious slippery slope argument. Rust isn’t some brand new language whose stable release was less than a year ago, it’s over a decade old now. Scheme and Lisp are interpreted languages for God’s sake, it’s borderline* impossible to use them for kernel programming.

    Also I’m pretty sure the whole point of the Rust project that all this drama is centered around is to keep Rust code separate from the kernel. From what I understand the whole point is to maintain Rust bindings to the kernel API as a separate project, so that if developers want to write a driver in Rust, they can without having to rewrite those bindings themselves. But the kernel code itself will still be all C code. Now I’m not a kernel developer, and the last time I wrote a driver was for my operating systems class in university over a decade ago, so take that with a grain of salt.

    * I say borderline because anything is possible with code if you’re creative enough, but anyone trying to submit Scheme or Lisp code to the Linux kernel is gonna get laughed off the Internet