Forum Discussion
Tiago Freire
Aug 26, 2019Brass Contributor
Will Edge Chromium Browser have a Cloud-aware file manager? To coexist or supersede Windows Explorer
I was thinking about how Windows Explorer is limited and requires plugins for its cloud features. Being naturally web-aware, I think it could make sense, perhaps, to have Edge Chromium to have enou...
Elliot Kirk
Aug 26, 2019Former Employee
Hi Tiago Freire, we tried something like this in our Windows Tabbed Sets feature. I believe that the feature was eventually cut as it did not solve the problem in a sufficiently understandable way. Thank you for the feedback, and we will certainly capture it. Thanks - Elliot
Tiago Freire
Aug 28, 2019Brass Contributor
I believe that to have enough resources and the right hooks, to achieve the best results, it would have to be a concerted effort across teams, so it can become a significant upgrade to the Windows OS, leverage OneDrive for cloud sync in a smarter way, and be buddy-buddy with Microsoft Office as well.
MAX_PATH = 260 is a very important constant, deeply set in as the first block of a Jenga Tower, and will not move for the foreseeable future. It causes significant impact and ramifications towards many design choices and apps, and since backwards compatibility cannot be broken, I can only see that it must be worked around with other, more modern APIs. And along with this, bring a full-fledged cloud-aware file manager.
Just like eventually MS makes choices to supersede older code bases for more modern ones, I see from my humble point of view of a consumer that the simplest approach in this case would be to provide a modern file manager based on modern technologies, while retaining the old one for compatibility with less fear of tripping over old code and breaking backwards compatibility because they are separate code bases.
MAX_PATH = 260 is a very important constant, deeply set in as the first block of a Jenga Tower, and will not move for the foreseeable future. It causes significant impact and ramifications towards many design choices and apps, and since backwards compatibility cannot be broken, I can only see that it must be worked around with other, more modern APIs. And along with this, bring a full-fledged cloud-aware file manager.
Just like eventually MS makes choices to supersede older code bases for more modern ones, I see from my humble point of view of a consumer that the simplest approach in this case would be to provide a modern file manager based on modern technologies, while retaining the old one for compatibility with less fear of tripping over old code and breaking backwards compatibility because they are separate code bases.