• 0 Posts
  • 64 Comments
Joined 11 months ago
cake
Cake day: July 31st, 2023

help-circle





  • So an option that is literally documented as saying “all files and directories created by a tmpfiles.d/ entry will be deleted”, that you knew nothing about, sounded like a “good idea”?

    Bro, if it sounded like a good idea to someone, you didn’t fucking warn them enough. Don’t put this on them without considering what you did to confuse them.

    Also, nfn, the systemd documentation is a nightmare to read through, even if you know exactly what you’re looking for.

    (I’m still gonna keep using systemd because it’s better than the alternatives, though. OP, don’t write stuff off because 1 guy is a dick.)



  • Two stories like this–as in, “oops AI sucks actually”, in about as many weeks. (The other one was about Amazon shutting down their Just Walk Out mechanical turk nonsense.)

    I think we’re starting to see the tide turn against Altman’s big con.

    I liked this quote BTW:

    the test left it confident “that a voice-ordering solution for drive-thru will be part of our restaurants’ future.”

    lmao you… already have one of those? So the subtext of this message is “we can’t just say AI was a terrible idea but yeah, we’re going back to the shit that worked before”











  • Similar to docker, but the technical differences matter a lot. VMs have a lot of capabilities containers don’t have, while missing some of the value on being lightweight.

    However, a more direct (if longer) answer would be: all cloud providers ultimately offer you VMs. You can run docker on those VMs, but you have to start with a VM. Selfhosted stuff (my homelab, for example) will also generally end up as a mix of VMs and docker containers. So no matter what project you’re working on at scale, you’ve probably got some VMs around.

    Whether you then use containers inside them is a more nuanced and subtle question.