• 0 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: February 15th, 2025

help-circle


  • I built a computer in 2012 with the idea of having 3 OSes to boot from: Windows 7, Mac OS 10.7 (hackintosh), and CentOS.

    I partition the drive into three main parts, and install each OS on one each. Except that I had to do it again, because Windows 7 lost its absolute shit that it wasn’t on the first partition. Just threw an absolute shit-fit that it didn’t come first.

    So I re-do the installations, let Windows be first in the partition order, Mac OS second, CentOS third. The next problem was that I couldn’t download any drivers on Windows, because it couldn’t recognize the absolutely bog-standard network controller on my motherboard. So I boot into Mac OS X, which (with a couple of quick kext edits) already recognized all of the hardware on the mobo despite none of it being Apple or Apple related, download the drivers for windows, throw them on a FAT partition I set up to exchange data between the OSes, and finally get Windows running in about 4x the time it took to get Mac OS running on the exact same built-for-windows hardware I’d cobbled together.

    And of course I fire up CentOS, and it was pretty much, “I got this” right off the bat.

    I’ve been using Windows and Mac OS since the late 80s, and linux since about 1999, and I still have never encountered a more fussy OS than Windows.







  • But that’s the thing, you haven’t instructed it that you want it to quit, you’ve only instructed it to close a window. That’s what that button does, and its function shouldn’t change based on whether it’s the last window in the application. Plenty of uses for running programs headless and not having them take up resources by keeping a window drawn (though certainly less of an issue now than it used to be).

    Dunno, I like more granular control instead of changing functions based on context when it comes to basic UI. If I want to quit a program, I quit it. If I want to close a window, I hit the UI element that does that, and only that.

    But this split goes back to the late 80s: Microsoft was late to the multi-window paradigm, and their first implementation pretty much was wrapped in one program, one window. If a program needed multiple windows or panes, they were all drawn in a parent window. Closing that parent window closed the program. They caught up I think with Windows 3.1 (and not fully until Win 95, though my memory is fuzzy, it’s been 31 years!), but kept the program-window coupling because their users were used to that, and it’s stuck. Linux desktop environments were built more towards the Windows paradigm so as not to confuse the largest source of new users, so now that stuck, too.