You don't have time to sit around without anyone noticing in retail unless there's not a business case, in which case there's no customers. That business has (at least) two problems.

If there's work to be done, it's immediately noticeable when you aren't doing it, to anyone who understands the job. No one else is qualified to manage people doing it.

Those jobs hardly paid anything to begin with, either. I looked them over last time I was unemployed.

That's not wrong. It's only indicative of how poorly their stuff works with other stuff.

One of the interesting things about the Android Linux scene is that it's common for distributions to have various user-selectable schedulers. This seems kind of unusual on desktop Linux.

Did I hurt your fee-fees?

Maybe. I never saw that... but that's the sort of thing that can easily be worked around if you have good legal representation, and Google has very good immigration lawyers.

I don't know about other places, but Google hires a lot of H-1Bs because when you're trying to hire the top hundredth of one percent of talent, and you need tens of thousands of such people, the US just doesn't produce enough. Not because the US is bad at producing top software engineering talent, but because the US is only 4% of the world's population. Expanding the scope to include the whole world lets you find a lot more smart people.

The distribution at Google seems to be (from where I sat) about 1/3 from the US, 1/3 Asian (especially Indian and Chinese) and the other third made up of the rest. So, given that we're only 4% of the world's population, I'd say that Americans are pretty heavily overrepresented. Even more when you notice that the non-natives have a higher average education level. My team as it was when I stopped managing had three Americans, two with BS degrees and one with an MS, and we had five from other countries, three PhDs and two MS.

They're not cheaper than citizens, they're more expensive than citizens. They get paid the same as citizens but Google covers their immigration legal expenses, which can easily be $10-20k every few years. Of course, that's peanuts compared to their salaries.

I'd expect that every instance that gets even a little public attention goes viral and ends up on the news. It's just too novel and juicy not to.

It seems unlikely that the driver model will get re-designed. It's all fundamentally C ABI now, and it will stay that way, because all the drivers won't get rewritten. The Rust code that interfaces with it will just have to be careful, and carefully diagnose any driver misbehavior. But misbehavior shouldn't cause a BSOD. At worst it should cause whatever operation was being attempted to fail.

It's been a while so I can't really direct you. When licensing became very uncertain I backed away and haven't done one in a while.

My best advice is to get a good flight controller kit up front so everything works together without a lot of screwing around. Also to read lots of build logs before you do one. And maybe start with a cheap type to build familiarity.

Also any design where you just have arms connected to a central board tends to be flimsy. I started with a SK450 and it's kind of floppy

They deliberately destroyed our public lands to make sure we all had to pay to live and you're here for it

If apple doesn't want to be in the middle of every transaction, they are welcome to stop doing that. No one is forcing them to gatekeep everything.

SLI causes problems with a lot of titles and also isn't available on Linux any longer. (There is still a feature called SLI in the Linux driver but it is NOT SLI.)

You didn't explain why they would need more than 60Hz.

The USA built that by paying for it.