331–340 of 423 posts
I don’t quite get why some developers seem hell bent on those kinds of hybrid development environments. Why not straight up Linux or macOS where he user-space is consistent at least?
WSL2 was promised as a good working extension for a Linux dev environment on windows by my peers. Sadly, a whole host of issues specific to my dev environment meant that it was useless as I’d spend more time fixing it than getting any valuable use out of it. More importantly, this became the very reason I switched to arch full time, and haven’t looked back since. I still hope that it becomes what it was promised to b…
Opposite anecdata - I got a gaming PC and i migrated all my development to it and WSL(2) has been a godsend. VS Code has a "WSL Remote" mode that works really well (where a vscode server runs in Linux and the windows GUI access it "remotely"). I even use the Windows Github app for the occasional GUI-assisted commit, and apart from being slow its fine. I've had only two problems with this set up: - Occasionally VS Cod…
WSL2 linux distros are not equal to bare metal linux distros. WSL2 Debian doesn't have systemd installed and what a fvckery it is trying to get it to work. That means sshd, docker, k3s don't work as expected on reboot. Some apps do not install properly becasue scripts expect systemd. Windows networking is PITA too just to do something simple like SSH into a WSL2 instance.
I don't get why deep Windows integration is so important. It's not something I would use on a production box. I just want Hyper-V to work like VMware and VirtualBox. As you say, VSCode remote makes it all seamless anyway.
I had to go back to VMware 15.5.2 (version before hyper-v layer) and disable hyper-v completely.
Earlier quoted context omitted.
The Windows clipboard just works, because WSL2 terminals are just regular Windows apps.
At this point - Can't you just SSH into the local linux VM or a remote linux server?
Earlier quoted context omitted.
Opposite anecdata - I got a gaming PC and i migrated all my development to it and WSL(2) has been a godsend. VS Code has a "WSL Remote" mode that works really well (where a vscode server runs in Linux and the windows GUI access it "remotely"). I even use the Windows Github app for the occasional GUI-assisted commit, and apart from being slow its fine. I've had only two problems with this set up: - Occasionally VS Cod…
I don't really know if you can call running a remote vs code setup on localhost as opposite anecdata. Isn't that just more of the same bullshit hoop jumping? Everytime I hear about how great someone's wsl setup is I roll my eyes because it inevitably involves some rediculously convoluted wrangling to the nth level for something that is relatively basic on native Linux. And these people rarely have an excuse for why t…
But it’s not jumping through hoops? I just either run `code .` (like I did on macOS) or select recent folder from within VS Code. It all just works fairly well, identical to ‘natively’ within Windows (except the occasional ts slowdown I mentioned before).
> And these people rarely have an excuse for why they prefer windows
Not that anyone needs an ‘excuse’ for their personal preference, but I would actually prefer macOS. But I got a Windows PC to use software that only runs on Windows (games) and then the whole wfh thing happened and here we are. I’m not interested in rebooting between different operating systems when I switch tasks, especially when they overlap (developing for games).
Convince Bungie to port their game to macOS and I’ll buy a Mac Pro to be back home on a Mac full time :)
Earlier quoted context omitted.
Tip: Add a separate SSD and format it as ext4. Mount it to wsl2 and do all your work there. https://docs.microsoft.com/en-us/windows/wsl/wsl2-mount-disk Currently, the mount is not automatic so you can make a startup.ps script and run it on start through group policy.
Ah this is a great tip, I will have to try this one -- thank you!
Earlier quoted context omitted.
Also opposite anecdote, I switched from Pop!_OS to Windows after getting into music production recently as a hobby (MIDI controller driver software doesn't always play well, even with WINE-devel) after over a decade on Linux. I expected to hate it, but I'm asking myself why I didn't do this sooner. It's the same sort of scenario as before -- I have Windows running the games I occasionally play, and music stuff, and I…
I've recently come across the same issue with DAWs. Settled on having multiple machines and switching the drives if I need to reuse a workstation for something else. Most of the time you can dedicate cheap systems to specific utilizations, it will save you time and effort. e.g. There is no reason for your DAW machine to also be your gaming machine as the hardware requirements are pretty different.
it's a GPL violation as far as i'm concerned, so anyone who uses it deserves what they get
Earlier quoted context omitted.
> It always seemed strange to me that people would rather use WSL than the real thing when Windows doesn't bring much advantage. Windows brings lots of advantage to some things (including interfacing with the large number of people who rely on people having software that works only or best on Windows; in anything other than very tech-focussed firms this probably includes your employer, and even in such firms it often…
My team has to support both windows and Linux builds of our product. WSL1 was a godsend for this - I no longer had to ssh into a VM and could build both the Linux and windows versions from the same source, which was amazing. I hit one issue with wsl2 and then I reverted because I learned that this scenario (different builds from same source) would always be slower on wsl2.
Earlier quoted context omitted.
I don't really know if you can call running a remote vs code setup on localhost as opposite anecdata. Isn't that just more of the same bullshit hoop jumping? Everytime I hear about how great someone's wsl setup is I roll my eyes because it inevitably involves some rediculously convoluted wrangling to the nth level for something that is relatively basic on native Linux. And these people rarely have an excuse for why t…
> Isn't that just more of the same bullshit hoop jumping? But it’s not jumping through hoops? I just either run `code .` (like I did on macOS) or select recent folder from within VS Code. It all just works fairly well, identical to ‘natively’ within Windows (except the occasional ts slowdown I mentioned before). > And these people rarely have an excuse for why they prefer windows Not that anyone needs an ‘excuse’ for…
No kidding. But on this site I’ve been lectured about the “consequences” of my personal preferences (when they in no way make alternatives less viable) and told my conscious tradeoffs are actually ignorant of the things I’m trading off even after I explicitly stated them. Tech communities love to talk about choice and freedom and love to try to Jedi mind trick people out of it in the same breath.