Yeah.

> The likelihood of any legal restriction was probably close to zero - it’s only from today’s era of hyper-regulation that we might even imagine something like that.

Normally I'd agree with a statement like this. Except this is a very specific case.

That lawsuit happened in response to Window 2.0, and the fact that they adopted overlapping windows in 2.0 strongly suggests that Microsoft did not think that the change would lead to legal action and was taken by surprise.

Yeah, it’s interesting how the desktop metaphor evolved over time but increasing display size and the ability to have multiple workspaces surely is a huge part of what makes tiling almost work.

And tiling still largely doesn't work with small windows.

You can tile windows in Windows as well with the windows key+ arrow buttons.

The default is just left, right, and top, bottom but if you install Power Toys and use Fancy Zones you can customize the zones https://learn.microsoft.com/en-us/windows/powertoys/fancyzon....

There’s also Crop and Lock which can help you cut out extraneous parts of certain windows

https://learn.microsoft.com/en-us/windows/powertoys/crop-and...

>"when Gates saw the Xerox machine, the display had no overlapping windows". So M/S cloned it as he saw it. Once M/S W1.0 was developed he saw the demo again and was surprised the windows overlapped.

Microsoft had Apple Lisa's in-house, and Charles Simonyi in person direct from Xerox PARC, and worked on pre-release Macintoshes in coordination with Apple to develop Microsoft Word for the Mac, all well in advance of any MSWindows development. There is no way the story is as simple as the above.

They are a bit out of fashion these days.

The main use-case was multiplexing terminals and, after tmux provided a solution that was usable by normal users, it seduced people away.

Also, mouse-first tiling was introduced on Windows so nowadays it is almost universal to have a degree of tiling.

They are nice for terminals and browsing properly-written web pages but for anything with an aspect ratio or a fixed size they are clumsy.

Modern tiling-wms often have a floating mode so the distinction is more keyboard-wm vs mouse-wm.

To be fair, in the era when resolutions like 512x342 or 640x480 were common overlapped windows were quite useful.

Most of the time, I want the active application window in the middle of the screen, but not necessarily filling the whole screen or the whole height, and also not necessarily centered. The window position and size depends on its contents, what sidebars it has, and so on. This inherently leads to overlapping windows. I use a tool that automatically moves and resizes windows to the application-specific desired position, while also having the ability to arrange a split-screen view using keyboard shortcuts when needed.

The primary value of overlapping windows is spacial memory: you remember where a given window is positioned on a 2D surface. The moment I grasped this I had the “oh boy I sure am glad this window partially overlaps this other window.”

(At one moment, I used to have around 20 windows on a single desktop, on my MacBook with 125% DPI. Too much but possible. Now I keep only 6-7.)

This is not to say that dynamic window management is worse. Far from it. But it excels at this: dynamic, rapidly changing environments, where at almost any given moment something is either opening or closing. This is usually the case with specialized programs like web browsers or IDE, but not with the main system WM.