you are viewing a single comment's thread
view the rest of the comments
[–] 90 points 2 years ago (2 children)
  • [–] 25 points 2 years ago (7 children)

    Maybe this will convince more people to switch to linux.

  • source
  • parent
  • hideshow 14 child comments
  • [–] 22 points 2 years ago (3 children)

    With the work that Valve is doing on Wine, and Proton, it's really becoming easier and easier to justify the switch.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 10 points 2 years ago (1 child)

    With the work that Valve is doing on Wine, and Proton, it's really becoming easier and easier to justify the switch deck.

    FTFY

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 2 years ago

    Tried getting PCVR working with the Quest 2, unfortunately support is still a hot mess and leaves the system with a super janky flood of audio devices, in addition to legendary stutters that make it unplayable. Win11 still better for VR.

  • source
  • parent
  • [–] 8 points 2 years ago (1 child)

    Could be. If you're running a core 2 duo I am fairly certain Linux will run markedly faster than Windows 10+...

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 2 years ago

    I actually still have some old servers with chips from that period, one of them is still being used as my firewall but until last year I was using others to run multiple VMs for email and web sites. Not as power-efficient but they do still work.

  • source
  • parent
  • [–] 3 points 2 years ago (1 child)

    That's not a guarantee on the Linux world either, but at least you do have the option of recompiling your distro to not use those options.

    There's talks from some distros to start dropping support for such old CPUs because it's holding back newer CPUs that could run even faster by using those instructions.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 2 years ago (1 child)

    Is it really that hard to include a fallback though? Obviously there's a way to collect the information without that flag. I suppose if you didn't want to take a performance hitting checking the flag all the time it could become a compile option (I would think anyone running that old of hardware would be willing to learn how to compile the kernel anyway), but there should be options available to keep the support available some how?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago

    That's pretty much exactly how it works already. You compile with -march=x86-64-v4 and it'll use SSE and AVX all over the place.

    glibc does the runtime thing, but only once on application startup where the dynamic linker will link the version of the function optimized for your CPU. But it's a manual process on glibc's part, the variants are written by hand.

    Not every project cares enough to do it dynamically like that and it would be a nightmare that way.

    The fallback is, recompile with -march=x86-64 which will only use the base set of instructions. Or -march=i486 if you want to run on absolutely ancient hardware.

  • source
  • parent
  • [–] -3 points 2 years ago (2 children)

    Issue is, a lot of people still using Windows, and Linux pro-audio is still questionable at best (lack of drivers, etc.).

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 2 years ago

    Also there's lots of industry tools where you can't really use anything but Windows. Even if you could technically make it work, it isn't a good idea because of how critical the system you're interfacing with is.

  • source
  • parent
  • [–] 4 points 2 years ago (1 child)

    The actual oh no is the amount of ewaste this will create as people buy completely new systems as they think that's their only option

  • source
  • parent
  • hideshow 2 child comments