The weird world of Windows file paths (fileside.app)

Article summary

The article discusses the complexities of Windows file paths, including absolute and relative path formats, disallowed characters, and length limits. It also explores the different types of paths, such as drive paths, UNC paths, and device paths. The article highlights the quirks and nuances of Windows file paths, which can be confusing for developers and users alike. The author's goal is to provide a comprehensive understanding of Windows file paths, which is essential for building robust and compatible software.

Main themes

• Windows file paths
• Serial ports and device management
• Unix vs Windows
• PowerShell and scripting
• Industrial automation
• Device enumeration and registry management
• File system quirks and nuances

What commenters say

• Windows file paths are more complex and quirky than those in Unix-derived systems, making them challenging to work with.
• The use of USB serial adapters can lead to issues with COM port assignment and device identification on Windows.
• Some developers prefer working with serial ports on Linux due to its more straightforward and predictable approach.
• The Windows registry can become bloated and slow down device enumeration if not properly maintained, especially in environments with many devices.
• PowerShell is a significant improvement over batch files and is a viable option for scripting on Windows.
• The assignment of COM ports can be problematic, especially when using USB serial adapters, and can lead to issues with device identification and communication.
• Windows' approach to device management and file paths can be frustrating and time-consuming, especially in industrial automation environments.
• The ability to rename open files is a notable difference between Windows and other operating systems, with Windows not allowing it.