DarthYoshiBoy

Very true. Perhaps my statement which continued on beyond what you quoted didn't make it clear, but I did point out what you said: "You've got brakes, but you're without any of the assistance that the car normally provides" as well as stating later that you've got "naught but your unaided foot on the brake peddle" both of which were intended to say that it's pretty hard to brake in most cars these days without power brakes.

I don't know how the Cybertruck breaks down on the easy <-> difficult manual braking spectrum, but I imagine that given the high gross vehicle weight and large wheels, it probably steers more towards the difficult end of the spectrum than the easy. Such a dumpster fire of a vehicle.

One has already been pulled, though seemingly for unrelated copyright issues?

That said, I'm surprised that things have gotten to this point, I suppose time will tell once the property holders get involved how committed Apple is to this whole change, there's still a lot of room to interpret the clause about conforming to all laws for the content that is being run in the app.

Given that I didn't think ANY emulators would make it into the Appstore, I'm going to retract my position. However, I think that we're still in the "Fuck around" stage of things and there may yet be some "Find out" to come.

It is a ridiculously proven and safe technology.

In Planes, where there are 3 or more levels of redundant power and hydraulic systems with an ability to fail down to a limited mechanical operation mode if all the other backup systems fail. It's proven because they designed it with a stupid level of failsafes.

There's no redundant power in the Tesla Drive By Wire system, if the power is cut, you lose the ability to steer. You've got brakes, but you're without any of the assistance that the car normally provides. It's so fucking stupid I can't believe it's allowed on the road. If anything goes wrong that cuts power while you're in motion, you're suddenly captive in 3.3 tons of stainless steel without crumple zones, without the ability to steer, with naught but your unaided foot on the brake peddle to determine your outcome. It's nothing like the multiple layers of failures you'd have to endure to find yourself in trouble in a plane both for the power and the hydraulics.

Bluetooth headphones are not modernity, they should of course be an option, but increasingly they are the only game in town. Wired is still king for loads of things, not the least of which is reliability.

You wanna know how many times my wired Sennheiser's have been unable to put music in my ear holes? Never. They always work. Care to guess how many wireless headphones have been able to provide sound every time I've wanted it without delay or failure? None. I've owned more than 2 dozen wireless this, that, and the other, headphones & earbuds, and none of them have been even a shadow of the reliability offered by my old wired headphones. Which is to say nothing of the fact that the wired experience usually sounds better (Still don't think you can get any comfortable phat 600ohm monster cans that don't have a wire) and has no issues with making sound when you're in a space that is saturating the 2.4Ghz band (my Costco is usually so full of idiots on Bluetooth that you can't get a reliable experience for anything from any wireless audio device.)

You seem to think it's "backwards rhetoric" to want a feature that will never be offered in a wireless setup, and that's just fucked man. There are a wealth of reasons why wireless does not fully replace wired. It's why anything that doesn't have to move generally gets a fixed connection, it's just more reliable and often more efficient. That's not backwards, it's just a priority that you don't value above others. If landlines or floppy disks offered any advantages over anything else they'd still be around today (and arguably they are in some limited niches,) but the replacements for those technologies have had no downsides against their replacements while wireless tech still has some significant downsides (again, maybe you don't weight the pros and cons the same, so this may not apply to you) against the technology they are meant to replace, and will likely never see 100% capture of their role as a result.

TL;DR: Stop trying to frame this as some sort of crusade against the future, there are legit cases where wired is just better than wireless.

Agree to disagree.

Dolphin requires JIT compilation and that is still verboten under these new guidelines.

Further, the rule change says that these apps are allowed to "Download" ROMs, it doesn't say that they can just play anything they want, it in fact says that they have to provide an index of everything their software might run and where it is downloaded from. The rules are not going to allow emulators as we know and love them. It says specifically that the software offered under the guidelines must be offered via In App Purchases, so in all,

A) Emulators can exist

B) They can download ROMs

C) You have to comply with all applicable laws while you offer an emulator that allows people to download ROMs ಠ_ಠ

D) "Software offered in apps under this rule must: use in-app purchase in order to offer digital goods or services to end users."

Which in whole means that they've allowed (for example) Sega to offer an Emulator app that will run ROMs of games that Sega owns, but they have to sell the ROMs to you individually via IAPs.

