jsheard

Those speeds on the Pro/Max are impressive though, more in line with Gen5 NVMe drives. Those have been available in desktops for some time but AFAIK the controllers are still much too hot and power hungry for laptops, so I think Apple's custom controller is actually the first to practically hit those speeds on mobile.

That's decently fast but not especially remarkable, most Gen4 NVMe drives can hit 6-7GB/sec.

However you can still do anything at https://html5zombo.com/

They haven't added or really changed anything since the acquisition AFAICT, it's just trucking along exactly as it was the day Zoom bought them out. Twitter account proofs were broken by the API changes years ago and nobody is at the wheel to fix or even just deprecate them.

https://github.com/keybase/keybase-issues/issues/4200

https://en.wikipedia.org/wiki/World_(blockchain)

Further down they also mention that the requests come from CFs ASN and are branded with CF-specific headers, so there's no attempt to be stealthy either, and it should be easy to block on your own terms if you want.

> 12.08% [of translators] say MTPE produces high-quality output.

> A significant portion (around 50%) of respondents do not offer discounts for MTPE work, arguing that post-editing can take as much time as traditional translation.

> Among those who do offer discounts, the most common range is between 10-30%.

And the consensus among professional translators is that MTPE only saves time if you're willing to accept a half-assed result. For them to edit MT up to the standard of manual translation takes just as much expertise and effort as translating it manually in the first place.

Not to say that easy piracy is necessarily a death sentence for a console, the DS succeeded in spite of ubiquitous and cheap flashcarts, but the Dreamcast shows it's not necessarily a path to success either. There are just more pertinent reasons for a system to sink or swim.

It is hard, but Microsoft came up with a hack to make it easier. MSVC (since 2019) annotates x86 binaries with metadata describing the codes actual memory ordering requirements, to inform emulators of when they need to be conservative or can safely YOLO ordering. Obviously that was intended to assist Microsoft's Prism emulator, but the open source FEX emulator figured out the encoding (which I believe is undocumented) and implemented the same trick on their end.

Emulators still have to do it the hard way when running older MSVC binaries of course, or ones compiled with Clang or GCC. Most commercial games are built with MSVC at least.

Kids these days are always saying "snaoƨd" and "foʀaṅr"

I think the key difference is that phone operating systems are designed around extremely aggressive memory management where any background process can be killed at any time. AFAIK macOS just isn't set up for that.