Sorry, bad phrasing on my end. I agree the community should suspicious, but I think the flawed premise in
It seems like there isn’t much criticism of the company or their tactics, and I’m curious if any of you think that should change.
is that there is consistent, well-founded criticism and has been this whole time. And even though the vocal folks are a minority, a lot of people feel ambivalent about the relationship rather than viewing it favorably.
I do think there are quite a few linux users and developers who are suspicious of Red Hat, they are a small-ish but pretty vocal minority.
Yeah, I’m with you all the way — no shade to OP, but the question has a flawed premise. I think the majority opinion is that they’re both an asset and a liability. They’re a huge contributor to the ecosystem and have done a lot of practical good, but I also think the community will turn on a dime if the suits overstep into FAFO territory.
(All that said, fuck Lennart Poettering. Dude couldn’t design a plan to get himself out of a paper bag.)
I’m talking about the executable binary flatpak, which is the interface used to execute and manage applications distributed in the Flatpak bundle format.
https://docs.flatpak.org/en/latest/flatpak-command-reference.html#flatpak
Flatpak: a system for building, distributing, and running sandboxed desktop applications on Linux.
Flatpak application: an application installed via the flatpak command or through a graphical interface, such as GNOME Software or KDE Discover.
Runtime: also called platform, an integrated environment providing basic utilities needed for a Flatpak application to work.
Flatpak bundle: a single-file export format containing a Flatpak application or runtime.
From https://docs.flatpak.org/en/latest/introduction.html#terminology
You might be thinking of AppImages, which are more of a pure file format.
Ah - I totally missed the Nvidia-related bit! Thanks for flagging that.
That being said, based on the maintainers’ past stances, I’m pretty pessimistic on them actually implementing a fix like that. They’re very much against the general practice of poking holes in their sandbox security perimeter.
Flatpak is quite fucking far from perfect, and will always remain so due to its flawed design and UX approach.
Pretty sure the culprit here is Fedora’s packaging which adds an opaque systemd timer to run auto-updates, but the thread immediately next to this one on my homepage just happened to be a nice case-study in Flatpak fuckery: https://lemmy.world/post/30654407
Of course, the proposed changes in the article do nothing to fix this sorta problem, which happens to be the variety that end users actually care about. Flatpak is an epic noob trap since it pretends to be a plug-n-play beginner friendly tool, but causes all sorts of subtle headaches that newcomers inevitably don’t have diagnostic experience to address.
Speaking as a data engineer, you’re having trouble because git is the wrong tool for the job. You can make it work if you use git-lfs + custom hooks — but if you choose to go that route, be aware you’re making things unnecessarily hard for yourself.
If you want to make this easy, separate out your concerns:
I was hoping to play around with the dataset over the weekend to toy with some text-embedding techniques, but they’ve pulled the cord on the download links.
Anyone have a copy of the full archive they’re willing to share, or a magnet link?
I appreciate systemd at a high level, and use it all the time, but Nanook’s comment in this thread is dead on the money in my book:
https://lemmy.world/post/30945123/17510444
The CLI interfaces for PA and SysD are janky/verbose af and make it hard for beginners to do simple things as well. E.g. try wiring up a virtual device with
pacmdthat fuses your desktop audio and mic output into a combined source using only the man pages, or putting together a fresh service from memory without looking up any directives.E: even better example, compare how easy it is to set something up to run in cron vs. a systemd timer.