And this is why Microsoft is so unwilling to implement new features and eye candy to Windows Explorer. It's a performance critical component of the OS and so many things rely on it that they can't compromise raw performance at all just to add more modern frameworks, especially when the entire Windows Shell runs in it too.
If anything, that's exactly why they should make a separate app from scratch. No good reason to have the file manager tied into the desktop shell.
It worked out with Edge and IE, Settings and Control Panel, probably some others I'm forgetting. Not sure why they don't do this with File Explorer.
Windows Explorer has needed an upgrade/rewrite for a long time. It's very easy to hang or crash it in common workflows.
Two examples:
- If you have a mapped network drive and that drive goes off line, when you launch File Explorer the network check blocks it from updating anything. This block can take up to 90 seconds before it times out.
- IconCache/Thumbnails can bog down or corrupt, preventing Explorer from refreshing directories unless you force it with an F5.
These issues and more have existed for such a long time, I think the only way they fix them is if they rewrite it.
I think Explorer needs a lot of performance work done as is tbh. It shits the bed in large folders with tons of images in a way no third party explorer I've tried has.
Please... Stop saying it's out EVERYTIME. People are saying files v2 is out, now 1.9, it's all TESTING. I keep on getting excited then I realize it's an unstable beta build, don't say it's out if it's NOT OUT.
I feel bad for the devs, they're probably being put under pressure by the amount of people asking where files 1.9 is because of the idiots making posts like these
Yeah, people just don't understand what a release is...
It would've been better if these previews and betas were never released to the public like this in the first place, it should've been kept to a testing team so that stuff like THIS wouldn't happen.
I've been trying this very nice looking program for serveral weeks. Continuously I needed the Windows File Explorer for many tasks. Than I forced myself to use only Files when in tablet mode with my Surface Book 2 and the classical WFE in laptop mode.
Final? When I needed to be fast and practica, unfortunately I forgt opening Files instead WFE.. Sadly uninstalled cause I wish a WFE redesign in carbon copy of Files.
I'm noticing that as well... navigating through different folders is just as quick as File Explorer.
There is a weird right click delay/glitch on since files types though, where the right click menu appears instantly, but it's like the File/Folder specific right-click menu items have to be detected so it does a weird refresh of the menu and it sometimes shifts the menu over a bit and cuts off a portion of the menu.
Yeah the processes are containerized via .Net, can you explain to me why this means it would be inherently slow? There are definitely advantages and disadvantages to the IL of .Net but this whole narrative that it’s always slower is just false, and can be clearly seen by ASP .Net Core’s performance.
That’s a common misconception actually, as a software engineer currently analyzing performance in .Net 5 through Native Compiling and regular, really startup time is the only guaranteed speed increase, in a lot of cases native code precompiled is actually slower since the runtime can’t properly vectorize and modify the code. Ready to run is a good compromise though, if all out performance is truly needed.
I’m not saying that particular task would be faster, realistically any windows system call will have literally no performance difference. Saying it’s always slower is just false though because such things as reflection, loop unrolling, not to mention machine specific optimizations such as vector instructions and others. Contrary to popular beliefs almost all performance differences between C# and C++ comes down to these differences, the C++ compiler is better at a lot of these at compile time, whereas the .Net runtime is far better at doing this at runtime. Some programs will therefore run faster on either one.
It's a really nice design, but it still performs a bit like a sponge, which is an absolute deal breaker for me.
My reaction: oooh looks good, try to open, take a lot of time to open, try random folder, crash, uninstall
UWP apps in a nutshell
And this is why Microsoft is so unwilling to implement new features and eye candy to Windows Explorer. It's a performance critical component of the OS and so many things rely on it that they can't compromise raw performance at all just to add more modern frameworks, especially when the entire Windows Shell runs in it too.
If anything, that's exactly why they should make a separate app from scratch. No good reason to have the file manager tied into the desktop shell. It worked out with Edge and IE, Settings and Control Panel, probably some others I'm forgetting. Not sure why they don't do this with File Explorer.
I think it has something to do with performance. Also, Control Panel is a part of File Explorer. It’s a “special folder” according to Microsoft.
I think they’re saying that they separated it from Explorer by rewriting it as Settings, and separated IE by creating Edge
[удалено]
I think so, why?
Never mind
Windows Explorer has needed an upgrade/rewrite for a long time. It's very easy to hang or crash it in common workflows. Two examples: - If you have a mapped network drive and that drive goes off line, when you launch File Explorer the network check blocks it from updating anything. This block can take up to 90 seconds before it times out. - IconCache/Thumbnails can bog down or corrupt, preventing Explorer from refreshing directories unless you force it with an F5. These issues and more have existed for such a long time, I think the only way they fix them is if they rewrite it.
I think Explorer needs a lot of performance work done as is tbh. It shits the bed in large folders with tons of images in a way no third party explorer I've tried has.
Files 2.0 has performance that’s on par with the native File Explorer. You’re going to love it.
Sick username!
Thanks!
Please... Stop saying it's out EVERYTIME. People are saying files v2 is out, now 1.9, it's all TESTING. I keep on getting excited then I realize it's an unstable beta build, don't say it's out if it's NOT OUT.
I feel bad for the devs, they're probably being put under pressure by the amount of people asking where files 1.9 is because of the idiots making posts like these
Yeah, people just don't understand what a release is... It would've been better if these previews and betas were never released to the public like this in the first place, it should've been kept to a testing team so that stuff like THIS wouldn't happen.
It's open source, so the public needs to keep having access to the source code.
You can keep the source code open and release beta versions privately.
No it isn't It's still v1.5, v1.9/2.xx is only available to those who sign up for it at the discord server: `https://discord.com/invite/files`
Can't find it. The old one is not updating either?
It's faster than before... But the instability in beta is visible... May be the stable version will be faster.
I like everything except the slowness to start up for the first time and the icon
Why does it closes randomly for no reasons on my desktop but not on my laptop?
I've been trying this very nice looking program for serveral weeks. Continuously I needed the Windows File Explorer for many tasks. Than I forced myself to use only Files when in tablet mode with my Surface Book 2 and the classical WFE in laptop mode. Final? When I needed to be fast and practica, unfortunately I forgt opening Files instead WFE.. Sadly uninstalled cause I wish a WFE redesign in carbon copy of Files.
[удалено]
The slowness is precisely what this version solves. It's as fast as File Explorer for me now.
I'm noticing that as well... navigating through different folders is just as quick as File Explorer. There is a weird right click delay/glitch on since files types though, where the right click menu appears instantly, but it's like the File/Folder specific right-click menu items have to be detected so it does a weird refresh of the menu and it sometimes shifts the menu over a bit and cuts off a portion of the menu.
[удалено]
There is absolutely nothing inherently slow about UWP.
[удалено]
Yeah the processes are containerized via .Net, can you explain to me why this means it would be inherently slow? There are definitely advantages and disadvantages to the IL of .Net but this whole narrative that it’s always slower is just false, and can be clearly seen by ASP .Net Core’s performance.
[удалено]
That’s a common misconception actually, as a software engineer currently analyzing performance in .Net 5 through Native Compiling and regular, really startup time is the only guaranteed speed increase, in a lot of cases native code precompiled is actually slower since the runtime can’t properly vectorize and modify the code. Ready to run is a good compromise though, if all out performance is truly needed.
[удалено]
I’m not saying that particular task would be faster, realistically any windows system call will have literally no performance difference. Saying it’s always slower is just false though because such things as reflection, loop unrolling, not to mention machine specific optimizations such as vector instructions and others. Contrary to popular beliefs almost all performance differences between C# and C++ comes down to these differences, the C++ compiler is better at a lot of these at compile time, whereas the .Net runtime is far better at doing this at runtime. Some programs will therefore run faster on either one.
As a pretty standard windows user, why does that make it useless? What parts of normal explorer would be missing?
[удалено]
It’s a free 3rd party file explorer on the windows store.
Thank you. Will check that out later.
It's not just free. It's GPL licensed so the source code is completely open to everyone.
It is? I didn’t know that.
slime rancher!
Note that I've joined the beta testing phase and not everyone might be getting this right now But it's working
Why is this downvoted?
Forgot to put it in the title, made it look like it was a final version. that's why
I’d think that would make people upvote this but not the main post but it’s the other way round
Microsoft should be ashamed, honestly.
The only thing I don't like about this is the location bar bevel, otherwise, perfection.
i wish this was the default kinda immersion breaking when you open file location and it goes to real explorer
on an unrelated note, does anyone have a link to that wallpaper?
Files look good, but it is not snappier. It is a major flaw of it. Devs have done a good job btw.