Comments by "James LaBarre" (@SenileOtaku) on "Proč Microsoft nemůže vytvořit konzistentní systém Windows" video.

  1. Childhood??? Closest I could say for 'childhood' systems was the DEC PDP11/20 (and that was high school).
    2
  2.  @RobertVandenEynde  Actually, there are themeing engines, etc that can fix this (I think KDE/Qt is actually better at it, but GTK is pretty close). They've already taken it into consideration years ago, even though it's not part of a basic installation it is readily rectified.
    1
  3.  @badbad_  Linux has been my "daily driver" for nearly 20 years now. Use it at work as well as at home (it's the work machine where occasionally, depending on which contract job I'm on, is unfortunately MSWindows).
    1
  4.  @tamaspacso9899  Hey, I could be talking about ReactOS instead.... (it's a MSWin clone, if you haven't heard of it).
    1
  5. Have no problem with UI inconsistency on my systems. I'm running the Cinnamon desktop on LinuxMint, and all blends in very nicely. You have FAR more flexibility in it's look, colors, shading, elements, etc (even though the Gnome3 devs do everything in their power to break user configuration in the GTK libraries). If you're using KDE/Qt applications under a GTK-based desktop, you can even theme those to more closely match the GTK configuration (and it works the same if you are on KDE, which can manage GTK theming). And if you're running some MSWindows application under the Wine runtime, even those can be made to blend in seamlessly. Part of the secret with this is *modularity*. MS needs to break-apart a lot of the functionality of their OS. As it is now too many elements are heavily intertwined with other unrelated components, too many layers don't merely bleed into each other, but have pieces welded in that have no business operating at that level. As far as 'backwards compatibility" is concerned, I'd think MS should take on the "Wine" approach. For that matter, they could essentially just port Wine to MSWindows, and make that the compatibility layer to run all those 'ancient' APIs. Then they could migrate those legacy APIs out of the core/kernel of the system, since they'd be supported within the compatibility layer. The wine-layer could then be frozen to whatever MSWin version they want to stop at (probably W7), and let the core handle newer functionality without having to worry about breaking legacy applications. Biggest problem is that MS would have to submit that legacy code into the WIne project, under a GPL license (various reasons too involved for here), which I don't see them willing to do. The alternative would be to base it on the very out-of-date ReWind fork of Wine (an awful lot of work to bring up to date, likely to costly to even consider).
    1