There are at least 10 different Microsoft design conventions in Windows 11
old.reddit.com
old.reddit.com
What happened to this will be easier to see, to remember, takes fewer clicks, is quicker.
I mean, you spend a billion bucks on a new design and get things like this (from MS Fluent):
Fluent experiences listen and adapt... They unite people and ideas, whether they’re on opposite sides of the globe or standing right next to each other... Fluent speaks in light and shadow, in spatial dimensions...
I just want to get work done. Save me from my spatial dimensions (and whitespace overload).
BARF. I can hear the thrumming of Enya's "Storms in Africa" behind this text...
Just basic things like putting focus on an input field of a pop-up dialog. I get that isn't sexy but it IS efficient. They should focus more on the later and less on the sexy gradient / look stuff.
Startup time is stable though: windows calculator has the same startup time as excel. Don't get me started on microsoft photos...
Modern UI quickly breaks down when you need to have complex software - software that needs a menubar, for example.
When thinking about design systems, there are few different levels and you speak about different ones depending on who you are talking to. For me it breaks down something like this, going from high-level to low-level:
Design Philosophy - Marketing (what you posted)
Design Principles - Designers / UX (accessible, minimal, emotion)
Design Language - Designers / UX (red is used to denote danger)
Design Library - Designers / UX / Engineers (ButtonPrimary color = blue, ButtonDanger color = red)
Design Implementation - Engineers (<ButtonDanger>Cancel</ButtonDanger>)
The ones marked as 95, NT, and XP are all fit with each other. Vista and 7 also go together fine, and with the UI theming still don't look inconsistent with the previous set.
The one marked as 8 looks right at home with 11 (which was really just a matter of giving it blurred transparency and rounded corners).
Splitting 10 RTM and the Store is weird. They very much go together.
That leaves 10 19H1 which is the biggest oddball to me and hopefully gets fixed to be consistent with 11.
But anyway, isn't it better that they haven't fucked with some of the older (95-7) UIs that your normal user is never going to see? (I'm counting add/remove programs in that set since there is a non-.cpl replacement that is modernized) Power users tend to hate it when things get changed for no reason other than aesthetics, especially since they often lose functionality.
I grew up with 3.1 and 9x. I don't want that back.
We have a bug in our backlog right now because we tack on an extra bit when we export files. Imagine we open foobar.raw and export foobar.txt and foobar.txt.info. But when the application tried to write out foobar.txt.info it hits the 260 character limit in NTFS. Meaning that the original file name was over 255 characters.
It was designed to work on a VGA screen with 480x640 pixels after all.
And this is from Windows NT 3.5 IIRC. Windows 3.1 didn’t have long file names (like the Apple II had in 1979 or so).
https://old.reddit.com/r/Windows10/comments/o1x183/the_famou...
The ODBC Driver interface for configuration is tied to the old dialog.
The interface for the drivers was designed around GetOpenFileName() as it was at the time.
One of the features of GetOpenFileName/GetSaveFileName is that the structure passed in can include two special options- a function pointer to a hook routine, as well as a custom dialog template which windows will insert.
The functions were improved in Windows 95 with the "Explorer style". Even old programs get this style at the very least, because windows will imply the flag.
unless a template or hook routine is specified. See if a hook routine or template is specified and the OFN_EXPLORER flag is not, then the hook routine or template was designed for the old-style dialog. Windows uses the old-style dialog in this instance so that the program can run and doesn't crash.
The ODBC Driver configuration uses a dialog template to add the "read Only" and "Exclusive" checkboxes. That is why it shows the old style dialog.
People might say, "They should update it"
Update what?
If GetOpenFileName()'s ability to fallback to the old-style dialog is removed, than you won't see this dialog. Instead, it will crash. Cool. great experience.
the driver interface? OK great. so now there is a new version of the ODBC Driver interface. Now all the ODBC Drivers need to be updated. Some of the drivers were written by companies that are either out of business or rather different. I have this sneaking suspicion that Paradox software isn't going to be writing a new ODBC Driver for the MS-DOS Database.
Just drop everything? OK Cool.... so now companies get forcibly upgraded to Windows 11 and literally cannot do business because they rely on them in some manner. "They should upgrade". I won't get into that except to say it's the stupidest thing I've ever heard, but companies in that position are far more likely to find ways to not upgrade the software that caused the problem so, you know, they can keep doing business. And not upgrading the OS is certainly cheaper than countless thousands of man-hours in upgrading their Business software.
And a big thing people don't understand about backwards compatibility is it's not just about old programs working. It's about new ones working to.
If Microsoft removed all "backwards compatibility", than practically nothing would actually work. Software would be constantly crashing, sending error reports, etc. Now, call me crazy, but somehow that doesn't seem like it's a great experience. And if upgrading to Windows X+1 suddenly caused programs to crash left & right, nobody is going to blame the programs.
It reminds me of when My Computer was renamed to This PC, and My Documents became Documents --- a subtle way to say it's not yours.
The latest anti user trend is of course that of referring to computers as "devices".
Point being that name changes can come from such over thinking.
You underestimate the amount of ducking around a normal user has to do to keep windows happy over the years.
Well, that and the fact that it actually does the trick 90% of the time, which is fairly stupid to begin.
Troubleshooting Windows is largely an exercise in futility to begin with; turning it off and on again is usually the only thing that even IT people can reasonably do (that, and google the error to find out about turning on/off this specific thing)
I don't think it is, it's like aging on an accelerated scale. Turning on and off is like death and rebirth, you don't have all the stuff you acumulate with age. No injuries, no tumors, it's a clean start.
The solution (if there is one) usually involves a fair bit of googling, uninstalling/reinstalling/updating things, maybe messing with the registry or settings.
You may think I’m exaggerating, but this is actually the list of issues I’ve had myself in a span of two years. I use the PC for browsing and gaming, nothing else. It has been very frustrating, and I’ve been working with computers for 20 years. I used to think Linux was a pain but am rethinking that.
Flash has been deprecated on the Mac for ages, and Adobe stopped supporting it completely last year.
They aren't really though. Aesthetically they are reasonably close but employ different conventions (e.g. the list/tree in win32 and the list in NT4 display the same kind of information but different ways, and with different icons).
Consistency is a pretty fundamental thing in interface design, and whether or not something "fits" aesthetically is only a small part of all this, which I think was OP's point.
I saw what the API of the classic Mac OS looked like[1] the other day, and it does resemble WinAPI very much. It's procedural, many functions take descriptors, many other functions take structs you allocate and fill in, there's a DIY event loop, and so on. It even has a windows.h (lol). Apple got rid of this in 2000. It then provided a VM-style "classic environment" backwards compatibility layer in OS X for ~5 years, and Carbon library for source-level compatibility for even longer.
Apple did manage to pull this off. Why can't Microsoft do the same? Why can't they put a seamlessly integrated 95/XP/whatever VM into their system that would launch when you run a win32 application, and finally give themselves the freedom to rewrite everything from scratch, with more sensible APIs and in a more memory-safe language?
Microsoft's insistence on maintaining native backwards compatibility with software some of which is as old as me is so perplexing.
This is why Microsoft has such a huge presence in corporate - unlike you or me, most corporates do not immediately update to latest, hi tech flashy tool of the month. If something works really well, they'll keep using it, sometimes for decades. And demand that Microsoft don't break it on their OS. Microsoft will happily support them as they earn a lot from corporate licenses and support.Apple doesn't have the kind of importance that Microsoft does in corporate. Nor does Apple have to support the kind of hardware and software that Microsoft does, and so Apple's monoculture helps them makes changes to their platform faster than Microsoft can.
But why does it apparently not apply to the operating systems themselves? And how would running win32 apps in a seamless VM (a-la Apple's classic environment) break that?
From looking at the evolution of Windows, it feels like they're only capable of writing new code, but not deleting or rewriting anything existing unless absolutely necessary to support new code. Those shiny UWP apps? Yeah, they still have that win32 message loop deep inside them.
As for running Win32 apps on different setups, it makes the system more complicated. When more vendors are involved, it also makes fixing things difficult - In case something breaks, Microsoft can say it is Apple's fault, and Apple will say we don't support Win32 apps, contact your developer. (Not to mention that Apple is not as corporate friendly as many others, like Microsoft, or IBM, as they are largely a business-to-consumer company and not a business-to-business company).
My idea is that Microsoft would build a special version of Windows that supports all kinds of legacy apps, and put it into a VM. And probably not update it much if ever. That would allow them to deprecate, and then remove, older APIs in the main system, which would in turn allow rewriting the internals to be less vulnerable. They totally have the resources needed to do this. And there's no technical innovation needed to do this, either.
As far as the end user is concerned, old apps still run. Except now they run in a sandboxed environment.
[1] https://en.wikipedia.org/wiki/List_of_macOS_components#Class...
I’m sorry. I had to laugh.
Windows has been so complicated and inconsistent, with built-in control panels, vendor mini-applications, inconsistent within Windows itself, where you see the parts that haven’t been touched since NT 3.5, alongside each and every version of Windows ever sold, plus the built in vendor specific control panels that makes it impossible to figure out what is the currently active Wi-Fi configuration (a recurrent problem I have when helping house guests to connect. Macs just work. Linux just works, Androids and iPhones easily connect. Windows laptops? Ha! Just use the range extender that’s in the guest bedroom. For some reason I will not dedicate the time to figure out for every Windows version and PC manufacturer why, that little thing seems to like Windows machines.
I use both Linux (Ubuntu/Raspian) and Windows extensively and overall most things just work better on Windows, poor design philosophies aside.
[0] https://iceburn.medium.com/raspberry-pi-connected-to-wifi-of...
The Disk Management UI's bottom pane, for whatever reason, has never worked with scroll wheels. It still gleefully ignores scroll wheels.
The Hyper-V Manager .. a new thing .. has a broken UI as well. It's "Actions" pane size is based off the screen-width, but the default size of the window is based off the screen height, so on ultra-wide screen monitors, a pane that should take up about a 1/3 of the window, ends up covering about 2/3 of the window.
I also love how even the Action menu is a hold over from some older UX ideas. There are two ways to bring up the help dialog now in all of the MMC apps, either with the Help menu, or via the Action menu.
But! At least they got enough attention to use Edge instead of the default browser if you try to open the "TechCenter Website" (a website that hasn't had that name in 8 years or so)
I assume they're building in the option to left-justify in case this move turns out to be another Windows 8 cock-up of a UI experience. I remember MS executives being "excited" about Windows 8 as well, it means little to nothing to me that Satya is excited about Win11.
"Placing layout elements on the four edges of the screen allows for infinitely large targets in one dimension and therefore present ideal scenarios. As the user's pointer will always stop at the edge, they can move the mouse with the greatest possible speed and still hit the target. The target area is effectively infinitely long along the movement axis. Therefore, this guideline is called “Rule of the infinite edges”. The use of this rule can be seen for example in MacOS, which places the menu bar always on the top left edge of the screen instead of the current program's windowframe."
[0] https://en.wikipedia.org/wiki/Fitts%27s_law#Implications_for...
Your whole comment also rings true when "design" and "designers" are replaced with "software" and "programmers".
I'm half joking but honestly I don't know why they bother with this. And for whatever reason, it gets under my skin and feels weird.
I am specifically referring to Google.
Businesses are great at iterating to find out just how much customers are willing to put up with in quality reductions before they actually leave, and also great at putting up barriers to shift that tipping point further in the company's favour. It turns out people will put up with a lot. Even stuff they hate.
We have the technology and ability to create things that are far higher quality, but it's usually a losing proposition from a profit-seeking perspective.
It's just the same old "worse is better" story.
(This is just a tangential thought, not some kind of disagreement or rebuttal.)
Users who have the choice will switch eventually, whenever they get the chance, they will never come back and they will hate you and share their discomfort. This will lead to scales being tipped against you wherever possible.
Now, you can still build a hard to avoid product and make a ton of money from it (Microsoft), so it‘s still not a losing strategy.
So here I am just begging companies to stop building terrible products because they make people miserable.
You can also build a high quality loved product and the effect above will reverse, but probably not at the same price (Apple, Jetbrains).
For a long time, the "Install Font" dialog was unchanged from Windows 3.0, with a tiny little folder tree view meant for 8.3 character file names and a drive picker button...
Some googling reveals they cleaned these up around 2015: https://arstechnica.com/information-technology/2015/09/windo...
To be fair, the last consistent Windows UI was probably Windows 3.1. In hindsight, it looks is incredibly cohesive and functional. Swap out the font (MS Sans Serif, especially bold, looks pretty bad), make the graphical components vector-based, and it would still look great today.
I still love elements of 7 and 10, but honestly would have been totally fine if 2K or XP were the final themes. Imagine if after all this time, the only way to date a Windows installation was by subtle design variations of the window title bar. Such bliss! Although of course, I am glad for many of the changes made during the mobile/touch revolution.
I wonder if the tide will ever turn on UX ideologists. Chased out of the industry like the witches and warlocks they are :)
https://old.reddit.com/r/Windows11/comments/o2a0kp/there_are...
There were further changes and inheretences from within each of those environments as well.
It was possible when using the application to recognise where and how various components and features originated and what platform(s) they were developed on or for. Even some 50 years after the first release, this can be determined.
As I came to use Unix and Linux more heavily, I noticed the same trend in various applications, both command-line (GNU and BSD userland, MVS JCL relics such as "dd", and others) and graphical. Various X11 and graphical toolkits became instantly recognisable, and though the appearances (and often feature locations and implementations) were often wildly inconsistent (Xt Intrinsics / Athena scrollbars, anyone?), once the contexts were known, the visual indicators made clear "oh, this is an Athena app, this is a Motif app, this is a gtk app, this is a KDE app", or singletons (Netscape / Mozilla / Phoenix / Fireox, StarOffice / OpenOffice / NeoOffice / LibreOffice, Applixware (remember that?), etc. came to be known quantities. Various JS toolkits and Electron apps are probably the current version of this.
I've (mostly in jest, though possibly more seriously with time) had the tag "technological archaeologist" in various online bios. That traces directly to my experience with tools developed over a number of different platforms or tools. Or simply the influences of time and trends or fashions.
Microsoft Windows at about 45 years of age now has its own design legacy and archaeological strata.
There is also a Twitter thread that notes what got lost over time - especially separation and contrast. https://twitter.com/tuomassalo/status/978717292023500805
Back when ads were actually a different background color on Google, I suspect they A/B tested background colors right up to the point that they disappeared on cheap TN laptops. I experienced this first hand when helping a friend with their laptop 5-10 years ago, and they clicked on an ad by mistake. Turned out that the ad background turned white at normal laptop viewing angles.
I'm always wondering whether my preference for this more "traditional" design paradigm just comes from using Win32 in my formative years or some objective difference of quality.
Anyone who shares the sentiment might want to check out the Chicago95 theme[1].
~2T$ and these jokers can't figure out how to reasonably update their kludgy mess.
(sorry for the rant, but this update crap killed a half a day of my non-profit volunteer time and is still unresolved)
For example one application in last 15 years: https://sciter.com/from-skeuomorph-to-flat-ui-evolution-of-o...
But to do the same on OS level - hundreds of different apps and applets ... That's Sisyphean task to be honest.
We should be lucky that old stuff is still working and API that appeared in Win 3 is still with us.
Actually that is not just Windows problem. On Linux, for example, all these utilities were historically console UI applications that are more "UI conservative" but even there - whole zoo of different approaches...
Building text-based tools is much easier than building GUIs on Linux because you have to target a specific GUI architecture like X11 / Wayland, and then you also have to think about fitting in with whatever window manager the user uses; GNOME / KDE / whatever.
On Mac or Windows, you build a GUI using the vendor's tools and you're golden. No need to worry about how the user is getting windows to show up on their screen because every user is using the same software to do so. For similar reasons, a lot of software just says screw it and targets Ubuntu only so they don't have to support your weird configuration on any other distro.
Upside, some of the legacy systems I wrote 20 years ago are going to look modern again!
What saddens me is that this steers the whole design process. You create a thin candy coating over the system to appeal to this audience, but at the same time, that clogs up established workflows and creates an inconsistent mess for more experienced users who have to work with both new and old UX flows.
Maybe we need to simply own the inconsistency. Build the shiny new experiences as a seperate flow, and allow users to migrate towards more traditional, powerful tools with the old UI conventions. Something like the manufacturer-provided shell you'd see on a late Windows 3.1 PC, where eventually you outgrow it and switch to using Program Manager.
Bonus points had actually updated them to the new design language (god fucking damn it).
Breeze cleaned things up a bit, but almost all the apps have an „I made the UI in 5 minutes before I fall asleep“ vibe (namely because the spacings are all weird).
To be fair: That is very consistent.
Personally, I think this is actually good. Consistent and Productive Design, especially on the level of patterns across an entire operating system of both first and third party applications, is an insanely difficult problem. This means one absolutely needs to bring in the consideration of resource allocation. Its not possible to do everything exactly the same; in fact, a related but incorrect argument may be that its not possible to do everything exactly the same on Day 1, but because "Good Design" is a moving target, its actually really difficult to reach that goal in any capacity whatsoever.
Inconsistent design, like this, tells me that it isn't a resource allocation priority for Microsoft. Thus, those resources are most likely diverted to more functional aspects; getting it working, faster, more consistent behavior, broader and deeper feature sets, etc.
This is the right trade-off for Windows. One can point to MacOS or iOS and see a much more consistent design language across first-party apps, as well as pretty strong adoption of this design language across third-party apps, but the cost of this near-perfection is abstracted away. Its easy to see inconsistencies in design; its much harder to speak in aggregates about obscure software issues, missing features, delayed releases, etc. Strongly consistent design, in the face of these issues (many of which are unproveable externally) may actually be the right trade-off for MacOS and iOS; Apple is a far more design/PR/marketing driven company, and this guise of "everything is engineered and under control" may actually be materially important for their brand.
Windows is different. Moreover; it should be different. The fundamental idea that an entire operating system needs a cohesive, strongly consistent design language is one that Microsoft has tried to push several times, but one which hasn't even seen internal adoption, let alone external. One can blame this on the design languages being bad, or their tooling being bad, or anything, but at the end of the day its still the most popular non-server OS in the world (or is Android bigger now? Well, its the same argument there too). Conforming to any central design pattern isn't a priority for Windows users. There's no physical law of the universe that OS-wide design languages are a naturally good thing; in fact, I would argue that design languages shared between many domains of applications may fundamentally fail to account for the wide variety of interaction patterns within every domain, and thus as a software platform increases its complexity of services offered, domain-agnostic design languages naturally begin to fall apart. They may actually be Generally Bad, though I only feel comfortable asserting with any certainty that they're probably not Generally Good or Bad, and there's room for different platforms to try different things.
Design consistency helps with that, or rather, design inconsistency hinders it. I sense stockholm syndrome. Windows would not lose anything by making their design language consistent.
Edit: I meant "Continue this thread," not "View rest of discussion."
This post forces you to use the app to see any of it period, or returns you to /r/popular. First time I’ve ever seen it as well.
I guess this is a trend. I wonder if it's affecting influencers' business.
Guess I don't get to see Instagram pages anymore. Sad thing is many small businesses use Instagram for their "website", there's a few around me that I haven't checked out because I can't see their "website" on Instagram.
> I wonder if it's affecting influencers' business.
HN is a self-selecting bunch. The vast, vast majority of people that care about influencers are logged in all the time anyway.
(just change www. to old. or i. for mobile layout)
I guess the same people who applaud each time when Federighi anounces the redesign of the macOS trashcan icon.