4 ms·
The UNC paths in Windows are very much a Windows-ism. They work perfectly when you're in an all Windows environment, but there's no consideration to speaking n
by Mister_Snuggles 10y ago
The UNC paths in Windows are very much a Windows-ism. They work perfectly when you're in an all Windows environment, but there's no consideration to speaking non-Windows protocols.
The key problem I have with KIO is that it's doing something that should be done at a lower level so that every application can benefit.
As I see it, there are three classes of apps on Linux when it comes to file handling:
* Apps that can open remote files using one set of protocols (KIO-enabled apps).
* Apps that can open remote files using a different set of protocols (things that reinvent this wheel, like emacs in your example).
* Apps that can only work on local files.
So we get a situation where I can open a file on an SMB server using Kate, but I can't open the same file in Sublime Text. It makes for a terrible user experience.
The Mac makes it easy to mount filesystems, but it's kludgey compared to using UNC paths in Windows. This is the one feature that I really miss from Windows.
- thom 10y agoSure, totally agree that it'd be great if this was a low level feature of the OS that seamlessly integrated with any possible GUI for authentication from readline and up. But we could sit here all day and enumerate ways in which open source operating systems and desktop environments are less integrated than others. All I was saying originally was that KDE was the first Linux environment I used which came close to the level of broad support and integration you get from something like Windows, and in some cases it went beyond.
- stuaxo 10y agoIntegration is definitely an area where open source could do better, the freedesktop project is a step in the right direction, but we need more.