Hello, tone-policing genocide-defender and/or carnist 👋
Instead of being mad about words, maybe you should think about why the words bother you more than the injustice they describe.
Have a day!
Again: Google would not be doing this if there was no perceived benefit for them. If it was merely a matter of adding a scarier warning, then what purpose does the new “student/hobbyist” account type that restricts the number of devices your app can be installed on serve??
The headline is incomplete to an extent that it’s dishonest because it doesn’t reflect the reality of what Google is saying.
Google will only allow “experienced users” to “continue” sideloading with the new, draconian restrictions that Google will be the arbiter of. “Continue” implies that sideloading will continue as it is in its currently acceptable form. However, that is not the case. If it were, Google would not be changing anything at all because there would be no perceived benefit for them doing so.
So in a way, yes, the entire article is wrong, because it doesn’t adequately push back on the premise that it implies and instead uncritically parrots what Google would prefer people to believe, which is that people that want to sideload their apps and use third-party app stores like F-Droid will not be negatively impacted, which is not true.
It’s not FUD. The “install unknown apps” toggle already does what you’re describing. Whatever the intentionally vague blurbs from Google imply, whatever the new toggle ends up being will be worse.
And that doesn’t account for the need they’re creating for a “student/hobbyist” account that Google is creating. If you use such an account, your app can only be installed on a limited number of devices, which Google will control.
The “install unknown apps” toggle already does that. Whatever that vague blurb implies, whatever the new toggle ends up being will be worse.
And that doesn’t account for the need they’re creating for a “student/hobbyist” account that Google is creating. If you use such an account, your app can only be installed on a limited number of devices, which Google will control.
Yeah, this is garbage. Nobody should accept this. People need to keep fighting this because the “hobbyist account” bullshit still gives Google full control over what apps you can install by creating an arbitrary restriction that they can change on a whim.
Nothing short of leaving the process of installing apps from outside the Play Store exactly the same as it is now should be accepted.
The Verge is laundering Google’s Big Brother bullshit with their headline by making it sound like Google responded in an adequate manner, which is exactly what Google wants.
I’m replying to you from Asahi Linux on an Apple Silicon Macbook. The drivers are definitely there!
FEX emulation of x86 on ARM CPUs has made many x86 games playable on my Macbook.
I’m replying to you from Asahi Linux on an Apple Silicon Macbook. The drivers are definitely there!
FEX emulation of x86 on ARM CPUs has made many x86 games playable on my Macbook.
The Linux app is just the desktop app, which doesn’t have the functionality that the Android and iOS apps do. It only works when paired with an Android or iOS device, so you’d still be shackled to those ecosystems without proper support for a mobile Linux app.
Canonical does a lot of bad shit, but switching to uutils is not one of them. The “challenges” are expected because it’s going in a non-LTS release, which is basically meant to be a beta of the next LTS. And those challenges are being quickly addressed as they’re being surfaced. This is exactly the right way to introduce something new, IMO.
I don’t like the uutils pushover license license though :/
Because their sandboxing format subtly breaks so many applications (more than flatpak) and Canonical very nefariously co-opts your apt install <package> with a deb package that’s actually a stub to install the Snap version, so when your shit breaks, you can waste hours before you realize that they fucked your installation.
Beyond that, Snap cold start times (installations or updates) are slow as shit (yes, even with LZO compression), and since each snap application can update on its own, you’ll also encounter random times when your shit appears to “freeze” but what’s actually happening is Canonical is busy polluting your loopback devices to decompress their shittified version of your app.
Canonical, being demons, have Snapified things like GNOME, so even your desktop environment will be encumbered by that dogshit packaging format.
Do not use Ubuntu if you value your time and well-being.
I miss when Docker was putting out new features for containers instead of this shit.
Can we avoid calling taking action against valid moral objections “drama”? It only serves to make the people doing the right thing sound like they’re being immature, even when they’re obviously right.
Objecting to a fascist government’s influence over very powerful build infrastructure used around the world is the right thing to do.
This type of comment is indistinguishable from the low-tier, rage bait comments under every Phoronix article.
oniux might be exactly what you’re looking for.
It was still in early development when I played with it months ago, so I’m not sure if it’s ready for daily usage, but it’s from the Tor Project team themselves, so I imagine it will only keep getting better.
If this works out, it’s likely something that container engines would take advantage of as well. It may take more resources to do (we’ll have to see), but adding kernel isolation would make for a much stronger sandbox. Containers are just a collection of other isolation tools like this anyway.
gvisor already exists for environments like this, where the extra security at the cost of some performance is welcome. But having support for passing processes an isolated, hardened kernel from the primary running Linux kernel would probably make a lot of that performance gap disappear.
I’m also thinking it could do wonders for compatibility too, since you could bundle abandoware apps with an older kernel, or ship new apps that require features from the latest kernel to places that wouldn’t normally have those capabilities.
The --stream functionality looks very useful as well. Super cool!
One thing I really miss from Unity is the efficient use of the top bar doubling as a title bar for full screen windows. I wish modern DEs would do this.
Just here to add that, yes, Snaps are very broken. Do not use them if you value your time or well-being.
The annoying thing is that Canonical dishonestly co-opts your apt invocations for snap installations, so you’re likely to waste hours of your life trying to figure out why the thing you installed doesn’t work or takes forever to launch randomly. And they keep Snapifying more of their distro, so even things like GNOME packages are only available as Snaps.
Zig isn’t memory safe by default. Safety needs to be opted-in to, which isn’t free.
And merely recompiling C projects with the (very good) Zig toolchain wouldn’t add any form of memory safety whatsoever as far as I’m aware. You can get some safety checks that way, but you still have to fix the buggy C code manually, which is a nontrivial task in best-case scenarios.