For what it's worth, it works properly on cygwin (and certainly the linux subsystem too). I know that the author uses it on cygwin too so there is at least some guarantee.

It is a sensible decision, as it will focus doing things right on that particular paradigm: UNIX.

For example, this means that plugins trying to extend grammar analysis, will primarily try to rely on their already existing parsers and tools via the command line. This means a streamlined process to create plugins / extensions to the editor, and the function of the editor is well defined.

To be fair, vim is somewhere around a 4th class citizen on Windows. It works, but it ain't pretty.

Plus, with the unix subsystem (minus bugs) you can still run this in Windows. That still amazes me.

What exactly isn't pretty about vim (specifically gVim) on Windows?

The default fonts, the menus, the menu icons, the font rendering, the inability to use many plugins....

It blows my mind that people want Unix tools in a non-unix environment.

With that said, Windows is working on that embedded native linux thing, so i imagine it will work there.

Actually it does work there.

Yeah, God knows that I only learn tools that I can use at any time, anywhere, on any hypothetical machine. Not the machines I actually own, but ANY MACHINE EVER.

This smells like confirmation bias to me.

> "Yeah, God knows that I only learn tools that I can use at any time, anywhere, on any hypothetical machine. Not the machines I actually own, but ANY MACHINE EVER."

This is a straw man argument.

I already use perfectly good multi platform editors like Sublime and Vim and I have Emacs as an option, although I have not used it much. There is a significant investment in time required to use a modal editor like Vim (and apparently Kakoune) at even close to a decent level. I simply prefer to not have to change editors every time I change platform, since an editor is a tool I use a lot and I have the option to not be restricted by platform limited editors.