I have been using Windows my entire life, but since I got my Steam Deck I’ve been considering trying to get into Linux.

I obviously don’t have much of an idea where to begin, other than that I’m currently also trying to learn Javascript. I’d like a basic workstation I can code on and mess with, that doesn’t run more than a couple hundred. Could use some recommendations for hardware plus where to begin.

  • AVincentInSpace@pawb.social
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    11 months ago

    Worth noting here that any even remotely modern computer supports hardware virtualization for natively running virtual machines, including laptop chips and even Apple silicon, although you usually have to enable it in the BIOS since few people need it and malware has been known to abuse it. The setting for that has various names depending on motherboard vendor but usually related to “Hardware Virtualization”, “Intel VT-d” or “AMD-V”. If for some reason your machine doesn’t, some virtual machine software also supports software emulation although be prepared to take a massive performance hit.

    Also worth noting that in my experience, even with hardware virtualization, in most cases, the performance of a virtual machine in a graphical environment borders on unusable no matter what operating system is running in it, and Linux is known for its ability to run smoothly on lower spec machines than Windows can when installed on physical hardware. Also also worth noting that every Linux distribution worth its salt lets you “try before you buy” (or to be more accurate, try before you install) and experience basically the whole operating system including installing programs from within the installation media, without touching your existing OS.

    (Of course, you might have better luck than I did running a virtual machine, and in the early days of your Linux journey you will DEFINITELY want a working copy of Windows you can quickly fall back on when something breaks. If you install a VM and you’re happy with how it performs, by all means, stick with that till you’re good and ready to make the next step. See how you like it, get some practice using it etc. before you make extremely-difficult-to-undo changes to your boot disk. If you want to get a bit closer to how it performs for real, but don’t trust yourself to install a new OS without accidentally erasing all your data, read on.)

    You can write an ISO image to a flash drive, boot off that flash drive, close out of the installer window (it’ll drop you to the desktop) and give Linux a test drive before you install it for real. If you decide you don’t like it, unplug the flash drive and reboot your computer, and Linux will leave no trace it was ever there. (Depending on your setup (specifically laptops that use TPMs and full disk encryption) you might have to reenter your Bitlocker password (which is a ~40 character random alphanumeric string saved in your Microsoft account) to re-enable secure boot, but that’s it.)

    Not everything works in a live environment – you’ll have a hard time installing graphics drivers when you haven’t installed the OS, for example, and all data/programs you create/download will be limited to the size of your RAM and wiped when you reboot – but you can get a pretty good test drive. You can get a feel for how the GUI works, customize it to your tastes, and even download and run stuff like Discord and Steam all without touching your boot disk.

    If you decide you like Linux, but not enough to completely leave Windows behind (no shame in that! It’s where I started too!) you can install in a dual-boot configuration. Basically, you carve out a portion of your drive for permanent use by Linux (I recommend ~1/4 to 1/2 of the total drive space but it can be whatever you want), your Windows C: drive shrinks by that much, and you get asked which OS you want to boot into each time you restart your computer. Neither OS will be aware of the other’s existence, and from the perspective of any programs you install they will be two different computers. Linux can read and write files saved on your Windows partition, but not vice versa, so if you want to copy files between them you’ll need to boot into Linux.

    Tutorials on how to set up a Linux dual boot abound online (in fact, many distros’ installers have it as the default behavior), so I won’t explain how to do it here. If you have any other Linux related questions, though, feel free to send them my way!