Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @[email protected]

  • 1 Post
  • 168 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle


  • it’s not “stable”

    “stable” in this case means that it doesn’t change often. Debian stable is called that because no major version changes are performed during the entire cycle of a release.

    It doesn’t mean “stable” as in “never crashes”, although Debian is good at that too.

    Arch is definitely not “stable” using that definition!


  • dan@upvote.autoLemmy Shitpost@lemmy.worldgotdamn
    link
    fedilink
    arrow-up
    5
    ·
    edit-2
    3 hours ago

    The tweet at the top has the rest of them attached as a screenshot which does make it a bit confusing.

    Lake Superior’s tweet (the “innermost” one) came first. Tom quote-retweeted it. Lake superior replied to Tom’s tweet. Ron took a screenshot of the whole exchange and posted it as his own tweet.




  • I’ve seen many a terrible containerized monolithic app.

    I’ve seen plenty of self-hosters complain when an app needs multiple containers, to the point where people make unofficial containers containing everything. I used to get downvoted a LOT on Reddit when I commented saying that separating individual systems/daemons into separate containers is the best practice with Docker.



  • Are there better alternatives for newbs who just wanna self host stuff?

    Docker is great for a beginner, and even for an expert too. I’ve been self-hosting for 20 years and love Docker.

    Back in “the old days”, we’d use Linux-VServer to containerize stuff. It was a bit like LXC is today. You get a container that shares the same kernel, and have to install an OS inside it. The Docker approach of having an immutable container and all data stored in separate volumes was a game changer. It makes upgrades so much simpler since it can just throw away the container and build a new one.

    The main alternative to Docker is Podman. Podman uses the same images/containers as Docker - technically they’re “OCI containers” and both Docker and Podman implement the OCI spec.

    Podman’s architecture is different. The main difference with Podman is that it never runs as root, so it’s better for security. With Docker, you can either run it as root or in rootless mode, but the default is running it as root.





  • Are you sure the caching headers your server is sending for those images are correct? If your server is telling the client to not cache the images, it’ll hit the URL again every time.

    If the image at a particular URL will never change (for example, if your build system inserts a hash into the file name), you can use a far-future expires header to tell clients to cache it indefinitely (e.g. expires max in Nginx).



  • You can use WebAssembly today, but you still need some JS interop for a bunch of browser features (like DOM manipulation). Your core logic can be in WebAssembly though. C# has Blazor, and I wouldn’t be surprised if there’s some Rust WebAssembly projects. I seem to recall that there’s a reimplementation of Flash player that’s built in Rust and compiles to WebAssembly.