Just a guy doing stuff.

  • 0 Posts
  • 89 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle

  • I’m sorry, my goal wasn’t to be a bother. My initial comment was intended to be friendly and funny - I’m not trying to patronize or be antagonistic. I learned a couple of years ago that I have autism, so I should have learned my lesson by now and stopped trying to be funny; It never pans out the way I mean for it to.

    Hope I wasn’t too much of a drag on your day, and I hope it gets better for you.

    With that said, a genuine question with no jokes: Can you help me understand how 2016 counts as recent, given the context? It was almost a decade ago, and I’m having trouble comprehending how it counts at all as recent since in tech “recent” usually means “in the last 2-3 years” unless you’re comparing to something from a much longer time ago like the 90s.


  • It was a lighthearted jab at calling 8 years ago recent; Not a political statement about Apple or operating systems.

    8 years is a ton of time in tech, CPUs from 2016 are ancient. Single-core CPU performance has doubled in Intel’s laptop chips since then, and modern laptop CPUs from Intel are often 12-core, versus the top end 2016 MacBook Pro having 4 cores.

    Not trying to start any fights, was just poking fun at the choice to call 2016 recent













  • Yep, as someone who just recently setup a hyperconverged mini proxmox cluster running ceph for a kubernetes cluster atop it, storage is hard to do right. Wasn’t until after I migrated my minor services to the new cluster that I realized that ceph’s rbd csi can’t be used by multiple pods at once, so having replicas of something like Nextcloud means I’ll have to use object storage instead of block storage. I mean. I can do that, I just don’t want to lol. It also heavily complicates installing apps into Nextcloud.




  • Hexarei@programming.devtoSelfhosted@lemmy.worldWhy docker
    link
    fedilink
    English
    arrow-up
    19
    ·
    10 months ago

    Others have addressed the root and trust questions, so I thought I’d mention the “mess” question:

    Even the messiest bowl of ravioli is easier to untangle than a bowl of spaghetti.

    The mounts/networks/rules and such aren’t “mess”, they are isolation. They’re commoditization. They’re abstraction - Ways to tell whatever is running in the container what it wants to hear, so that you can treat the container as a “black box” that solves the problem you want solved.

    Think of Docker containers less like pets and more like cattle, and it very quickly justifies a lot of that stuff because it makes the container disposable, even if the data it’s handling isn’t.


  • That’s pretty much what I do as well. It was an absolute game-changer for me when I discovered tiling WMs some ~7 years ago, because it meant super consistent keyboard shortcuts for getting to exactly what I wanted to interact with. I know where individual apps/tasks go, so I put them there. And then when I need to switch to them, it’s as straightforward as Super+[workspace].

    Also helps a ton that i3wm’s workspaces only take up a single monitor at a time, which makes it excellent for jumping between monitors.

    None of this is set in stone, but I usually follow a relatively consistent pattern:

    Center Monitor

    • 1: Primary/“serious tasks” web browser
    • 4: Any remote or virtualized desktop I might have open at the time
    • 6: Image/video editors. Also sometimes just misc usage.
    • 8: Development web browser next to neovim
    • 9: Steam/games
    • 10: Misc. Often a DBMS or file manager
    • 11: Misc. Often where I put any secondary tasks or second projects I need to reference
    • 12: Misc. Often where I’ll stick any long-running tasks that I just need to check on every now and again.

    Left monitor

    • 2: Music/comms/task list

    Right monitor

    • 3: Always only a terminal.
    • 5: Text editor to use as a
    • 7: Secondary/“wasting time” web browser