New work laptop arrived.
I've been using Linux on the desktop for 22 years. However, I'm increasingly having to jump into my Windows VM in order to work with PP and Excel files; often the web-based versions cannot expose features I need to use, or handle the file size.
So: continue with Linux + Windows VM (to which I can now allocate a ton more RAM), or move to Windows and use the WSL for dev-related things (including Docker, k8s)?
@mauriciofauth I dual booted for a few years way back when - I found it inconvenient to go back and forth between the systems, particularly if I needed to do it more than once a day. Part of that was due to boot times, which today aren't as bad.
Definitely something to consider - thanks for reminding me of that option!
@heiglandreas @mwop @grmpyprogrammer While I don't agree with policies from MS, WSL2 is a nice environment to work in and I regularly switch between working there or in normal Fedora (mostly around do I plan on playing certain games that don't work under Proton).
Since the addition of the GUI layer you can even run non-CLI apps, so I don't feel hindered at all working under it. I still prefer GNOME and full fat Linux, but it works.
So... because I had a work deadline this week, and because my Windows VM on my old machine was crashing, I ended up using the new machine's Windows 11 install... and I'm not hating it. Haven't had a chance to get moved into WSL yet; that'll be next week. Will report my experiences!
It was death by a thousand paper cuts - unreliable communication between gpg on wsl and my yubikey, lack of an easy way to type special characters (I don't have a num pad on my keyboard), lack of middle click paste, no way to restart MS Terminal quake mode if wsl restarts, difficulties getting vagrant working within wsl, and more.
@dragonmantank @heiglandreas @grmpyprogrammer @shochdoerfer None of them, by themselves, was horrible (though the yubikey thing made gpg signing and ssh a huge issue). But in the aggregate, I was setting myself up for a frustrating experience.
I had Linux up and running how I wanted in hours. Meaning I'll be back to normal productivity immediately when I sit back down to work next week.
Silver lining: I better understand windows now, so my VM is already easier to work in.
@shochdoerfer @dragonmantank @heiglandreas @grmpyprogrammer yeah, actually started down that route before going the whole "communicate via socket to the windows gpg-agent" route. The problem was that usbipd couldn't bind it - failed every time. And for some reason, the socket route started failing for me, even when win gpg-agent could see the card. Honestly, all of this felt like hacks running on top of hacks.
Far easier with windows running in a VM - virtualbox binds all USB transparently.
Open source. Open community. We are dedicated to building and enriching the PHP community.