Of course Intel has been designing and selling GPUs for years, I guess Lip-Bu means they're going to start manufacturing them as well? Or they're going to be data-center focused now?
Since he was touting that they recently hired a well-known GPU architect, it seems unlikely that this is merely about them using their own fabs for discrete GPUs instead of having integrated GPUs being the only ones they fab themselves. Some kind of shift in product strategy or reboot of their GPU architecture development seems more likely, if there's anything of substance underlying the news at all.
But this news is somehow even less comprehensible and believable than usual for Intel, whose announcements about their future plans have a tenuous connection to reality on a good day.
Various anticheat/DRM schemes actually do direct syscalls on Windows, so Proton has patches that use seccomp to trap them and jump to the intended Nt* syscall. There was actually a feature added to the Linux kernel a few years ago (syscall user dispatch) so that Wine could stop using seccomp for this, but Wine is still not using it.
Upstream Wine also supports direct syscalls on x86_64 macOS. macOS syscall numbers have a high bit set, so Windows syscall numbers (0 to ~300) are invalid macOS syscalls, that triggers SIGSYS, and then Wine jumps to the Nt* syscall.
How are they explaining away the fact that the Japanese male astronaut asked for a consult with the flight surgeon on the public loop (a video which NASA has since removed from YouTube)?
Everyone on the ISS needs to have a seat reserved for them in a docked spacecraft, in case they need to evacuate the station quickly (or for a medical issue like this). You can’t bring back just one person from a 4-person crew; the other 3 would have no way to leave.
No. On NT, kernel ABI isn't defined by the syscalls but NTDLL. Win32 and all other APIs are wrappers on top of NTDLL, not syscalls. Syscalls are how NTDLL implements kernel calls behind the scenes, it's an implementation detail. Original point of the thread was about Win32, UWP and other APIs that build a new layer on top of NTDLL.
The stapled ticket is optional beyond notarization itself. If you notarize but don’t staple the ticket, users may need an internet connection to check the notarization status.
Apple makes excellent hardware (laptop, phone, mini...) to the point I'm willing to pay more for it, but I would prefer a lot to customize my SW. And so I avoid their hardware.
reply