If you have a bunch of 3rd party Intel code, sure each of them will be translated once and stored on disk. But after that, the Intel code will not be in memory. Loading the translated binaries into memory will not be significantly larger than their Intel counter parts would have been.

I'm not really sure where your misunderstanding is, but you're clearly confused about something.

Keep an eye on the Mega65. A re-implementation of the C65 prototype that was never released. An FPGA core, HDMI output, and the capacity to mount disk images from an SD card. With their dev kits shipping now, it looks like they'll be ready for a production run soon(-ish).

(Submitted too soon) There's even an edit button on the documentation page that links directly to github.

With .net core, which is becoming .net 5, if the documentation is bad you can clone the source code and work out what it actually does. Then, if you are feeling charitable, clone the documentation and submit a pull request to fix it.

Or at least raise an issue against either repository pointing out the problem, hoping someone else will fix it.

An open communication channel with the developers makes a world of difference.

And here's a new battery research paper that promises 3x the storage...

I know it's always there. Sometimes I don't notice it, as if it isn't there. Sometimes I do notice it, but it doesn't bother me.

But it would sometimes make it difficult to sleep, giving me a headache. That doesn't happen anymore.

It sounds like this procedure doesn't make tinnitus go away, but may accelerate your ability to ignore it.

I've had tinnitus for decades. Usually I'm completely unaware of it. Like breathing or other bodily functions, I can focus on it and hear it. But even when it is noticeable in a quiet room, it's no longer annoying.

You clearly haven't been keeping up then. .NET Core is cross platform, and the version 5 release will see it become the only version of .NET. Version 5.0 release candidates are available now, though I expect there to be a few more iterations before it is production ready.

Sure, the ".NET Desktop Runtime", including the windows forms GUI assemblies, will remain Windows only. But .NET console applications, that avoid direct system calls, should just work on linux.

The windows desktop application is dying anyway. Many people seem to be building web apps instead. It seems like the .NET team are pushing further in this direction with Blazor. Running the .NET runtime in the browser via web assembly, with a HTML UI. (I'm not saying that's a good idea, just that this is where they are heading)

While we at it, can we please have; unicode filenames, filenames cannot start with a hyphen, shell filename globbing that always prefixes a folder (one of './', '../' or '/').

So some highways and parking lots. (but apart from that, what have the romans ever done for us).

And how many accidents have occurred while these features are enabled?

I would like to see each vehicle evaluated by the same criteria, based on the same miles driven. Though at least California is forcing companies to provide some data. Tesla isn't really participating.

Tesla don't appear to be solving the same problem. They certainly aren't providing any evidence that they can drive on anything other than highways.

This is a common problem with engineering. You only hear about the problems, not the successes. Particularly if that success doesn't seem to impact the bottom line. The squeaky wheel gets the grease.

Though I'm sure Youtube could quantify the ad revenue from people with captions turned on, and compare that to the support burden of spam etc. Obviously they don't believe the feature is worth the support cost.

Uber was under a lot of pressure to be seen catching up to google. They weren't ready for this.

And if you did look down at your phone for the same number of seconds, you should be charged.

But in this case, so should Uber for creating this obvious situation.