News for hackers. Stuff that matters.
Re:The Unix spirit set free: Plan 9 from Bell Labs (2006) [pdf] by laumars on Monday June 02, 2014 @08:46AM (#7833158)
NT might have system objects structured in a tree for privileged access, but it's not quite the same thing as having everything as a file system object that's transparently accessible by any application.

eg, you couldn't use Notepad to edit those NT objects, where as you could with Plan 9's design since.

Re:The Unix spirit set free: Plan 9 from Bell Labs (2006) [pdf] by frik on Monday June 02, 2014 @12:38PM (#7834358)
The problem is backwards compatibility. To make the code transition from Win16API to Win32API very easy in 1994-95 era Microsoft made several design decisions for Win32API, that don't make sense anymore - 20 years later.

Some of them are the limited MAX_PATH, which is defined as 260 characters, reserved characters in file names, 8.3 filename aliasing (fixed), etc. - see: http://msdn.microsoft.com/en-us/library/windows/desktop/aa36...

Unfortunately, the Windows shell (explorer.exe/shell32.dll & cmd.exe) are more limited than what you can do with Win32API. One can access the NT object tree from C/C++

You can use CreateFile(), ReadFile(), WriteFile(), etc. Win32API function to work on NT objects (not just files but real NT objects, the name is just inherited from Win16API) - http://msdn.microsoft.com/en-us/library/windows/desktop/aa36... , http://msdn.microsoft.com/en-us/library/windows/desktop/aa36... , http://msdn.microsoft.com/en-us/library/windows/desktop/aa36...

Some NT path examples:

  "\\.\PhysicalDrive2"  ...  opens third physical drive 
  "\\.\C:\"  ...  opens the file system of the C: volume 
  "\\.\COM1"  ...  opens serial port 1
  "\\.\pipe\pipename" ... opens named pipe
  "\\.\mailslot\sample"  ... open mailslot
  "\\?\UNC\server\share"  ... opens universal UNC path
  "\\?\C:\" ... opens C:, you can exceed the MAX_PATH limits
screenshot of WinObj that corresponds to the last example: http://s1.postimg.org/ckhs6xedr/ntobject.png

Instead of further improving Win32API, as they have done like ReadFileEx() (http://msdn.microsoft.com/en-us/library/windows/desktop/aa36... ), Microsoft toys around with several dotNet API layers on top of Win32API and now a WinRT API that stills sits on top of the Win32 subsystem. Windows NT would support several subsystems (like there are POSIX, OS/2, Xbox subsystems for WinNT/ReactOS).