Hacker News new | ask | show | jobs
by tinco 4496 days ago
Well that does it I'd say. With such a negative attitude, who wants him on the team anyway? What the advantages are? They're clearly laid out in the project.

Seriously, screw that guy.

edit: Yes I know who 'that guy' is and it's great he's been working on Vim for all these years, but he certainly has his head up his ass if he thinks Vim users would not benefit from some big refactorings, a more accessible code base and some dropped platforms. If all those Amiga programmers love Vim so much, why would they be disappointed with an eternal Vim7.4?

It's not too late for Vim to lose the editor wars.

2 comments

Seriously, totally uncalled for.

I would say that for the majority of people Vim is just working fine.

That 'guy' has been maintaining Vim for years and all he asks for is to donate to his charity.

Also, did you read his response? He doesn't say don't do it. Just wouldn't be easy and some current functionality may be lost. In his mind, it would be better to work on the current code base and do small changes. I would say that's an entirely reasonable response.

It's comments like this that turn people off from working on open source.

I still have yet to see these concrete user benefits.
The benefit is indirect rather than direct, as in the user benefits from the increased availability of plugins/guis since they would be easier to create. Also vim lacks lots of very simple but essential features of modern code editors simply because it lacks the graphical capabilities to do so (an example would be displaying the documentation of some method you are autocompleting, something which I have never seen in vim and which I actually believe is impossible).
> an example would be displaying the documentation of some method you are autocompleting, something which I have never seen in vim and which I actually believe is impossible

For python at least, having 'preview' as part of your completeopt has it display the docstring of what you're completing. And :h completeopt suggests that's intended behaviour for all types of completion (where it makes sense), too.

Yes, but currently retrieving that info is done synchronously, so it might slow down things. Under neovim's model, this can be done more efficiently.
If it makes vim plugins less painful it has a huge benefit for me. I run almost completely vanilla vim in part because the plugin system is so awkward.
You can not see the concrete user benefits of a modernised, cleaned up code base ? Maybe you need to look harder.
"Modernized" means JSON-rpc IPC? If so, no thanks.