Another big thing that doesn't get covered by big O analysis is the potential for parallelization and multi threading, because the difference created by multi threading only amounts to one of those dropped coefficients.
And yet, especially for the workloads being run on a server with 32-128 cores, being able to run algorithms in parallel will make a huge difference to performance.
The least expensive MacBook is still $1000, closer to $1500 if you spec it with reasonable storage/ram. It really isn't that much of a stretch to add $100-300 for a 1080/1440p monitor or two at a desk.
A lot of android apps are built using Java/Kotlin, so you don't actually need to care about architecture since the JVM supports both x86_64 and arm64.
There are exceptions to this though, since some apps need to run native code. Those apps would need some sort of emulation/translation layer for the arm instructions.
AFAIK registrations get approved manually on this instance so I doubt it'd be bots, the admin isn't really active so I figured the instance was dying but I didn't realize it was that dead.
Seconding Breezy, the app is way better than my phone's (OnePlus 9p) default weather app. They also have a wide variety of widgets, including some with Material You theming for Android 13+.
They're all tone indicators, since you can't communicate voice tone over text.
/s stands for sarcasm, sometimes /srs is used for serious, I'm not too sure what the others stand for but those are the most frequently used from what I've seen
The DS did have an IR sensor but (I'm pretty sure, don't quote me too hard here) a majority of the local communication was using either wifi or a proprietary wireless connection using the wifi antenna/chip.
I specifically remember Pokemon Black/White having an IR quick-trade option where you had to put 2 DS's back-to-back and being really confused about it because it seemed useless since it took so long to actually work.
Are there really only 300 people here? Surely that data is wrong?
I agree with this mostly, but at the same time more powerful hardware lets the devs experiment with more advanced mechanics. For example, ToTK runs pretty hard into switch limitations with its impressive physics. If Nintendo wanted to take that engine even further, they'd likely need a hardware upgrade.
Additionally, more powerful hardware starts putting more demanding mechanics into the realm of possibility for an indie dev team that has neither the time nor the resources to optimize their games at the same level as a big studio.
I think blocking downvotes is an option built into Lemmy servers that can be communicated through the API. I know there are a decent amount of instances that don't federate downvotes because of toxicity concerns.
In the grand scheme of things the difference between C, C++, and Python isn't meaningful when operating over a network (edit: for a single-user system). It's very likely that the difference for thread OP is just caused by weaker connections to specific repos.
We're talking about a package manager, not a game, network server, etc. On a basic level the package manager only needs to download files from a network and install them (OS syscalls for reading/writing files, these are exposed C functions or assembly routines), or delegate to a specific package's build setup (which will also likely be written in a compiled language)
Spoken like someone who's never played a Zelda game. That being said, probably just play it on an emulator unless you like the portability aspect
Edit: But seriously, Nintendo is one of the only publishers that hasn't ruined their games with live service micro transactions and battle passes, and one of the only publishers that hasn't ruined their long standing IPs yet (Pokémon excluded, but that technically isn't owned completely by Nintendo). I don't exactly like Nintendo as a company but I have to respect that they haven't been cash grabbing in the same way other publishers have.