391–400 of 428 posts
Earlier quoted context omitted.
I suppose 'power-users' can put up with 'small-button' GUIs but I do think a general purpose GUI needs to be easy to use for people who aren't used to controlling mice and keyboards all the time.
Being able to use mouse and keyboard makes you a power user in 2025?
Earlier quoted context omitted.
I'm with my neighbor comments. How do you use Ubuntu without snaps? The base Ubuntu install already comes with several snaps. Installing random things through apt leads to snaps. I personally do not know how to avoid snaps on Ubuntu.
I made this snap "alternative" to solve this exact problem: https://github.com/justinclift Packaged as: https://github.com/justinclift/snapd-empty/releases/download... It's just an empty package that tells the system snap is installed, to stop the broken dependency chains you otherwise get from force uninstalling snap. It's been working fine on a handful of Ubuntu 24.04 systems I've been handed and can't change the O…
It should be this: https://github.com/justinclift/snapd-empty/
Earlier quoted context omitted.
I'm with my neighbor comments. How do you use Ubuntu without snaps? The base Ubuntu install already comes with several snaps. Installing random things through apt leads to snaps. I personally do not know how to avoid snaps on Ubuntu.
You migrate to Debian. Everything else is a bandaid that can be rug pulled any time Canonical feels like doing so.
Earlier quoted context omitted.
> but several features in ntfy won't be available through debian packaging due to missing golang and nodejs packages Woah. Shouldn’t Node and Golang be in Debian’s official repos by now?
Nodejs itself is, but when you install a node project manually, you type npm install and wait while it downloads the 500 different packages it depends on. Debian follows the same philosophy as for other more traditional languages and expects that all these dependencies are packaged as individual Debian packages.
Earlier quoted context omitted.
You're right. You don't have to use snaps. Ubuntu migrates packages slowly in behalf of you. Using apt to install some packages installs snap plumbing and downloads the package as a snap automatically. You don't have to install it manually. There's no malicious intent though, it's made to "impose a positive pressure on the snap team to produce better work and keep their quality high" (paraphrased, but this was the of…
Installing the inferior snap packages when you apt get is one of the worst cases of a Linux distro refusing to respect the user's intent that I've experienced.
This has got to be the most user-blind self-imposed preference in a modern operating system outside of Microsoft's BS.
If you're going to use an OSS operating system, the control of what is placed on the system should be inherently with the user. If the developer has a question if a new package should be added or is required, throw a prompt and ask -- with a default to not use application containers and the default packaging system.
Really not hard.
Earlier quoted context omitted.
Nodejs itself is, but when you install a node project manually, you type npm install and wait while it downloads the 500 different packages it depends on. Debian follows the same philosophy as for other more traditional languages and expects that all these dependencies are packaged as individual Debian packages.
Just jumping in to say that this is making me genuinely reconsider adopting a licence/policy that forbids repackaging: the fact that someone can repackage my project, but worse, and still use my project's name? Absolutely not. I do not want the burden that inevitably comes when people complain to me that this or that is missing from a repackage.
Earlier quoted context omitted.
I agree that maintainers should not be expected to support patched versions of their software, but as a user I like the Debian policies you call insane. I would actually pick Debian exactly because they are cautious with the dependencies.
Debian is not cautious with the dependencies. Debian breaks a lot of what they ship, sometimes flagrantly like removing a whole feature, sometimes insiduously by introducing new bugs. I don't really care that Debian doesn't view it as breaking things. From my point of view, users trying to get my product get subpar experience in a way which is far from explicit. I personally wouldn't use Debian but people are free to…
I don't want to install an app that downloads and executes 500 node packages that I don't know what they do. Those packages should already be vetted and in Debian. If not, then I'm not interested.
Side stepping the distro repos for dependencies for software in the repos leads to unexpected behavior.
Earlier quoted context omitted.
Also watch out for surprise file deletes in /tmp and /var/tmp at 10 and 30 days. This too can be turned off.
I can’t fathom why anyone would be surprised that a directory named “tmp” is ephemeral.
I am going to assume you are used to tens of days wipings of /tmp. Imagine suddenly it was decided that the wiping needed to happen every tens of seconds for security reasons and to minimize ram usage. Do you think this would impact your workflows that used /tmp? This is 100% analogous to the current situation. Yes, tmp is ephemeral, but on what timescale?
Earlier quoted context omitted.
Just jumping in to say that this is making me genuinely reconsider adopting a licence/policy that forbids repackaging: the fact that someone can repackage my project, but worse, and still use my project's name? Absolutely not. I do not want the burden that inevitably comes when people complain to me that this or that is missing from a repackage.
I mean, that's just how OSS works. Anyone can fork your thing, do whatever, and call it a day. Going MIT or whatever won't save you either - this repackaging business is basically the entire business model of AWS.
Earlier quoted context omitted.
> Debian's heavy patching of kernel in Debian stable Needs citation. Debian stable uses upstream LTS kernels and I'm not aware of any heavy patching they do on top of that. Upstream -stable trees are very relaxed in patches they accept and unfortunately they don't get serious testing before being released either (you can see there's a new release in every -stable tree like every week), so that's probably what you've…
LTS has had major breaking changes in various areas in recent times too, virtio was badly broken at one point this year, as was a commonly used netlink interface. Hat tip to the Arch kernel contributors who helped track this down and chase upstream, as we had mutually affected users. The debian and ubuntu bug trackers were a wasteland of silence and user contributions throughout the situation, and frustratingly conti…