I suggest trying Windows Subsystem for Linux. You’ll get a simpler way to get familiar with the command line, which is the important part if you’re interested in development.
That or dual boot, you don’t need to set aside a large partition for messing around.
I’m a fan of “keep it stupid simple” or, as I tell myself at work on the daily, “keep it simple, stupid”!
Oh man, I had no idea about that.
I’ve been using Nova for something close to a decade now I think. I just toss it on my new devices and move on, it’s done what I wanted for ages (mostly for the adjustable grid, but I’m sure there’s some features it has that I’ve stuck with that I just feel are default at this point, stock launcher just feels weird).
I don’t think you need to wait years for user friendly Linux tbh! I recommend checking out Linux Mint. It’s basically designed for people used to Windows and handles the technical stuff for you.
You can do almost everything through the GUI rather than the command line, so for things like updates, it’ll show you a little notification in the corner by the clock like you’re used to, you open up the software manager, and click the update button.
And most software nowadays can either be downloaded through an app store like interface, or by downloading an executable file from a website.
And if you’ve ever used a mac, there’s a time machine equivalent built in (timeshift). So you can set up an automatic backup daily/weekly/etc and if you mess up something, in most cases you can revert back to a point when it wasn’t messed up.
I say give it a shot, you can always go back if it’s not for you! But usability has improved so much in the last few years.
That’s odd! I had no issues with the stock Ubuntu install. Installing CUDA on a Windows machine requires WSL2 now, but I didn’t really use it for anything more than that, so I could’ve just not used it enough to find problems. As soon as I finished the semester that required proprietary software, I got rid of Windows entirely though.
IMO, as long as you get comfortable with the basics like navigating directories and moving files, installing and updating software (first through something like apt, compiling stuff manually isn’t necessary at first), and managing some basic bash settings like aliases, you’re pretty much set. At least, from a programmer’s standpoint.
I dunno how well versed OP is in computers overall is the thing. The above is a good baseline, but you need a general understanding of how operating systems work in general to be really comfortable with something like Arch. Like you gotta know what a driver is before you can troubleshoot issues with your hardware, or if you’re managing disks it’s good to have an idea of how filesystems work. But that all comes with experience.