Yes, daily, as a virtual screen for my Macbook using a BLE mouse and keyboard paired to the Macbook not the AVP. Then I supplement the Mac with the occasional AVP side app using fingers and eye gaze control.

If only the AVP ran MacOS natively on the M2. Somewhat ironic that I have to park an M1 Macbook on a table next to my AVP, screen open so I can unlock it (requirement for the screen pairing).

I’m considering putting my Mac Studio into ‘never screen lock’ and then using a long range Logitech dongle for the wireless keyboard and mouse so I can use my AVP without an opened Macbook by my side all the time.

A big bonus for me was VisionOS 2 added lower latency screen mirroring (and I think foviated rendering of the mirrored screen). Prior to that I had to use a developer strap with a second usb cable to the Macbook to get no noticeable latency on the screen and cursor.

Strongly disagree. As a dev who’s been in the business since the days of the first gui apps and OSes, UI can be very straightforward, but we have designed modern systems such that they are immensely complex.

Styles and inheritance and asynchronicity have turned what could be a simple approach into an inscrutable problem.

Aren’t you one of developers of android?

That would explain a lot :)

Very dangerous wishful thinking.

Ui can only be as straightforward as a user wants it to be - if all user wants is pressing couple buttons to open couple windows - then yes, it is straightforward.

Asynchronicity is not a problem it is one of the many solutions to help alleviate the problem.

I took. my wife’s Model X out for a moderately complicated drive last night and was very pleasantly surprised by the new FSD behavior.

Very significantly improved over the last few updates.

Having submitted a number of “product breaking bug reports” through official channels while using a paid support incident, can confirm Kafkaesque and a multi year support process.

Oh, I can get a person to “respond” to a problem with a paid support incident. But the person responding is clearly hired only based on their ability to respond to an English email, once a week, with either, “thank you, I will forward that to our engineering team” or “thank you for your patience, our engineers are still looking into that issue.”

Severity, impact, paid support, none of that matters. Heck, it’s impossible to tell if it’s an actual person or just a sophisticated shell script.

Spoken like someone who hasn’t put a match to gasoline.

Having recently used gas to help start a wood slashings pile on fire, gasoline is very explosive and dangerous.

Diesel will burn in place when lit. Gasoline vaporizes when let out if its container in ‘room temperature’ conditions and creates a vapor fireball when it finds a nearby ignition source.

Never use gasoline as an ‘accelerant’ to start something else on fire —- it’s way too dangerous.

So Avalonia is built on top of Skia which is Google’s portable 2D rendering engine.

So in theory it is as cross platform capable as Chrome/Electron without all the overhead that html brings. Brilliant play, imho.

Now, as long as Apple doesn’t manufacture a reason to ban apps based upon it…

Skia is also used by Android, Flutter and Xamarin, among others.

Probably a much simpler answer. The programmers who work on a washing machine are probably inexperienced low wage disempowered help. And there’s an innocent rx/tx loop for a home grown notification system and noone on the team knows better or knows how to use a packet sniffer or perf analyzer.

Never attribute to malfeasance what incompetence can explain.

Put a packet sniffer on it. Bet it doesn’t use https, that costs extra for microcontrollers. Dollars to doughnuts it’s a teenager on a road trip.

Are we there yet? Are we there yet? Are we there yet?

This was my experience too. While it takes a good long while to get resolved, because my mistakes were accidental and I talked it through and followed the process, I was dealt with politely and given grace.

All in all a scary but good experience.

Thank you from someone begrudgingly paying thousands of Euros for IEC medical device standards pdfs!!!!

Windows NT was rock solid until Windows XP was released, but GPU performance was meh and Windows games generally didn't work well unless they were written to target NT. As I recall, there was one commercial graphical strategy game for NT at the time.

XP broke the subsystem isolation of NT in favor of enabling Windows non-NT types of drivers with higher levels of kernel/GPU efficiency due to less isolation. This also brought in the ability of the drivers to crash the kernel.

And that, my friends, was the end of rock solid Windows NT stability.

I was on the Windows team during the XP SP2 years. Stability was somewhat reachieved by an intense focus on defensive coding to detect rogue driver and the establishment of the WHQL, or Windows Hardware Quality Lab. WHQL was basically an investment in driver analysis tools and a moderately sized team inside MSFT who's sole job was to debug and fix other people's drivers.

It's not a good replacement for isolation though, and it requires sustained continuous effort by both MSFT and the windows hardware partners, which imho hasn't continued.