As someone who tried to maintain a large application flatpak I would say it’s pain in the ass to work with and things break often. The way it’s configured and how permissions are set needs to be simplified.
From the “universal package formats” that’s the one I’ve had issues with when using it on a distro not specifically mentioned to work, it was supposed to be universal! Though not sure if that’s an issue with whoever packaged the app or anything specific with AppImage. Poor experience anyway.
Also no repo model. I like package manager to deal with shit. We have sorta solutions for that but not quite like snaps and flatpaks.
Also the dependencies stuff is weird. They advice you to think of the oldest (LTS?) distro you think the app will be used on and use deps compatible with that one. Which just seems, I dunno, icky, for lack of better word.
But for a random one-off app, I think it’s fine. I prefer flatpak but it’s fine, I wouldn’t avoid it or anything.
I’m not necessarily opposed to it, as I do use them if they’re inaccessible to me otherwise and if it’s official and up-to-date. But for security-sensitive apps (like a browser) I would rather not rely on it. Furthermore, it seems it’s unofficial anyways.
This is so rude. You've done nothing for the guy (neither have I), and have probably used and benefited from his work (that we did not pay for) in some way - and then to single him out and ridicule him? There's an actual human on the other side there...
That part is stupid indeed. If you run X, do xinput and find your trackpad. Then do xinput list-props on that to see all the settings there are. Xinput can also change them with xinput set-prop and they reset after a reboot, so feel free to fiddle around.
Once you’re done, just slap your settings into a script and run that on startup, then you’re set.
There is a pre built distribution, you need to configure binary cache to get it. Refer to the “Substitute for nonguix” section: gitlab.com/nonguix/nonguix
Guile and Guix is way better documented than Nix. The language have more features, so you don’t have to use a hack to load packages, can actually know what is accepted in a function instead of blindly copying what others do, and it comes with a formatter.
I think the language is harder but more powerful than Nix’s.
Imo a better manual and examples would help a lot.
I’d say one of the biggest issues is the one with proprietary drivers - you can’t really find examples and guides on how to get drivers working because it’s kept hush-hush, and to install them yourself requires knowledge on how to set things up, knowledge which beginner users don’t have ofc.
I’m a big fan of Guix and Guile but atm I couldn’t switch over due to this.
I don’t work with music at all, so most of this update doesn’t mean much to me. However, it’s nice to see the export window was improved—I want my single-click behavior, damn it.
The telemetry is limited to update-checking and error reports. Distributions will disable update-checking because they already handle updating Audacity. Error reports need to be manually submitted. It’s possible that most distributions just disable networking altogether when building Audacity, if it even exists in their repositories at all. Fedora’s package is waaay out of date. Arch disables networking altogether.
Audacity has still instituted a CLA. This is quite worrying. But nothing has happened yet.
I should have specified that the Audacity CLA allowed Muse Group to relicense Audacity from GPLv2 to GPLv3. Yes, I agree with you that not all CLAs are bad. While you keep the copyright to all your contributions, because the copyright is assigned to them (? I’m not actually sure about this), they can relicense it. The CLA agreement.
You grant MUSECY SM LTD, an affiliate of MuseScore and Ultimate Guitar, (“Company”) the ability to use the Contributions in any way. You hereby grant to Company , a perpetual, non-exclusive, worldwide, fully paid-up, royalty free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute your Contribution and such derivative works.
There was quite a lot of confusion and outrage about this at the time, so I can’t recall whether Muse Group specifically said they wanted to include Audacity in Apple’s app store or this was given as an example of why the CLA could be beneficial. My rebuttal was this is not a particularly noble cause. There was also the argument that the FSF requires you to sign a CLA for its own projects so it can reserve the right to relicense it if it benefits the project. My rebuttal to this was…well, it’s the FSF. The day the FSF relicenses their software under a non-free license is the day they die.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.