[Reebles]

Not sure why Bram doesn't believe that removing support for obsolete OSes such as MS-DOS, Amiga, and BeOs helps with Neovim's goal of simplifying the codebase and maintenance. Are there even any actual users of these systems that are disappointed that they won't be able to use neovim? If they're satisfied on those OSes surely they'd be satisfied with legacy vim.

[johncoltrane]

That's not what he said. He said that Neovim's goals could be achieved without cutting out features and removing supports for exotic OSes.

[coldtea]

>He said that Neovim's goals could be achieved without cutting out features and removing supports for exotic OSes.

That's the same as what parent said.

Neovim's #1 goal (from the webpage) is: "Neovim is a project that seeks to aggressively refactor Vim in order to simplify maintenance and encourage contributions". And other goals including adding new features for the future.

You might not 100% HAVE to drop "supports for exotic OSes" for that, but is extremely logical, and very much helpful in that direction.

Anything that reduces code size makes it easier for maintanance. You don't want to have to check how things play for those IFDEFS for Amiga OS when you write code for 2014.

[SamReidHughes]

Are you familiar with Vim's code? How is support for those OSes making things substantially more complicated?

[ggreer]

Are you familiar with Vim's code? Just look at all the OS-specific files in the source tree[1]. Not only that, there are ifdefs-galore in the shared code. RealWaitForChar is over 400 lines and contains 41 ifdefs.[2] Many are for long-dead features or platforms. That function just waits for user input, but it has to be ridiculously complicated to account for platforms without basic functions like select(). The infamous eval.c starts off with ifdefs for Amiga, VMS, and Mac OS Classic.[3] Neovim has ripped out tons of this stuff, and it's drastically reduced line count.

1. https://github.com/b4winckler/macvim/tree/master/src

2. https://github.com/b4winckler/macvim/blob/master/src/os_unix...

3. https://github.com/b4winckler/macvim/blob/master/src/eval.c

[coldtea]

You don't have to be familiar with Vim's code to know that having support for obsolete OSes makes the code substantially more complicated.

[teacup50]

Bulk churn is the kind of easy task that gives the impression of progress while providing very little actual value.

In 8 months, here's what NeoVim has done:

1) Reformatted all the code.

2) Deleted a lot of working, old code.

3) Raised a good chunk of cash.

4) Published a very shiny website.

5) Released nothing.

There's nothing wrong with simplifying a code base, but if you run around trying to do that independent of any reasonable technical direction, you're just making noise.

Given that NeoVim's technical direction is extremely poorly considered (while also disparaging Bram's work), I can't help but think highly of Bram for being polite -- at all -- to such a disrespectful fork.

[ggreer]

Your comment seems to consist of some things that aren't true, and some true things accompanied with baseless insinuations.

1. The code was reformatted because Vim's codebase is a mess. It mixes tabs and spaces willy-nilly. It uses different indentation rules in different parts of files. These issues may seem cosmetic, but they make the code harder to follow and increase the likelihood of bugs. Indentation can be especially misleading when control flow lacks braces (a common occurrence in Vim). The change didn't require much effort and it made it easier for people to contribute to Neovim.

2. Actually, quite a bit of Vim's old platform-specific code is broken. It's just that nobody uses an SGI IRIS or Amiga, so nobody complains about it. In some cases, Neovim removed ifdef'd code that could never possibly be included[1].

3. People have donated less than $40k to Neovim. That's not even the salary of a single developer for the 8 months it's been around. The contributors aren't in it for the money. They simply want to build a great editor.

4. A very shiny website? It's just static pages hosted on Github. If you look at the commit history[2], you can see it's insignificant compared to work done on the Neovim codebase.

5. Nothing? There's an entire repository of working code. Right now you can clone Neovim, compile it, and it will run almost all Vim plugins without issue. The team is very conservative about declaring software stable. They may not have a tagged release, but to call the existing work "nothing" is unreasonable. It's at least as stable as Atom.

You also neglected to mention all the other work done on Neovim, such as replacing ad-hoc cross-platform compatibility and event handling with libuv. Then there's the improved plugin APIs which allow features that aren't possible in Vim.[3] And of course, plugins can be written in any language. No more VimL shims needed.

Lastly: Disparaging? Disrespectful? It's hard to find any criticism the Neovim contributors have made towards Bram or Vim. They like Bram. They like Vim. Thiago tried to contribute to Vim multiple times, but was discouraged or ignored.[4][5] Instead of complaining or giving up, he and the other contributors are trying to improve the editor and the community around it. There's no malice or greed involved.

1. https://github.com/neovim/neovim/pull/814

2. https://github.com/neovim/neovim.github.io/

3. https://github.com/benekastah/neomake

4. https://groups.google.com/d/msg/vim_dev/QF7Bzh1YABU/02-YGr7_...

5. https://groups.google.com/d/msg/vim_dev/65jjGqS1_VQ/fFiFrrIB...

[kev6168]

How is forking an open source project disrespectful? For the past eight months I have only seen Neovim folks being very professional, open, and quick to respond to user input. They have been keeping their heads down quietly working on extremely hard problems.

Natively supporting Lua/LuaJIT and Python in writing asynchronous plugins, this alone is worth the wait. I am willing to give them A LOT MORE than 8 months if they can pull just this single feature off.

The request for Python integration has been sitting at the top of Vim's voting list for many years. It must be a very very difficult task, otherwise it could be done years ago. http://www.vim.org/sponsor/vote_results.php/

Other than the new plugin infrastructure, Neovim's GUI and embedding systems will be awesome. Anyway, I applaud people who explore and try to make progress (like from Vi to Vim, a natural process). In the mean time, I am happily using Vim which is both extremely powerful and stable.

TL,DR; I can wait.

[jballanc]

> 5) Released nothing.

I've been tracking the neovim repo for a while, and my feeling is that they could have easily made a couple of releases with stability matching some other notable projects, but they have intentionally chosen to be conservative and wait.

If you want an example of one area where there has been work and improvement, check out the Wiki page on the updated clipboard integration: https://github.com/neovim/neovim/wiki/Python-plugins,-clipbo... . Yeah, it's different, and not yet as capable as Vim's built-in clipboard integration. But if they are headed toward a goal of more generalized integration points, then this is a strong step in the right direction.

[sondr3]

I don't really see any problems here, they haven't made any promises either to release anything either before they are up to speed with where they want to be, just looking at their Github repo shows that there's a lot of activity going on. I'm really looking forward to seeing where they are going. In eight months things may have changed drastically, who knows, but I think that NeoVIM is going to be great. Besides, this is a bit like complaining about vim being a fork of vi, it's how things goes with open source software.

[dennyabraham]

neovim is in the process of several major under-the-hood refactorings to enable larger scale changes. If it's not immediately apparent to you what the team is working on, you can see the project goals and progress thereupon on the project tracker.

https://waffle.io/neovim/neovim

[sbilstein]

I often refer to these two pieces when debating rebooting a project from scratch:

Joel Spolksy Things You Should Never Do Part 1 http://www.joelonsoftware.com/articles/fog0000000069.html

Darmesh Shah How To Survive a Ground-Up Rewrite Without Losing Your Sanity (a response to essay #1 13 years later) http://onstartups.com/tabid/3339/bid/97052/How-To-Survive-a-...

It's not always cut and dry when you should start over, but if you are make sure you are doing it in a way that starts presenting customer/user value ASAP.