[hhjj]

There are still a lot of bugs, features not working at all in windows. So a feature that works but slowly in extraordinary (for most users) conditions is not prioritized.

If you want a bug-free os, you'll pay an extreme price in features or in dollars.

[baobabKoodaa]

> There are still a lot of bugs, features not working at all in windows. So a feature that works but slowly in extraordinary (for most users) conditions is not prioritized.

Please don't pretend like Microsoft has rationally prioritized the feature/bug work on Windows. Microsoft is spending resources pushing ridiculously niche use cases like "3D Objects". Microsoft is also doing a bunch of duplicate work, for example, maintaining 2 different UIs for Control Panel even though the old one was fine. Maybe it's time for Microsoft to stop the endless re-designs just for the sake of "new is better", and maybe focus on fixing bugs?

[tom_]

You may be correct in the larger sense, but there will be multiple teams working on Windows, with non-interchangeable staff. Assuming anybody found this bug before, somebody on the Explorer team almost certainly will have rationally prioritized it.

[lupire]

Why? Would someone rationally get a bonus for fixing this instead of whatever quarterly promise they made to their boss? What's rational about fixing a bug that isn't threatening revenue?

[tom_]

They wouldn't. The person rationally prioritizing this bug will have put it somewhere down the bottom of the list. And that's how we find ourselves here, with the issue unfixed.

[kasabali]

> If you want a bug-free os, you'll pay an extreme price in features or in dollars.

It isn't like Windows division doesn't make billions of dollars every year. Lack of resources is hardly an excuse.

[BillinghamJ]

I suspect in both features & dollars!