• 8 Posts
  • 54 Comments
Joined 2 years ago
cake
Cake day: March 28th, 2025

help-circle


  • While I agree on principle, we’re not always using big-name websites. The argument falls short for some-local-blog.com, there’s no security improvement on clicking that link as opposed to shortener.tld/blog-link. I’d say we should trust the source of the link instead of the link itself. Link shortening can be useful if you want long links to look nice when sharing, or simply for personal use so that you don’t need to remember long links to access an internal resource. Or just for personal websites. I can link my CV at https://domain.tld/cv instead of the full PDF file path, for example.








  • For most “normal” setups, no. Networks, environment variables, volumes, permissions etc. map pretty much one-to-one.

    If you’re using compose, you can even keep your setup mostly unchanged and use podman compose. Although, I would recommend learning a bit about quadlets and using them instead. There’s a tool called podlet that can help you translate your docker commands to quadlets, although it’s not complete and does miss some features. The annoying thing can be some QoL tooling that exists for docker compose that doesn’t for quadlets e.g. automatic restart for changed quadlet files. I wrote some scripts for most of these situations. I will probably release them at some point after I make sure that they don’t rely on any specific properties of my setup. But you can easily write them for yourself if you know some shell scripting.

    For docker run commands, you can mostly get away with changing it to podman run.








  • I love the rolling release model, and the AUR. (I even maintain some packages on AUR.) I have installed and used pure Arch in the past, if only for the rite of passage.

    But nowadays I mostly use EndeavourOS. It’s basically Arch once it’s installed, but has a nice and fast installer, with great defaults. Also, the community is awesome. I rarely need any help anymore, but I still like hanging out in their forums helping others, and generally chatting about non-Linux stuff.


  • Fair enough. I’m not a professional programmer, so I guess I won’t understand your frustration with long term maintenance of Go code. I do agree that it can be unnecessarily verbose. Writing something as simple as an http server takes a long time. Also, the dependency management sucks. It can’t seem to decide if it wants to be declarative or not.

    I do like that it’s dead simple though, and that the standard library has most of the basic stuff. I’ve mostly replaced the need for Python with Go, for small CLI apps. Nowadays, I only use Python when I have to use some specific library, mostly for mathematical computing.



  • I don’t think there’s an std-way of doing it, but the Rust ecosystem has this thing where people usually settle around one library. In this case, it is tokio. Afaik, most async stuff is done using tokio. What little async I’ve used, it’s been using tokio or some library like actix-web that uses tokio under the hood.

    Also, side note, I never understood the idea of why golang is ugly. I think it’s fine, except for maybe the repeated if err != nil guards. Those are ugly. I wish it used additive types for error handling.