assassinator42

Rumor is Samsung won't support Google's Linux Terminal (at least for their existing phones) since their Knox conflicts with the Android Virtualization Framework :-(.

Honestly I'd like to see Windows 11 running under this as well, but that seems incredibly unlikely.

For my 2016 Volt I need to run the defroster to be able to actually see out of the window though. And that takes around 4KW on average.

I can get less than half the range on cold days in the winter (65 MPGe) vs the maximum in the summer (140 MPGe)

Java and the .NET Framework had partial trust/capabilities mechanisms decades ago. No one really used them and they were deprecated/removed.

I took a bit of umbrage with LineageOS for this.

CyanogenMod required a CLA to assign them copyright to Cyanogen Inc, only for them to basically kill the project. They forked it as LineageOS only to still require a CLA.

This is a game; I don't think a debug configuration (with checks for things like this enabled) would run fast enough to be playable on contemporary hardware.

No you don't, MinGW(-w64) targets windows directly (with MinGW statically linked in). I've built a Windows->Linux cross-compiler that depends solely on DLLs built-in to Windows (kernel32.dll, MSVCRT.dll, and user32.dll).

Granted that was hundreds of hours, some patches (only 8 lines though), and probably a bit of masochism.

I did of course need MSYS2 command line utilities like make and bison to run the GCC configuration/make scripts. Although we use the mingw32 version of make along with the cross-compiler which also has no other dependencies (it uses cmd.exe as a shell if you don't have a bash.exe in your PATH).

I would assume targeting OpenXR would be much more productive? It's unfortunate that Apple insists on being so proprietary.

I've been confused by this, aren't these systems using ACPI instead of Device Tree? I know AWS ARM systems use ACPI.

The proliferation of Docker containers seems to go against that. Those really only work well since the kernel has a stable syscall ABI. So much so that you see Microsoft switching to a stable syscall ABI with Windows 11.

This is going to make it even more of a pain to do egress filtering on networks/systems we administer. I want to be able to allow list sites with dynamic IPs. The existing solutions for doing this by examining SNI are already often bypassable by forging the SNI (looking at you, AWS Network Firewall).

Ada has the bounds checking, but doesn't (AFAIK) have a safe way to deallocate dynamic memory. At least as of now, there is a proposal to add something like Rust in the future. It also has memory unsafe concepts like specifying an address for a variable.