Feel free to read their guidelines at https://developer.apple.com/app-store/review/guidelines/#third-party-software, because there isn't any way in my reading to interpret those rules as allowing something like Higan to exist on the app store, the new rules are such a narrow carve out that it's hard to imagine that anyone is able to provide an emulator for iOS any time soon. They've opened a door that basically nobody could walk through and the people who could walk through it wouldn't need to because they could just distribute the ROMs with the emulator to begin with, it's business as usual for Apple.

It depends. In the early days of the Android ROM scene, Twitter was the best place for news. Cyanogen and all the crews basically announced their new releases exclusively on Twitter. There has been a similar vibe for other scenes over the years as well. Discord is largely taking over that space these days, but I miss the simplicity of following one or two people whose updates I cared about a bunch over the new reality where I'm in 30 Discords and they're all chock full of notifications for endless nonsense I care nothing about.

They did

My 2016 Nissan Leaf is 4400lbs, which is more than my larger (but still not that big) 2016 Mazda CX-5 at ~3500lbs. Both manage to fit my family of 5, but the Leaf is far less accommodating and it weighs a good deal more. Small EVs are still pretty substantial. A Kia EV6 which is roughly the same size as my CX-5 weighs 5500lbs. You add a lot to a vehicle when you add an EV battery.

As I heard it, the fact that they were heavily implying (and often delivering) versions of the emulator that worked with as yet unreleased games for Patreon backers exclusively while the 'open to everyone' version was not as compatible, is what probably did them in.

It would have been pretty hard for them to argue that their emulator was for legal means when they were constantly telling people to pay up for the Patreon to get access to builds optimized for games that hadn't yet gone on sale. If they had just kept the public in parity with the Patreon and just coincidentally had performance uplifts on upcoming games before they dropped, they'd probably have been fine. As it is, they painted a pretty compelling picture that they were "pay for piracy" and that's where the lawyers probably told them to take a deal and get out.

I've dabbled with Linux on Mac hardware a couple of times and I've got to say that Linux DEs generally hew closer to Windows conventions than Mac ones and I found using the Mac keyboard with Linux to be a dreadful experience without the fact that the chiclet keyboards are the worst shit I've ever put my fingers on.

I very quickly snagged a standard mechanical qwerty 104 key with brown switches and cursed every moment that I had to use that abominable keyboard built into the stupid MacBook. Apple seems determined to do things different for the sake of different as much as they possibly can and trying to adapt all their nonsense to the Win/Lin way of doing things made my life worse in numerous ways (most DEs have great remapping for keys and such, but it gets messy fast if you've got apps from different paradigms.)

I'd very much recommend against going out of your way to get a Mac keyboard for using Linux unless you enjoy fighting against things. But hey, if that's your kink, then a Mac keyboard with Linux would be my recommended way to go.

The original Game Boy Color has a screen that is only 160 pixels x 144 pixels at a 6bit color depth. That color depth means it can keep track of 6bits of color information for each pixel (technically the GBC screen CAN display 15bits of color information, but it's limited in software to 6bits absent certain tradeoffs.)

This isn't exactly how it all works, but I'm going to just do some quick and dirty math really quickly that sorta simply illustrates how this works. To adequately display a 60fps image on the GBC display at the 6bit color depth of the screen, we'd need to be able to process 23,040 pixels (each with 6 bits of color data) every 60th of a second. To simplify further, there's 138,240 bits of data to process every 16.6ms just to "drive" the display, or put another way 138,240 bits of data to process to ensure that the display gets all the information it needs to build a complete picture every 60th of a second.

So for a 1600x1440 display, you're looking at 2,304,000 pixels, and the Analogue Pocket has a 16bit color depth, so you're going to need to be able to process 36,864,000 bits of data every 16.6ms to "drive" that display.

Getting a GPU/CPU/FPGA that can handle 138,240 bits of data every 16.6ms is a fairly easy task these days. Getting a GPU/CPU/FPGA that can handle 36,864,000 bits of data every 16.6ms is also a pretty easy undertaking these days, but it's much more power intensive and it's going to cost a bunch more. All of which is beside the shader calculations the Pocket adds in to do things like emulating the pixel fade of old LCDs or other effects that further emulate the properties of the original displays which requires further processing.

The tradeoff is that you can build a more detailed image with all those extra pixels, but you're going to pay for it both in electrical power spent, heat generated, and costs sunk.