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

help-circle










  • 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’m sorry, but since we’re being pedantic, this is not a proof. It’s full of assumptions, some of which are wrong.

    5% is clearly better than 100%

    Never denied it. 0% is even better. What matters is where it’s used. If it’s used for FFI, that’s understandable. Any other use should be scrutinized more. And that’s the issue. The claim of Zig’s creator is that the devs of Bun are not reliable. And to me at least, his arguments make sense.

    it’s usual for Rust projects to use at least some unsafe

    Doesn’t seem like it. This article claims that only about 20% of Rust crates use unsafe at all. Even among those, the vast majority use it for FFI, which is kinda unavoidable.

    but somehow 5% isn’t

    Again, no one claimed that. But we need more than “better than 100%” when it’s a JS runtime. And the "better"ness isn’t necessarily linear. So, even though it might be technically “better”, it might not be by much. At that point, what even is the point of the rewrite?

    Again, I’m not claiming that it’s actually badly written. I’m only claiming that your arguments are not adequate, and that Bun is not a reliable company, so take whatever they claim with a grain of salt.







  • 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.