Installing OS, 10 years ago:

Windows: click a couple of buttons enter username and password

Linux: Terminal hacking, downloading shell scripts from github

Installing OS today:

Linux: click a couple of buttons, enter username and password

Windows: Terminal hacking, downloading shell scripts from github.

Link to video: https://m.youtube.com/watch?v=qKRmYW1D0S0

  • @PenisWenisGenius@lemmynsfw.com
    22•5 months ago

    I tried to help my brother, who is a computer scientist to install windows 11 on his new am5 motherboard build. Am5 was really new and even with our combined knowledge it took all day of fucking with it to find a way to get windows 11 to recognize the m2 ssd. We had to load it with an older driver from the manufactures website and we had to do some kind of shenanigans to get the installer to actually recognize the files. Iirc this was a gigabyte motherboard, a reputable brand.

    This was when am5 was newer so it’s kind of understandable I guess, but I also installed arch for troubleshooting purposes that day and it only took 30 minutes 🤷

    • @MalReynolds@slrpnk.netEnglish
      2•5 months ago

      And when I switched mobos from Intel to AMD, it just booted (Arch then). Couldn’t believe it, just went.

    • @Avatar_of_Self@lemmy.worldEnglish
      1•5 months ago

      To be fair, I find that people with a Computer Science degree are pretty much just like most other users except that they need more privileged access somewhere because they are usually software developers or somewhere in that orbit. A Computer Science degree does not prepare someone to be a sysadmin. That doesn’t mean they can’t be an excellent one but it certainly isn’t because of their degree path.

    • based_shrimp
      0•5 months ago

      Usually got problems with Windows not recognizing drives during install only on Gigabyte mobos. Turning off all forms of Fast Boot in BIOS fixed it for me, but it was an older motherboard (one for AMD FX series, IIRC).