• ssladam (edited 9 years ago)
    +6

    I'm a massive convert. I went from being a bleeding-edge upgrader, to holding out all 5 (6?) of my systems to Win7 for the past several years. But Windows10? I've already got the insider preview running on two systems, and I l-o-v-e, love it.

    The one fear I've got is that I'm holding out hope that MS won't be overly restrictive with customizations. I'm hoping they really open up and allow modders to do exciting things with tiles and the start menu, rather than locking it in too tightly.

    • Nerdeiro
      +4

      Windows 8.1 is tolerable if you install a start menu replacement, like Classic Shell. But even Win10 requires such hacks. The new Start menu is not quite there yet.

      One issue I have with the new menu is that it's not possible to move the "Metro" apps to sub-folders in the All Apps section. Classic Win32 apps can be moved around and tucked neatly in sub-categories just like in Windows 7 and before. This is a pain in the ass, because the only categorization for "Metro" apps is alphabetical, with separators by letter. Each entry is this list takes more space than they did in Win7. A flat list like this makes the scrolling annoying.

      Classic Shell solves this neatly by separating "Metro" and Win32 apps in different sub-menus, and if I never want to see the "Metro" stuff, I can simply remove that part.

      If Classic Shell is still needed, there's no reason for me to upgrade, so I'll stick with Win8.1 on my gaming rig, at least until I really, really need Directx 12.

      • gabe2068
        +3

        Why do you say 'tolerable'? That implies that you wouldn't be able to use it without that? I've never understood that because windows 8 is not the worst windows to come out and it isn't hard to use at all. I'm glad stuff has been changing around in it and not stayed exactly the same as it had been for 10 years, that would be boring.

        • Nerdeiro
          +2

          you wouldn't be able to use it without that?

          Exactly. I wanted Win8.1 for my gaming rig because it has better handling of SSDs and dual monitors, but the start screen is a hassle I'm not willing to put up with, specially on a 27" non-touch display.

          I could tolerate it if it was possible to pin it to a specific monitor (my secondary is a smaller 24" that sits on the side) BUT have the applications open on the main display, but Windows 8 doesn't do that, applications open on the same display of the start screen, requiring them to be moved around.

          • gabe2068
            +3

            I've run windows 8 since release and 8.1 since release and I spend almost no time in those menus? I just don't understand how it is that big of a hassle. You literally click one button and you are on the desktop and don't have to worry about it at all.

    • fred (edited 9 years ago)
      +3

      Ive heard good things thus far. Given their history im holding out until SP1 (or an equivalent) and the inevitable bugs get worked out. Been burned too many times in the past to overlook MS' history of major OS releases.

      • spaceghoti
        +5

        According to the Wired article posted previously:

        There’s no service pack coming in six months to fix a hundred things and break 50 others; Windows is just going to get better every few weeks.

        • fred (edited 9 years ago)
          +3

          They say this, but its unproven, and the models they have built and their customers have adhered to will likely determine that course of action.

          Microsoft hardly tests and QA's their monthly updates. Service packs and the whatnot helped reduce this overhead for companies supporting the windows OS.

          Its likely fine for consumer use but in a business setting things change a bit. I hope they manage it great, but im not going to be on the bleeding edge given the shaky release history.

          Even with them ditching patch Tuesday as a method, companies will still run releases on a schedule with WSUS/SCCM/LanDesk etc for version and QC.

          Service packs in the past were tested and vetted much more than simple updates and in a lot of cases included essential updates that were already released. they may call them something different, but they have a lot of companies that use their OS, and they need to be able to continue to meet their needs.

          • spaceghoti
            +3

            You're definitely preaching to the choir, here. I don't trust anything Microsoft does out of the box. I'm not comfortable until they release a service pack with all of the updates necessary to create a stable system. My point is simply that Microsoft has said they're not doing service pack updates for 10, nor are they planning to release any new versions of Windows. They're simply going to push out periodic updates to patch and upgrade things they feel need fixing as they come along.

            How this works out for them remains to be seen. I don't have much faith in Microsoft architecture.

            • fred
              +3

              I think they are definitely in a bad spot overall. In their search for stability they have found trouble dealing with the bloat of their code.

              Products like Exchange are good examples of this. They have started releasing them every few years, but many companies rely on email so heavily, and Exchange patching being so finicky and break prone that many companies just got to 2010, skipping 2007 altogether (the last two I worked for included).

              And these, even on their "new" email system are already outdated by almost two versiosn. and due to their inability to support the code and bloat that comes from version to version a 2003 ->2013 upgrade isn't possible. So how do they fix that? How do they instill confidence in companies that you don't need an Exchange Certified Master to help with an version upgrade?

              The same can be said for server and workstation releases but on a issue of scale and version control. To this day we have 1 or 2 2012R2 servers but still rely on 2008R2 and 7 at our core. I still have some 2003 boxes im decomming and it has be a pretty big pain to get through some of these upgrades with vendors. I don't want the headache of support 7, 8, 8.1, 10, 2008, 2008 R2, 2012, 2012R2, and whatever 10's server version is.... That's like 8 different code bases and software compatibilities I have to support. So what do we do? We trim the fat, 7 and 2008R2 only. We have a few 8.1 (surface testing)/2012R2 (Few enhancements like DHCP replication) and may consider a move to 10 when the EOL 7/2008R2.

      • the7egend
        +2

        They're going for incremental updates and no more service packs or even major releases.

    • [Deleted Profile]

      [This comment was removed]