I'm not aware of any cool homebrew, but there is a certain level of cool being able to compile the code for some N64 games using the original IDO compiler on original hardware. You can even compile one of the many decompiled games like Super Mario 64, Banjo Kazooie and more that all will produce the exact binary shipped on the cartridge byte for byte, all from reverse engineered work to create byte matching equivalent C code.
In Canada there's been a big problem with stolen cars lately. Mostly trucks, and other high value vehicles though. Selling them locally isn't feasible, but there's a criminal organization that's gotten very good at getting them on container ships and out to countries that don't care if the vehicles are stolen. So even with tracking, there's nothing people can do. Stopping it at the port is the obvious fix, but somehow that's not what is being done. Probably bribery to look the other way.
Same thing in Australia - some gang was busted recently for stealing mid-range four wheel drives, packing them in shipping containers with partially dismantled cars (I guess so that a cursory inspection would just show "car parts" rather than a single nice looking car) and then shipping them around the world (I guess an overseas buyer isn't checking if a car with this VIN has been stolen on the other side of the world).
There isn't enough detail for me to know how serious is was in regards to stores not being able to accept payments, but a date of this blog being 2010, and it being written about a time when every megabyte of filesize matters makes me think it was possibly much earlier, like maybe 2001-2005. If that's the case, maybe not being able to process cards wasn't as big of a deal as it would be today because you could likely assume most if not all customers could pay with cash if card payments were down.
This is very wrong. Ghidra might decompile to some C code, but this is a completely different, and very high bar. This is 100% matching C code that compiles to the exact binary the game shipped with. This means it's able to be modified, tweaked and upgraded. Ghidra is helpful to do some research, but it won't compile.
I might be misremembering, but I seem to remember most games of that era were 540p scaled to 1080p. 720p would have been an upgrade. But your point still stands.
For many people yes, because that 20k isn't being added to the mortgage, so it isn't easily financed over a long period of time with low interest. These days, many people are stretched to meet the minimum down payment and won't have 20k extra to throw at a problem like this.
Redraw facilities are available in most countries? Refinancing etc? Genuinely curious.
For example (in Australia), my mate recently spent $40k, drawn out of his mortgage on solar panels, battery, double glaze windows, heat pump heating and cooling, gas stove to induction, gas hot water to heat pump and is currently investigating drawing more to upgrade roof insulation.
How can you refinance when you just bought the house? There is no equity for you to tap into, and if there was, you now even have a highly monthly payment.
Housing prices have to decrease first if you want people to be able make these decisions. That means we need a deflationary economy through increased production, so more people can be able to afford the enhanced productivity.
Those projects from the ship of harkinian are not recomp. Those are based on completed decompilation projects. So they're not translating the mips assembly to an unreadable C being recompiled. They're true ports from as close to the real source code as you can get.
How about adding information about IDO, like the static recompilation project being used in N64 game decompilation projects? It enables compiling code in a linux environment and having it match 1:1 as if it were run by the original compiler. There's even significant progress in decompiling the entire codebase as well.
On a related topic. I have a really weird problem in my house where I'm about 20 feet from my TV trying to use my PS5 DualSense connected to a Google TV device connected behind the TV. It uses Bluetooth, which is also 2.4GHz, and the issue I'm having is that the dongle behind the TV is really impacting my controller connection and making playing games over PS Remote Play completely impossible. I even have the GTV device hard wired with an Ethernet adapter, as is my PS5. This can't really be a range limitation can it?
(Obligatory HN pedantry: arguably unrelated, but now I'll try to help anyway because this is quite common.)
Bluetooth is pretty low power, but without the TV in the way, that range should be no problem at all. Problem is that a lot can block it physically and drown it out in RF noise.
Most TV's probably have a thin, but solid aluminum plate in them for structure that could indeed block BLE and be causing the issue. Ironically, this is one RF case where metal studs would actually be helpful.
For comparison, I fly a paramotor and use Sena Bluetooth mesh for comms, and just our heads at any distance are enough to block it if we're on the wrong side of each other. Motorcyclists on the other hand don't often have this issue since there's other vehicles and stuff to bounce their signals around.
What might help if that's the issue is something reflective like foil mounted somewhere that can see both the controller and the GTV device. I'd also try to make the reflector slightly/roughly parabolic-ish (kinda shallow as to not make aiming difficult) pointed at the GTV device. You can hide the reflector behind and/or point it through anything RF transparent like wood or plastic.
Another possibility is other 2.4ghz noise— You could try turning down 2.4ghz transmit power on your AP as a possible quick fix. Of course if you haven't, make sure anything that can be on 5ghz, is.
Edit: Note that a reflector will also reflect noise sources at the GTV device.
I've also had issues with poorly shielded HDMI interfering with 2.4ghz in close proximity, so even just jostling things around behind the TV a little or using your best shielded HDMI cables there could help some.
Debugging RF can be tricky and frustrating, but I hope one of these tips helps either you or maybe a passer-by one day. :)
