noderat

No, if you read the blog post on Microsoft's site it goes into more detail:

This is the real and full D3D12 API, no imitations, pretender or reimplementation here… this is the real deal. libd3d12.so is compiled from the same source code as d3d12.dll on Windows but for a Linux target. It offers the same level of functionality and performance (minus virtualization overhead).

Amiga from Atari?

Blast from the past for sure. MZX, TurboPascal and mIRC scripting were some of the first things that got really into development after migrating from my brother's hand-me-down C64 and later an Amiga 600.

I really wish the documentation for things like DI, IOptions and ILogger were moved out of the ASP.NET documentation. Trying to decipher from the documentation how to use these in a non-ASP.NET project is needlessly complicated.

This is the problem with this new wave of devices that only work when connected to the manufacturer's cloud service. There needs to be more focus on devices and software that allow you to run completely independently of the manufacturer's servers. The Home Assistant project has been a blessing in this area, but many devices either lack support or must have custom firmware to work in an "offline" mode.

I've been exclusively using Linux/*BSD (Slackware/Gentoo/Arch) for personal use since upgrading from my K6-2 500 to an AMD Barton 2600+ because finding, installing and managing "trustworthy" software is easier.

Linux has hardware compatibility challenges and software with bugs, but so does Windows. I don't, however, have to search through monstrosities like Download.com. I don't have to figure out what software may have a new release that is important to me. Critical dependencies are handled automatically. Every distribution may handle these in slightly different ways but these basics hold true.

Every time I've had to use Windows I've spent an enormous amount of time searching for and installing things. Once installed I then discover the software has changed to a limited free trial or some other nonsense that ends in another search, install and disappointment loop.

It's tools that have shown up in the last few years like scoop that have made dealing with Windows at least somewhat tolerable.

There is no documented API access for Google Domains.

I have owned since launch day a Nexus 1, Nexus 4, 2x Nexus 6, 2x Nexus 7 and Pixel 2 XL and they are all currently still functional well past their warranty. (The Nexus 1 was replaced by Assurion for water damage with a refurbished device @1.5yrs but replacement is still running.) In fact my Nexus 4 is still in use every day as an APRS GPS receiver/data logger, and one of the Nexus 6s is now in use by a co-worker as a OBD2 data logger/HUD.

I've avoided Samsung devices (including Galaxy Nexus/Nexus S) because the girlfriend has had the last 4 Samsung devices fail or become completely usable right at the end of the warranty (+/- 2mo) running completely stock. For those that became completely unusable it was usually pitiful battery life, the others became too slow to function on stock roms that I suspect they failed due to internal storage wear. Not even custom roms could save them.

I keep my devices a long time, and frequently repurpose them after they are no longer my primary device. Non-Samsung "Pixus" problems are overblown, except Nexus 6 AMOLED burn-in which is annoying but didn't present itself until it was used daily as a HUD.

They already have a 'black box' which contains their logs. This is how they have been able to investigate the previous reported crashes.