• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle

  • I used to use Ubuntu in the past, and it wasn’t Unity, Upstart, Bazaar, Mir, Launchpad, Snap, Amazon ads integration etc. that convinced me to look elsewhere, it was that I found out how other, not commercial distributions, integrated and instrumented its user base into their development.

    Instead of having to sign a CLAs when contributing and signing your right away to some corporation, you become part of the community. (Update: It seems they have switched from their Copyright assignment, so something not as invasive in 2011, which is good. But they still require you to sign a CLA.)

    So always look who is developing the distribution first, are they individuals or is it one company. And don’t let yourself be bated into the dependency of one company, because then you will be the victim of enshittyfication eventually.



  • cmhe@lemmy.worldtoLinux@lemmy.mlRecommend me a scripting language
    link
    fedilink
    arrow-up
    19
    arrow-down
    2
    ·
    1 month ago

    What about Lua/Luajit?

    In most scripting languages you have the interpreter binary and the (standard) libraries as separate files. But creating self-extracting executables, that clean up after themselves can easily be done by wrapping them in a shell script.

    IMO, if low dependencies and small size is really important, you could also just write your script in a low level compiled language (C, Rust, Zig, …), link it statically (e.g. with musl) and execute that.


  • I started using Fedora Silverblue on a tablet, seems to work fine so far, but requiring a reboot in order to install new system packages is a bit cumbersome and the process itself takes a while, but ordinary Fedora also doesn’t win any races when asked to install a new package

    I think switching to FCOS or Flatcar on servers that just use containers makes sense. Since it lessens the burden of administrating the base system itself. Using butan/ignition might be unusual at first, but it also allows to put the base system configuration into a git repo, and makes initial provisioning using ansible or similar unnecessary. The rest of the system and services can be managed via portainer or similar software.

    I also do not have long term experience with FCOS, but the advertised features of auto-update, rolling-release, focus on security and stability makes it a good fit for container servers, IMO.

    An alternative to Debian on servers might also be Apline Linux. Which also has more a focus on network devices, but some people use it on a desktop as well.

    If you have many different systems, and just want to learn to operate them all, maybe NixOS might be interesting. Using flakes, you can configure multiple machines from just one repo, and share configurations between them. But getting up to speed on NixOS might not be so easy, it has a steep learning curve.


  • cmhe@lemmy.worldtoLinux@lemmy.mlCoreboot: Pros and Cons
    link
    fedilink
    arrow-up
    12
    ·
    edit-2
    2 months ago

    So generally the pro of coreboot is that it is open source, but the con is that it is open source.

    What I mean by that, you can fix any issues yourself, however, if you are unable to do it yourself, you have to wait until someone does it for you and often what features are available and stable are a hit and miss.

    Compared to proprietary bioses, the company has some kind of standardized process for developing the bios. So you often get want you would expect. However, if the money flow from the pc vendor to the bios vendor drys up, you, or the community of owners. will not be able to fix any issues.

    Linux support should be the same, regardless if you choose proprietary or open source bios. But that depends on how well the coreboot was ported to the platform. So officially supported coreboot bioses are likely better than others.

    Personally, if all other attributes are equal, would go with coreboot, because I like to support vendors that offer that choice, and IMO a open source solution, that you can review and build yourself is intrinsically more secure than a binary blob, where you have to blindly trust some corporation. But other security minded people might disagree, which is fine.




  • Not the drama itself should influence your judgment, but how they will deal with it.

    Whenever people work together on something, there will be some drama, but if they are dealing with it, then that should be fine.

    Nix and NixOS are big enough, that even if it fails, there are enough other people that will continue it, maybe under a different name.

    Even it that causes a hard fork, which I currently think is unlikely, there are may examples where that worked and resolved itself over time, without too much of burden on the users, meaning there are clear migration processes available: owncloud/nextcloud, Gogs/Gitea/Forgejo, redis/valkey, …




  • Here is the problem: Even paying will not get you out of ads any longer. You bought a TV, well the manufacturer will show additional ads on it. You paid for Windows or a Mac, well Apple or Microsoft will advertise additional services on it, same with Android (Google services) or IPhone.

    Just spending money to be ad free is no longer enough, because companies try to find ways to extract even more money (or information to sell others) from you, now that you have proven to have some. Either be it additional subscriptions or vendor lock in. They never have enough money, they just want all of it.

    So to live ad free, you have to avoid using any product with profit interest or research every company you deal with on what its incentives are, which is very hard or impossible for many people.

    Here is a tip though, try to find hardware that comes without bundled software, and find open source software to use it with.




  • What kind of comparison is that? sudo is setuid while Firefox and its extensions run as the user you started it as.

    Also sudo has just one very specific and limited use case, while Firefox is more of a platform for web content. I could argue that sudo itself is an ‘extension’ to a Linux system, like every application.

    You also don’t have to install all of those extension, you can choose which you trust, similar to a Linux system, you don’t have to install every application in the repository.

    If you say that the Firefox add-on repo should be more managed like a repository of a Linux distribution, where developers cannot simply upload their own software, but need to find a trusted maintainer first, I could agree to that. But that would mean more work and overhead.



  • Snap is just one case where Ubuntu is annoying.

    It is also a commercial distribution. If you ever used a community distribution like Arch, Gentoo or even Debian, then you will notice that they much more encourage participation. You can contribute your ideas and work without requiring to sign any CLAs.

    Because Ubuntu wants to control/own parts of the system, they tend to, rather then contributing to existing solutions, create their own, often subpar, software, that requires CLAs. See upstart vs openrc or later systemd, Mir vs Wayland, which they both later adopted anyway, Unity vs Gnome, snap vs flatpak, microk8 vs k3s, bazar vs git or mercurial, … The NIH syndrom is pretty strong in Ubuntu. And even if Ubuntu came first with some of these solutions, the community had to create the alternative because they where controlling it.


  • cmhe@lemmy.worldtoSelfhosted@lemmy.worldUncommon Syncthing usecases
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    10 months ago

    I mod my games on my PC and sync it to my SteamDeck. I also sync the save files back and fourth, to continue playing on different devices. Mostly non-steam games.

    I also sync my eBook collection to my eink reader with syncthing.

    Everything is also mirrored to my always-on NAS, so syncing always works.