my123

> Note that 64-bit Windows does not support running 16-bit Windows-based applications. The primary reason is that handles have 32 significant bits on 64-bit Windows. Therefore, handles cannot be truncated and passed to 16-bit applications without loss of data. Attempts to launch 16-bit applications fail with the following error: ERROR_BAD_EXE_FORMAT.

winevdm on Windows eschews that level of integration, but perhaps MS should have shipped WoW16 with limitations instead of nothing.

Comment · 9 days ago

An app can opt-in to it in the manifest without needing that global system override.

Comment · 13 days ago

it's one of the ABI differences between x86 and arm. on arm, char is an unsigned char

Comment · 13 days ago

OpenGL on Apple GPUs is implemented on top of Metal with some private extensions to be closer to OpenGL behaviour. Making things work performantly on top of regular Metal is quite a bit harder.

Comment · 16 days ago

The CEF update was baking in the public beta channel for around the last 6 weeks.

Epic could have benchmarked their beta client against the Steam beta client which would have shown this.

Comment · 16 days ago

It was a planned update since long before. Just a coincidence in timelines.

Comment · 17 days ago

Things are a lot worse than Spotlight on a number of platforms...

Comment · 17 days ago

Using American technology licensed by the Dutch, the US is able to do this because a lot of the EUV research was financed by the DoE and licensed to ASML.

Comment · 19 days ago

> to make macOS a closed system like iOS

The reason why that won't happen (but more and more warning prompts all the time because of this modern world...) is because macOS is a self-hosted platform.

Apple _needs_ macOS as an unlocked OS at the very least as a development platform to develop their operating systems on. Not having the self-hosting requirements allows to tighten the security model a lot.

Notably, with a Unix terminal, a huge problem for sandboxing is how to determine permissions granularly, whereas a UI flow has significantly better answers to that.

Comment · 1 month ago

Not an easily feasible option notably because the firmware ACPI tables are in part stubs - but work on hybrid ACPI/DT instead is possible.

One of the reasons is that Qualcomm uses supplemental ACPI tables (think device tree overlays) shipped inside of the driver packages. Look at the .bin in plenty of the drivers carefully and you'll see that they're supplemental ACPI tables.

Windows doesn't have such a notion and it's implemented via having an ACPI table loader statically linked in to individual drivers.

_On top_ of that, Qualcomm uses PEP to intercept plenty of ACPI functions and implement them in native code instead.

Comment · 1 month ago

It's worth more with business practices that the current owner wouldn't be willing to do.

Comment · 1 month ago

Monaka-X will include SME2 but it didn't make the cut for first-gen Monaka