• 29 Posts
  • 308 Comments
Joined 11 months ago
cake
Cake day: December 28th, 2023

help-circle
  • renzev@lemmy.worldtolinuxmemes@lemmy.worldSnap...
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 days ago

    If you’re interested in another approach to containerizing GUI applications, also checkout out x11docker. It’s a small independent project maintained by one guy, nothing big like flatpak, but also pretty cool. The name is actually a bit limiting – it supports both docker and podman, and can run wayland apps as well. One of the coolest features, in my opinion, is the ability to run a separate X server inside every sandbox and forward individual windows to the “host” X server. That way you can prevent apps from spying on your keyboard or other apps’ windows.


  • The thing with appimages is that they expect the developer to have full knowledge of what libraries need to be bundled with their app, which makes it difficult to make truly universal appimages. In flatpak you just select one of a set list of runtimes and add any additional dependencies on top of it. Flatpak also re-uses the files for each runtime in between the different apps that use it, which saves a lot of disk space.


  • Why not containerise everything? You need libreoffice? No problem, here is a docker or podman container.

    Flatpak is basically GUI-optimized containers. It uses the same technology (namespaces) as docker and podman, just with some extra tools to make GUI-related things work properly. That’s why flatpak apps don’t use the system’s gtk version – they’re running in a sandbox with a different rootfs. You can spawn a shell into the sandbox of a specific app with flatpak run --command=sh com.yourapp.YourApp and poke around it if you want to.



  • Sorry, but in my book, actions speak louder than words. And the actions here are very clear: they made a useful service that benefited people. They paid for it out of their pocket and suffered major inconveniences in their personal lives to keep the service operational and to uphold their ideals of transparency. It’s a net positive contribution to the world, even if you account for the offensive/hurtful jokes they made along the way.

    You can spend hours talking about what people should or should not have done. Critiquing others from your high horse is easy, but it gets you nowhere. As another example, take Lemmy’s developers. You could go on for hours denouncing their tankie/authoritarian views, but it won’t change the fact that they created an anti-authoritarian and censorship-resistant platform that benefits many people.

    What I value personally is a consistent moral framework. What someone thinks on isolated issues or what kind of offensive humor they like is a lot less relevant to me. Do I disapprove of it? Yes. But do I condemn them for it? No. Because actions speak louder than words.









  • It’s going to confuse everyday users

    Call me a conspiracy theorist, but I believe this is the intention. I think big companies deliberately put in confusing and bad design to “test the waters” and see if people will still buy their products. It’s the same with the apple mouse charging on the bottom, or why companies keep making their logos uglier with each iteration. It’s a psy-op to condition the masses into accepting worse products without complaining.





  • renzev@lemmy.worldtoScience Memes@mander.xyzNobel Prize 2024
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    1
    ·
    1 month ago

    When I hear “AI”, I think of that thing that proofreads my emails and writes boilerplate code. Just a useful tool among a long list of others. Why would I spend emotional effort hating it? I think people who “hate” AI are just as annoying as the people pushing it as the solution to all our problems.


  • Maybe I’m confused, but from what I understand, “declarative” means you tell the computer what you want the final thing to look like, and “imperative” means you tell the computer what steps to take. So Dockerfile would be imperative because it’s a set of commands that are executed in-order to create the image. Meanwhile docker-compose.yml is declarative because you say which containers are used with what options and how they’re interconnected. IDK tho, as far as I understand the definitions aren’t that rigid




  • This (and systemd bugs) is the main reason I moved away from nixos on my homeserver. Nowadays if I want declarative configuration, I just cram everything into docker containers and write a huge docker-compose.yml for everything that I want to run. Would still recommend nixos for things that don’t require a lot of tweaking. Like if I had to set up a simple website for a small business or something. I love how you can set up SSL certificates for nginx with autorenewal just by switching it on in configuration.nix.