That could be a 2 birds one stone situation for me. My daily driver is a laptop with Nvidia hybrid GPU setup and it’s hella-twitchy with X. If its more stable with Wayland that’s yet another reason to try switching.
That could be a 2 birds one stone situation for me. My daily driver is a laptop with Nvidia hybrid GPU setup and it’s hella-twitchy with X. If its more stable with Wayland that’s yet another reason to try switching.
While I appreciate the difference between mirroring and emulation, @lemmyvore@feddit.nl might have a point in so far as scrcpy
and other options that aren’t emulation, may still be part of the reason why no one is making polished emulation options.
If a dev can get by with a bunch of physical devices connected and controllev via adb, scrcpy and the like, or a passable emulator in Android Studio, then there’s less reason for them to build or contribute to an emulator for their needs, and consequently op (and the rest of us) don’t get a shiny open-source emulator.
Man! I was super excited about this, being a big NixOS fan, but then I realised that the “Way” bit is going to kick me in the nuts. I haven’t made the switch to wayland yet; I keep thinking about switching, but last time I checked being tied to i3 and nvidia hardware scared me off (although I’m aware sway is a drop-in alternative to i3, but it’s an extra complication). Another reason to make the switch when I can though!
Out of curiosity, how do big media apps treat something like Waydroid? Like, I imagine Netflix and co being awkward with anything like this in a misplaced attempted to prevent “piracy”. Do you find apps treating you like a second class citizen?
Nice one 👍. I’ve been looking to replace onenote handwritten notes for years with something with better Linux support. Interested to give this a try! Thanks for sharing!
Where do we stand on hoarding code to protect against outsourcing? I have a friend who is encouraging his team to do everything he can to hoard and make it impossible for recently onboarded individuals in a “cheaper cost center” to mess with it.
I think it’s the right call, for both the team and the company. The team wants to keep their job, and to keep building the thing they worked so hard on. But I think it’s also best for the company. Management can’t control themselves when they see that they can get literally 10 engineers for the price of 1 local engineer. They know that each of the 10 is going to be less good than than a local engineer, but they always fall for “but still, they’re not that much worse and for that price how can I lose!”. Of course, the damage of 10s of mediocre-bad engineers is far more costly, especially when outsourcing an existing project. So I’d say it’s the right thing for everyone for the team to protect their code ownership anyway they can.