**(1)** I think both nimedit and aporia were small experimental projects that didn't get very far and that no one really uses. [More than half](https://nim-lang.org/blog/2018/10/27/community-survey-results-2018.html) of Nim devs use [vscode](https://code.visualstudio.com), which has by far the best [support](https://github.com/pragmagic/vscode-nim). You can see from [YouTube videos](https://www.youtube.com/playlist?list=PLXIivpcMlfwAevvA4IvLIiYOujqSuyyKY) that both [Araq](https://www.youtube.com/channel/UCAIXKsgiEkRjwlNgduABgmw) (our BDFL and author of nimedit) and [Dom](https://www.youtube.com/user/d0m96/videos) (author of aporia) use vscode.
**(2)** You need to install a C compiler and properly configure Nim regardless of which editor you use. **The simplest way** , as the [Windows download page](https://nim-lang.org/install_windows.html) says, is to **run "finish.exe" to install MinGW**, update your PATH, and make sure your command prompt got the PATH update. Using Visual C++ compiler, LLVM, etc is possible - but more complicated. As an alternative you could also compile Nim in [WSL](https://docs.microsoft.com/en-us/windows/wsl/install-win10), which gives you all Unix tooling but slightly slower Windows performance. **(3)** If you going to use a 32-bit VS2017 (as the "Program Files **(x86)** " path suggests), you must also use 32-bit Nim ("x86", not "x86_64").
