spoiler

made you look

  • 0 Posts
  • 21 Comments
Joined 11 months ago
cake
Cake day: July 27th, 2024

help-circle
  • Tons of software meant to run on 32-bit hasn’t been updated to run on 64-bit natively.

    32bit only Linux apps are basically non-existent, anything with the source available and maintainers would have been ported at some point in the last 2 decades, otherwise they have very specific technical reasons for being 32bit only (like OBS iiuc), the source has been lost somehow, or it’s a proprietary program where the company has no interest (e.g. Valve with Steam)

    In fact I think Steam might really be it.






  • I always thought it was purely a hardware limitation, but reading up on it I found it’s actually just “virtual 8086 mode” that was dropped, 16-bit protected mode is still available even when running the CPU in “long mode”.

    So it rules out DOS apps, but 16bit Win 3.x apps should still run. But it’s probably a compatibility minefield, and even MS decided it wasn’t important (iirc the only thing they kept around was support for 16-bit app installers, but by internally swapping them out with 32-bit versions when run, since it was apparently common for 32-bit 9x apps to still use 16-bit installers so they could show a proper error message when run under Win 3.x)















  • Why have a laptop or a dual boot with Linux when you can now more easily stay on the proprietary OS ?

    This is called market retention.

    Preventing migration to another OS, another software ecosystem.

    The ‘Embrace’ and ‘Extend’ parts of EEE.

    That’s stretching the definition to the point it’s nearly unrecognisable.

    What the term meant was for things like Internet Explorer, where MS adopted an existing standard (Embrace), started changing it in incompatible ways (Extend), while using their market power to lock out competitors (Extinguish)

    e.g. IE used an incompatible method for sizing and laying out elements than any other browser, so a site that laid out properly in NN4 looked broken in IE6, and vise versa. So most devs targeted IE6 as it was more popular, and NN4 users got more and more broken sites.

    ACPI was similar, Windows had an extremely lax implementation of it, so motherboards often shipped with bugs that Windows would ignore but would stop anything else from booting. Intentional? Doesn’t really matter, since it sure was helpful in slowing the adoption of things like Linux, that had to come up with workarounds for all the broken hardware.