It definitely lends credibility; versus the introduction from the other comment - that this is the guy that glitter bombs package thieves on youtube - which makes me take this less seriously.
Wsl 2 is really cool, right up until you want/need to do anything with the underlying hardware. No usb passthrough, no hardware acceleration, gpu passthrough is there but it's still early stages as performance is about half of native and vendor tooling is absent, etc
It's getting better all the time though - they tease usb passthrough might be doable as it's already supported with remote desktop
There was a story a few weeks back about Microsoft working on a new android subsystem. So truly coming full circle; android OS stability (via project treble), the vm approach instead of compatibility layer approach, and improvements to hardware sharing/passthrough to wsl 2 mean that they can finally realize what they tried to do with Projecy Astoria.
They'll need to manage their own app store as I can't imagine they'll have gapps//shims out of the box, but that works in their favor if they wanted to do another mobile play.
As i understood it, using raw input keeps the system awake and that may be working as intended (hence they suggest that Microsoft better document that//reflect it in powercfg /requests). The issue is that GeForce experience was requesting raw input when it wasn't necessary.
As i understand it, she was supposed to submit to google for an internal review a fews prior to externally publishing it. She simultaneously submitted and published it, and Google sought a retraction after internal review. She met that with an ultimatum with do X or I'll quit. They took that as a resignation (as Google wasn't going to do X), and accepted it.
I'm not fully informed about what she wanted, but I don't think it was particularly unreasonable, the controversy more has to do with headlines and spotlights about this person and her conduct/history in the past.
It did, but only for a small portion of applications. Others would run very poorly, if at all, depending on the degree in which the application hooked into google services//android api. The original project was more analogous to WINE for *nix systems, a compatibility layer; there where many edge cases that simply didn't work and supporting new versions of Android would require almost completely rewriting it (pre project treble).
The VM route is simply more workable and sustainable. While WINE has achieved some great success, it's still a spectrum. Some software simply doesn't work, some mostly works, some works but performance is abysmal, and some work flawlessly - depending on how deeply they integrate with windows and what APIs they utilize.
It's been a good while since I read the original story, but Wikipedia [0] has some background and should have some citations if you want to dig in further
WSL's origins are actually as a android subsystem for when they where making a mobile play with the Windows Phone. At the time it ultimately got scraped because it was too ambitious of an undertaking, and got spun off as WSL. Now that android[0], windows OS and WSL[1] are more mature it's going full circle.
[0] maintaining an android subsystem (and various versions as distros) should be easier now for the same reason it's easier for vendors to update phones, project treble.
[1] better filesystem sharing, GPU pass through, WSL is close to natively supporting graphical applications, etc
Can you point me to any examples of that stereotype? Historical employment figures, long form discussions, etc? I've genuinely never heard of that one, and considering the dominant solution in this space is Postman an alternative, female gendered solution could be argued as inclusive.
I don't get the gender backlash here, personification has been a thing for a long time and there doesn't seem to be any malfeasance (intended or otherwise) here. It's not lewd, doesn't play to stereotypes, etc.
To me, a basic litmus test is whether you could easily swap the gender without reworking anything. If you can't, it's probably offensive, if you can it's practically gender neutral (naming aside). It's not a catch all, obviously, as it's no replacement for awareness of history, culture, stereotypes etc.
It's easy enough to maintain a rebranded mirror synced to upstream. Instead people seem to want to take offense just for the sake of virtue signaling.
You don't have to have it exposed to the internet. Without an active connection, clients cant make new passwords/sync, but you can access previously saved passwords that are already synced.
It also doesn't have to be exposed to the internet. You can have it accessible behind wireguard for instance.
I have it, a DNS server, cloud storage, etc on my home lan, and use wireguard to access it on the go.
What's the issue though? Their bio seems fine, they're experienced//well known, the signal protocol is open-source with no issues thus far as I'm aware...
I asked this the other day on a similar comment, and the best they could do is critique Moxie for having a savior complex