@avidamoeba@lemmy.ca
@avidamoeba@lemmy.ca avatar

avidamoeba

@avidamoeba@lemmy.ca

This profile is from a federated server and may be incomplete. Browse more on the original instance.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

A single source of truth for software is one way to solve that. There are others with different pros and cons in active use that have shown pretty good results.

avidamoeba,
@avidamoeba@lemmy.ca avatar

And loving it! 🍆

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

Because you can package and deploy OS components with it. As a result you can build an OS with it, do foolproof updates of it and …gulp, happy tearrollback components without involving any other system like a special filesystem.

My bravery comes from being a software guy that’s been doing OS software development for over a decade so I believe my opinion is somewhat informed. 😂 I’m currently working on a software updates implementation for an automotive OS.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

Answered under the sibling comment: lemmy.ca/comment/4954544

avidamoeba,
@avidamoeba@lemmy.ca avatar

I like snaps.

avidamoeba,
@avidamoeba@lemmy.ca avatar

Don’t threaten me with a good time.

avidamoeba,
@avidamoeba@lemmy.ca avatar

Yup. It’s bullshit. They just don’t include Flatpak in the default OS from the installation media.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

I think they’re a good way to package apps. Superior to Flatpak for sure. I like Flatpak too and if Canonical abandoned Snap tomorrow, I’d switch my snap-packaged apps to Flatpak. The only non-bullshit downside of Snap is the proprietary server-side and the lack of multi-repo support. I don’t care much about either because I know implementing either is fairly uncomplicated and it will happen should the reason arise. If Debian wanted to start using Snap, it’d take them a month to get the basics working with their own server side. If the client side was proprietary too, I’d have had a completely opposite opinion on Snap. Finally Canonical supplies all the software on my OS. I use third party repos only when absolutely necessary. If Canonical ran a proprietary apt server side, I wouldn’t even know, apt doesn’t care. Some of the myriad HTTP mirrors could easily be running on IIS, or S3, or Nexus. The trust equation for snap is equivalent.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

I like this comment.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

Upstart 😶‍🌫️

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

The initial use case for Snap, when it used to be called Click (circa 2012-13), was mobile apps for Ubuntu Touch. Those were the same as desktop Qt apps, just using the a mobile theme and layout. Canonical developers just had the foresight to create a design that isn’t limited to that use case. As a result Snap is a superset of Flatpak in terms of use cases. Flatpak can probably be rearchitected to match that if anyone cared. If that were the case I’d also be drumming it up.

The funny thing is, we wouldn’t be having any of these discussions over the merits of Snap if RedHat came up with it instead of Canonical and the server side was OSS from the get go. When RedHat was cool that is. In fact likely Canonical would have been using thet too. Just like they use PulseAudio, Systemd, and Wayland.

avidamoeba,
@avidamoeba@lemmy.ca avatar

If you reinstall often a separate /home makes some sense. Otherwise it’s probably pointless. I’d try to get to a point where I don’t have to reinstall my base OS and invest in an automatic backup solution.

avidamoeba,
@avidamoeba@lemmy.ca avatar

Could be. I know docker and this looked like a nail.

avidamoeba,
@avidamoeba@lemmy.ca avatar

And yes.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

Yes. It even pulls the image for you if you don’t have it.

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

Whenever you get bored:


<span style="color:#323232;">~$ sudo docker run -it --rm archlinux bash
</span><span style="color:#323232;">[root@5452124778b3 /]# pacman -Syu
</span><span style="color:#323232;">:: Synchronizing package databases...
</span><span style="color:#323232;"> core downloading...
</span><span style="color:#323232;"> extra downloading...
</span><span style="color:#323232;">:: Starting full system upgrade...
</span><span style="color:#323232;">resolving dependencies...
</span>
avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

Ooof. That hurt.

avidamoeba,
@avidamoeba@lemmy.ca avatar

Because Canonical bad.

avidamoeba,
@avidamoeba@lemmy.ca avatar

/sarcasm

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

Serving files over HTTPS is not difficult to implement If anyone cared. Even if the cloud backend was open source you still wouldn’t use it. Downvote now!

Ubuntu 24.04 LTS Committing Fully To Netplan For Network Configuration (www.phoronix.com)

The Canonical-developed Netplan has served for Linux network configuration on Ubuntu Server and Cloud versions for years. With the recent Ubuntu 23.10 release, Netplan is now being used by default on the desktop. Canonical is committing to fully leveraging Netplan for network configuration with the upcoming Ubuntu 24.04 LTS...

avidamoeba, (edited )
@avidamoeba@lemmy.ca avatar

Can it suck more than NetworkManager? 🥹

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #