What not to port to ReactOS

From ReactOS Wiki
Revision as of 19:04, 27 September 2018 by PurpleGurl (talk | contribs) (Addition)
Jump to: navigation, search

This is a place for sharing what Windows features we don't want in ReactOS, or at least not by default.


  • Removal of animation -- In NT 5.x, MJPEGs and animated GIFs would animate correctly when set as wallpaper or viewed in Windows Photo Viewer. In NT 6.x, they did not.
  • Inability to save to the root folder of the system drive -- In NT 5.x, users could edit the contents of the "Program Files" and "Program Files (x86)" directories. In NT 6.x, this is not authorized, even for administrators, which is a huge pain when developing game mods, or really just for anyone who wants to be treated like an adult and like the owner of their own computer.
  • Open With no longer remembering every program previously used -- In NT 5.x, the "Open With..." menu would remember EVERY program that you had ever opened a specific file type with. In NT 6.x, it's a gamble, though I suspect that it's based on which programs are installed vs. which ones are merely run as-is without needing to be installed.
  • Windows assuming what details you want about a file -- Many who use media files would still prefer the original sort headings such as Last Modified, Extension/Type, Size, etc. If you have a large folder of mixed file types, then you might not want Artist, Song Title, and other .MP3 tags as headings, or at least not the only ones. So if we include this, at least give the ability to disable this and let it default to the classical sort headings.
  • Poor extension and MIME handling
  • Taskbar no longer resizeable
  • Poor file searching -- Newer Windows versions started creating indexed databases of files. Older versions would do a complete crawl if you want. Understandably, part of the change was to make things more friendly for multitasking, since crawling is more disk intensive than reading from a single database. However, this often results in not being able to find things. Also, many users would rather crawl on demand rather than have a disk-intensive indexing service running in the background. This can cause gaming lags, for instance.
  • Blank desktop in Windows 10 when not running Explorer -- In windows 10 (?) the background image has now been tied into Windows explorer whereas it was previously independent of it. This means that when explorer.exe is not running the desktop is blank. This ties any look-and-feel into explorer's GUI and prevents you from running alternate shells that do not have the means to update the background themselves. Previously you could add a background, kill windows explorer and use alternate shell elements such as Rocketdock and Jetstart and have a usable desktop without explorer.exe running.
  • File 'discovery' delays -- When you try to perform a copy it often takes longer for Vista+ to discover the files than it does to actually copy or move them. Workarounds include using the Command prompt and using XCopy, manually deleting files using the Del command, etc.
  • Inability to hold window focus -- Allowing windows to pop over a password dialog could theoretically compromise the password.