Thanks for the explanation! So it sounds like the emulator is detecting the error 'out of band' with the emulated execution flow, and choosing to throw an error message rather than letting the execution continue. If it didn't catch the error, it sounds like it would glitch out in much the same way as the real GameBoy would. Is that right?
That's right. This sort of thing is more likely to indicate a discrepancy between the emulator and the real hardware, than actual game behaviour, so emulator developers choose to treat it like a crash. Some emulators have "continue anyway" buttons and some don't.
No but with the raspberry you're not there without a power supply, case, cooling and storage.
Add them up and a Quad-Core N100 becomes equivalent. Here they're on Amazon for 180€ with 16GB ram and 512 GB storage. And cheaper options with less storage and ram (usually coupled with the sightly slower N95 chip)
It's not a pi and if you want to integrate it into electronics a pi is much better but for the "small mini server" usecase I don't see the benefit of going for a pi anymore.
The typical modern gaming PC uses a lot more power than the original xbox. Yes maybe it's more efficient because it's doing "more", but in the end it's one person playing a game.
Depending on what you are patching, it will invalidate a great part of the cache, and you will be looking at very long build times for everything in your system.
If that dependency is deep in your dep tree and is statically linked somewhere than there is no way preventing that.
If it’s only dynamic linking than yeah, it might happen that you need a huge recompile (but that is not that big of a problem nowadays in my experience - gentoo used to compile way longer in my subjective experience for example). Also note: nix will soon get content-based hashing which may solve this problem.
I have a step in my fashion work where I pause and consider what the colors I’m selecting will look and feel like to a normal person. Converting back and forth between [optimistic-seaglass-springtime] and “teal” isn’t very accurate, but I’m certainly accustomed to it. I’m going to try this technique soon now that I know about it; as I’m already color sensitive to pitch, I suspect the value will be in training that sensitivity rather than memorizing their hues.
Is it possible to fall back to a jpeg if the browser does not support js, wasm, or web workers? With a <picture> element, maybe?
I did some tests on my own server and found that for some reason it's quite fast when running on https, but super slow on insecure http. Not sure why that is, maybe the browser disallows something that's important here for insecure connections.
https://cosarara.me/misc/jxljs/ in my test, it will simply fall back to jpeg, even if the jxl.js library is loaded (scroll down to Image with fallback).
This is because JXL.js doesn't support `<picture>` tags - there is no rationale for WASM-decoding JXL when you can provide a fallback in natively-decoded JPEG/PNG/WebP.
The rationale would be that it might be more efficient to WASM-decode JXL than to download a JPEG, especially in pages with lots of images, but I would want a fallback if the browser does not support WASM.
And I think that, sadly, it's not even a full solution, because linux can manage to get thrashing even without swap. It pages in and out things like memory mapped files or the content of executables of stopped processes. See for instance:
https://serverfault.com/questions/898388/how-to-prevent-kern...
I don't agree with the reasoning presented.
It takes the estimate for the amount of energy that it takes to run the internet infrastructure and clients (141GW * 8765h in a year = 1235865 GWh), divides it by the amount of data transferred yearly (241 billion GB) and gets to 5.12kWh/GB.
You might argue that if people download more data, more equipment needs to run to enable it, but really all this energy consumption is happening regardless of my PC being idle or saturating its fiber pipes with torrents. If your website weights 14kb, all this same equipment needs to be on for my PC to load it.
The website usage on the client side is more to do with resource usage. Unnecessary usage of Javascript is often what makes websites laggy.
You computer will normally down-clock (you can turn this off in the bios) when under lighter loads.The difference between a JS-free webpage and a bloated web page that uses multiple JavaScript with extra Javascript for ads and tracking could be around 10W/H to 40W/H on Desktops.
Maybe, or maybe the new equipment is much more efficient than the one it's replacing. It sounds true, but you can't really tell if it is or not, and really my annoyance is in saying it costs any estimated amount of energy, or carbon, to transfer 1GB of data. It does not, the transfer itself is basically cost-less. What costs money is running the infrastructure that makes it possible, and that's much harder to measure.
You can use the bx instruction to jump to any address stored in a register.
> Additionally, what would happen if one of TheZZAZZGlitch's incorrectly reconstructed ROMs was run on a real GameBoy?
It would crash, and eventually start playing the ROM on the speaker, the whole point of the video :)