• 11 Posts
  • 83 Comments
Joined 1 year ago
cake
Cake day: March 28th, 2025

help-circle


  • As far as I understand, it doesn’t keep copies of the different edits. The original file is saved, and the edits are serialized and stored in some form. Only one more copy is generated for the final version for preview and such. When editing again, you can add to or subtract from previous edits, and again a maximum of two files will be present. (But there would be no thumbnail, preview etc. for the original. So it isn’t exactly double the storage usage.)

    This is my vague recollection from what I’ve read in the discussions, so take it with a grain of salt. But this is close to what’s happening when you’re editing.






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