If we followed that idea though (keep it as it has been for 30 years) then Google Drive or iOS would have you browsing through hierarchical folders like Windows Explorer.
I've had many non technical people ask me how to create folders in those systems...
People can live with a flat file structure; Early versions of DOS were like this. Maybe we should go back to line editors too... So much prettier and simplified! No menus or dialogs! You don't even see a pageful of content at once! Just a blinking cursor and some brief commands. No messy interface...
It's a definite balance though, is my point. You have to make these determinations all the time while making consumer-facing software.
For example, I'm making a 'Newsfeed for Twitter' right now (top tweets people you follow have liked/shared) and people I show it to want keyword muting so the feed isn't dominated by Trump news. From a UX perspective I really resist adding keyword muting. Instead I added a 'Tailored' mode that shows top items your friends are talking about that aren't being talked about across the network.
Similarly I had "Top -> 12 Hours | Day | Week" and to remove the "12 Hours | Day | Week" submenu, I created a feed that algorithmically balances popularity and recency.
So I'm saying these choices are ever-present when making software. Some moves like Apple removing the 'Escape' key seem like random silliness but some hard choices are important when making a good product.
That would be amazing. As it is now, I have to search for stuff and I no longer have a clear picture where stuff is and just how much stuff I have. Therefore, when I'm searching for a document and it does not come up, I'm not sure if it's because it doesn't exist, or just because I did a wrong query.
Yes, an explorer.exe interface for Google Drive would be a huge win. That's also why I avoid using it, and keep everything I can in Dropbox instead.
I think they changed because search became affordable enough to become a valid strategy, not because some genius figured out people are confused by folders.
It changed the up-front effort in FILING for a greater but later effort in FINDING (assuming keyword search).
To compensate, of course, users can invest a greater upfront effort in NAMING and TAGGING.
Several decades ago, I made filing mostly go away by creating files in the directories in which they would eventually be filed. This requires the ability to create nested subfolders, without which no substantial filing system is viable.
There's probably an order of magnitude at which hierarchical filing systems become the only rational approach (depending on the material). It might be 1,000 in some cases, or 10,000 in most cases, and maybe 100,000 in a few cases.
