MS Flight sim started as a non MS flight sim on the Apple 2. A Sopwith Camel flying over a flat terrain with line art 3D. MS brought it ported it to the PC, and incrementally improved the graphics, planes and terrain over the years. Since it started in the 1970s, the online period of MS Flight sim is rather short compared to the offline-only period.

On steam, it is currently rated at "Overwhelmingly Negative". This is because you are forced to be online to play it and it takes an eternity to download the game.

All the features mentioned are things you can already do with an android tablet running a home assistant client. Put it in a nice frame on the wall with a hidden power supply and bingo you have something you can control all you house things on.

Bonus, it's all open source and you can add your own things if you know a bit of coding.

Yes. The 2 was missing.

979-8868801242

Yes. I was there a few months ago. The coffee was excellent, which is my primary priority.

This is the point where you find there is an instruction that does what you are trying to do and your hand crafted assembly was dumb.
I've added a couple of instructions to X86, so for those two instructions, I don't make that mistake. All the others are fair game.

But Húsavík has a Eurovision museum. So it wins. I'd live there.

Yep. I was there in the standards meeting when the feds turned up and gave a talk about the mandatory LA features we had to add. We all pointed out how this was stupid and would be exploited by everyone and anyone to spy on everyone and anyone including those feds demanding we add LA.

And here we are 20 years later.

Where I grew up in Wales, they were just plain ugly hexagonal poles of concrete with a light on top. No swan neck to be seen.

They were ugly as sin too.

The 8086 was a long time ago used microcode for different reasons. It had a limited transistor budget and microcode was an efficient way to implement lots of instructions. Obviously there were other options, and it wasn't long before transistor budgets increased to allow for microcode-less CPU architectures.
Today in chips with many more transistors, microcode affords the flexibility to respond to security issues and bugs and to provide support for all sorts of features (VM stuff, trapping, failover etc) without encumbering the underlying instruction logic with that stuff. There is a middle ground in transistor budget where microcode-less CPUs are common. They don't have the features and they do have an instruction set designed with that in mind. What we have seen with higher end ARMs is they are big and complex and so have bugs and the vendors can't work around the bugs because they don't have microcode.

My knowledge is about 3 months old now (the time since I retired from a large CPU company) and I'm looking forward to being more and more out of date over time.

RISC-V is a spec. A RISC-V CPU is an implementation of that spec and there is nothing stopping that implementation using "non free" microcode. In a large CPU, there are many good reasons to incorporate microcode and I expect to see RISC-V with microcode become common.

i'm still not paying the Adobe tax. AI art theft tools or not.

It's like an RF circulator but with audio.

My Juicebox is a first generation model. It is supposed to be internet connected but I did not let it connect. Then the company bricked all the connected ones with a crowdstrike style update. Fortunately mine never got the update because I kept it off the internet. So it sits happily on the wall, charging my EV when required.