They probably fixed all the bugs they considered essential, and the rest is just nice to have fixes that can be moved to the next cycle if necessary (and they still have a week to work on them before release, although they might be careful not to introduce severe bugs now).

The general idea with this approach is that it doesn’t make sense to block a release on a few bugs worked on by only a subset of available developers and having the rest idle - the project can be finished faster by moving the remaining tasks over to the next release and accepting the bugs in the meantime.

Not familiar with the API, and I’m not entirely sure if it’s not just a bug in Eternity (fork of Infinity), but lemmy.one doesn’t have downvotes and I don’t get the option to downvote anywhere.

If you don’t sign into a Google account, you will never arm this mechanism at all.

The comment you replied to is a direct reply to the comment you linked - I don’t think it was intentional, but if it was, then I’d like to say it’s not a very helpful reply as OP already read it.

someone just plain lying about what OS they’re using in order to break fingerprinting.

The idea with avoiding fingerprinting is to look like whatever the biggest group of users looks like, because that’s who you share the fingerprint with. If you use an uncommon value for something, you make fingerprinting easier.

That’s one of the reasons why for example Vivaldi on Linux sets its user agent to match the latest version Chrome on Windows.

That really depends on the technology used. For example, all modern Ethernet standards (which includes both copper and fiber optic) are full duplex, meaning they can provide the full bandwidth in both directions at once. So a gigabit Ethernet link can do a gigabit in one direction AND a gigabit in the other direction at the same time (but not two gigabits in one direction).

Salt from the seawater

In my very limited experience with my 5400rpm SMR WD disk, it’s perfectly capable of writing at over 100 MB/s until its cache runs out, then it pretty much dies until it has time to properly write the data, rinse and repeat.

40 MB/s sustained is weird (but maybe it’s just a different firmware? I think my disk was able to actually sustain 60 MB/s for a few hours when I limited the write speed, 40 could be a conservative setting that doesn’t even slowly fill the cache)

Sounds like most of that would be handled by the kernel with non-Deck-specific modules - it won’t forget to notify the userspace that a device has disappeared just because it was in sleep mode at the time it was physically disconnected.

The only problems I ever had with sleep on Linux were all inability to wake up some part of the motherboard or the GPU because of crappy firmware, never with connecting/disconnecting external stuff.

Fair enough. I misunderstood, my bad.

Then what’s the meaning of this whole part?

On non-corpo linux syslog can be disabled if you want, though I’d prefer to just symlink/mount /var/log to a memory filesystem instead.

Is it just a random tidbit that could be replaced with a blueberry muffin recipe without any change of meaning of the whole comment? Because it sure won’t help OP at all with their Arch-specific question, so it’s either that, or it provides contrast to the “corpo Linux”, which is how I interpreted it.

And here’s the remaining part of your comment I left out, just to make sure people won’t lose the context between two three sentence long comments (for those without any attention span, it comes before the previous quoted part):

If you’re on arch you use redhat’s garbage.

On non-corpo linux syslog can be disabled

systemctl disable --now systemd-journald

I’d prefer to just symlink/mount /var/log to a memory filesystem instead

Set Storage=volatile in /etc/systemd/journald.conf

Your mileage may vary - your experience might be different for one reason or another

The data collection can just as easily be done by the game itself, the launcher doesn’t have any special privileges

How is it open source?

How is it not? Open source doesn’t mean you have to accept other people’s code. And it is perfectly valid to only dump code for every release, even some GNU projects (like GCC) used to work that way. Hell, there’s even a book about the two different approaches in open source.

So whatever benefit you were hoping to get from Nvidia’s kernel modules being open source probably is not there.

It allowed the actual in-tree nouveau kernel module to take the code for interacting with the GSP firmware to allow changing GPU clock speed - in other words no more being stuck on the lowest possible frequency like with the GTX 10 series cards. Seems like a pretty decent benefit to me.

I know people say that you don’t NEED an SD card if you buy the most expensive version and rely heavily on cloud services but it’s definitely an intentionally worse customer experience.

Honestly, this depends entirely on the user. My previous phone had 64 GB internal storage and an SD card slot, but I never felt any reason to use it - all I need is enough storage to hold the photos I take until I get home and copy them to a hard disk (which then periodically gets backed up to another hard disk stored at a relative’s house). Then I can delete most photos and videos and keep only a few that I think I might want to share.

I’m not saying this is a workflow that everyone would find acceptable, just showing that different people can have vastly different needs. I personally definitely don’t need an SD card if I have 20 GB+ available for my photos, and that doesn’t seem to be a problem with 128 GB being the baseline for current Pixels.

Of course that doesn’t mean I’m going to stop ragging on Google for taking away features with obvious intention of creating problems for a portion of the userbase and selling the solution. There’s no reason Pixels can’t have an SD card slot at their current price.

Now it feels like I’m limited to Samsung or Google if I want a flagship SoC…

Google’s Tensor is definitely not a flagship SoC (Tensor 5 is rumored to change that, but its launch is still far in the future and there’s no guarantee it actually lives up to these rumors), so it seems like deciding on the vendor should be pretty easy if you don’t mind Samsung’s OneUI

By taking away the MicroSD slot to force users towards expensive cloud storage?

No no no, that’s what the crappy modem is for

Vista’s problem was just the terrible third party drivers and the fact that it was preinstalled on machines it had no business running on. 7 didn’t improve much on it (except fixing the UAC prompt so that it no longer made you feel like you’re using Linux with misconfigured sudo timeout), but it had the benefit of already having working drivers from Vista and proper hardware capable of running Vista/7.

Zig didn’t come to my mind when I was writing my comment and I agree that it’s probably a decent option (the only issue I can think of is its somewhat small community, but that’s not a technical issue with the language).

My argument against Go and Java is garbage collection - even if Java’s infamous GC pause can apparently be worked around with a specialized JVM, I’m pretty sure it still comes at the cost of higher memory usage and wasted CPU cycles compared to some kind of reference counting or Rust’s ownership mechanism (not sure about the proper term for that). And higher memory usage is definitely not something I want to see in my browser, they’re hungry enough as is.