I think it’s even simpler than that: they want a share of Google’s data, and more control about what ads they can show to their customers constantly. Their hardware platforms are okayish and sold for a quite low price, but they monetize it on ads.
Amazon’s Fire devices already have this, they don’t use Android with Google, they use the fully open source version. They can collect any data they want already
Exactly this. There’s no nefarious motive to doing this, because Amazon can already do everything nefarious that they want to do with their current Android-based Fire OS.
I’m actually willing to take Amazon’s reasoning at face value for this. They say that Android is too heavyweight and inflexible for embedded IoT devices, and that they want to build something lighter. This makes plenty of sense, and is indeed something that Google themselves have also said as justification for their move to Fuschia for their own embedded devices.
For Linux fans, it’s probably a good thing that Amazon has chosen another Linux-based architecture rather than doing as Google are doing and moving off Linux to a different kernel.
hopefully they’ll design some package manager incompatible with android at the most basic level - and then double down when it’s proven to be a huge mistake. a good tick upwards for dev jobs, but the time for actual competition was over 10 years ago. this will fail miserably.
“hey here’s news. Maybe. I can’t actually tell you. It’s just what I was told. This hasn’t been relevant to me since it once was. But here’s a blog post about it. I like cheese.”
Really weird article. A bunch of snarky comments from the author that add nothing to the conversation. “It’s been a decade since I touched an Nvidia card, so I’m just giving you the info I read in a changeling. Couldn’t tell you if it was true or not, so fuck you!”
I am also not a fan of this website, but NVIDIA proprietary drivers are notoriously bad especially with Wayland, so I was thinking that people might find it useful and upgrade their drivers.
I’m really hoping this all forces Ubuntu out as the face of desktop Linux.
It’s been pretty low tier for years now, and Canonical just proves corporate backing doesn’t guarantee a good distro.
Snap is pretty garbage, default GNOME is horrendous, the repos break every other month, apt is still pretty lame despite being an user upgrade for apt-get, the packages are neither stable nor cutting edge, they change core OS backends like every update which breaks configs and makes documentation obsolete.
I’d like to suggest Fedora as the new goto, but I feel like it’s a bit too privacy and FOSS oriented which may scare away new users.
Debian is great but it doesn’t have latest packages which isn’t optimal as performance upgrades would take time to release or need to be manually installed.
Well, I’d prefer Canonical to fix their shit, instead of forcing immature products onto users. I’m not against snap per se, as there are valid reasons for sandboxing, especially for games (remember when Steam accidentally wiped some user’s home folders back in 2015? Sandboxing would have prevented that).
However, in its current state, snap causes just too much friction. For example Firefox can’t remember the last used directory for up/downloads, Steam snap will just create a new data directory (forgetting about the games already downloaded), there’s no way to allow additional folders (like /net from autofs) in snap apps etc. It’s just a myriad of issues which make working with the system unnecessarily complex and frustrating, and there seems to be little progress fixing those.
unfortunately, industry loves shit like Ubuntu and RHEL because of their corporate backing. comps love having the insurance of someone to blame or somebody to fix their shit when things hit the fan. I’ve worked for many comps who choose RHEL for that alone. Should we choose the OS built by a bunch of randos in their basement, or something backed by Red Hat where I can just pay them money to handle my support tickets faster if shit blows up? or who tf do I have my cyber liabilities insurance guys sue if the OS has a huge fuckin problem? I want a company behind that shit.
See, that’s the situation where we just don’t use them. I’m talking about wiping the original OS and putting something that’s really FOSS in its place.
Another not-Linux Linux based operating system. Can’t wait to argue same as with Android and ChromeOS that this is not like “real” desktop Linux looks.
We really should stick to calling it GNU or something.
Definitely not GNU, that’s even worse than calling it Linux. We should simply call it by it’s own name, Vega or whatever it ends up being. Android is Android. ChromeOS is ChromeOS. We can acknowledge they utilize the Linux kernel and some other open source code, and as such give some back. But they are not what we refer to as Linux, as that is a spirit as much as if not more than it is a collection of software.
An OS is defined by its ecosystem ( applications, users, and philosophy ). Everybody knows what an actual Linux distribution is and the kinds of desktop environments ( eg. GNOME, KDE, XFCE ) and applications that Linux implies ( eg. Docker, Podman, Emacs, GIMP, OBS, LibreOffice ). It does not matter if the C library is Glibc or MUSL. It does not matter if things were compiled with GCC or Clang. It does not matter who wrote the version of ‘ls’ installed. It is not confusing when somebody tells you they are using “Linux” on the desktop, the server, or the cloud. You know what they mean.
Saying GNU / Linux does not add any clarity in my view and could be confusing or wrong. If you use Alpine in the cloud, you are using Linux ( very clear ) but not GNU / Linux. If you are using Void on your desktop, you are using Linux ( but maybe not Glibc ). Is one version of Void Linux called GNU / Linux and the other one isn’t? It is not a useful label other than politically.
Android and ChromeOS use the Linux kernel but are not Linux distributions by any useful use of that term. If I switch you from Void to Arch, you could use it for hours without noticing the change. You might not notice until you went to update software. If I moved you to Android or ChromeOS, you would certainly notice right away. In some ways, Windows is a more similar environment than Android is.
If I say, “I use Linux”, you do not have to ask me if I mean Android or if I have a Chromebook. People that don’t “know” that these other systems use the Linux kernel would never make that mistake. The “confusion” is artificial.
As a non-Linux example, is there anybody that is confused that the XBox uses the Windows kernel? Even if I say “I game on Windows”, would you honestly wonder if I meant XBox? Or would it be super obvious that I meant on a PC?
If I say, “I game on Linux”, you again know that I do not mean Android or ChromeOS ( unless I am purposely trying to be arrogant or funny about it ). You might ask if I am using a Stream Deck but, guess what, the Deck also boots into KDE. It really is Linux.
My Nest thermometer and my IP camera both run the Linux kernel as well. Do we need a special name for them? No. Nobody is truthfully confused by that either. Would we call them GNU / Linux even if they use Glibc? I hope not. So what does GNU / Linux even refer to outside of the political meaning?
I’m pretty sure Fedora Core 4 was my first Linux daily driver. I love distro hopping but I always end up back on Fedora when I have a big project to work on and I just want vanilla Gnome, my developer tools, and no surprises.
Snaps are a relatively recent way of packaging application installations in certain flavors of Linux. Steam is Valve’s game distribution platform (amongst other things).
There’s an unofficial Snap package to install Steam and it apparently doesn’t work so good
Snap is a sandboxed environment to install applications in.
Flatpak is a more portable implementation of the same broad idea, it downloads a chroot and runs applications from within using a separate program called bubblewrap (one could, in theory, use chroot to run apps from within the downloaded flatpak images, bubblewrap offers further isolation through things like namespaces and cgroups etc. )
Snap, unlike flatpak, is a Canonical specific implementation that has a reputation for breaking a lot of things.
It’s perfectly possible to isolate a steam install, NixOS does that by default to even get it running (on NixOS nothing is where any binary blob expects it to be). There was a very brief issue with experimental steam when they tightened up their own sandboxing and doing sandbox-in-sandbox broke stuff but that was fixed before release as Valve is, indeed, responsive, even if the distribution isn’t officially supported. But you gotta have some professionalism and have institutional continuity, they don’t want to deal with J. Random Hacker doing a one-off packaging job. Or distros trying to be smart and replace the steam runtime with their own library versions. Basically, assume that the whole thing runs directly on the kernel, make sure to have graphics drivers, and you’ll be fine running it as-is.
Snap is Canonical’s (developers of Ubuntu) attempt at their own containerized software package format, conceptually similar to Flatpak in some ways but differing in details of implementation. One major note is the back end is kept closed source so you cannot host your own Snap repo, which ruffles some feathers.
Apparently distributing Steam (Valve’s video game store/launcher) in Snap format is causing some problems.
Meh. As a KDE F38 user, this is a super boring release. Nothing really new for us to look forward to, except LibreOffice 7.6 (which you can get via Flatpak). I was hoping the new DNF 5 would make the cut, but guess it’s still not ready yet. :(
Guess will have to hold out my excitement until F40 for Plasma 6 and DNF 5 (hopefully).
omgubuntu.co.uk
Top