It probably goes against Vim tradition, culture and freedom to choose, but I wish they added even more built-in features (like Helix) that are currently implemented in competing and sometimes brittle plugins and have to be put together into also competing vim starter packs and distros of plugins and config files just to have a modern setup out of the box.

▲

gorjusborg 2 hours ago | parent | next [-]

I agree in principle that absorbing the best from the ecosystem is good. However, anything pulled into core should have a long lifetime and be considered part of the API. This deserves careful consideration, and plugins work really well until it is clear there is a reason to pull something in.

	▲	Blackthorn 44 minutes ago \| parent [-]
		Not to talk about the other side of the holy war too much, but one of the things I appreciate about GNU ELPA is it's treated as part of the Emacs distribution and needs to follow all the rules of Emacs proper as a result.

▲

bheadmaster 2 hours ago | parent | prev | next [-]

This is what happened with the Language Server Protocol.

Prior to 0.9 (if I recall correctly), you had to install a plugin to be able to interface with LSP servers, and in 0.9 they integrated the support into NeoVim itself.

	▲	shmerl an hour ago \| parent [-]
		Would be nice to also have such support for DAP, though nvim-dap is doing a good job so far.

▲

augusto-moura 3 hours ago | parent | prev | next [-]

I believe neovim started as a fork specifically to implement features like LSP support and package management, VIM eventually also caught up. But i don't believe anything is out of the table, or against Vim tradition. Which features do you want to see built-in, specifically?

	▲	QuantumNomad_ 2 hours ago \| parent \| next [-]
		I’m also pretty sure that on an episode of The Standup, one of the Neovim core maintainers TJ DeVries (Teej) said that it is a good idea to prove new ideas in the form of a plugin rather than submitting pull requests for Neovim itself with new ideas that have not yet been tested out and proven in the real world. Implicitly implying that indeed Neovim is open to bring features from plugins into core Neovim itself, if they are proven to be useful for a lot of people. Unfortunately I don’t remember what episode it was or even if it was specifically on an episode of The Standup, or if it was some other video that he and ThePrimagen did outside of The Standup.
	▲	aidos an hour ago \| parent \| prev [-]
		Multi threading, but yeah. Original HN post here if you’re interested. https://news.ycombinator.com/item?id=7279358

▲

lawn 3 hours ago | parent | prev | next [-]

Neovim is actively moving in that direction.

▲

skydhash 3 hours ago | parent | prev [-]

Define “modern”!

Almost all such complaints are close to “I want to be cool and be seen as an haxor, but all I know is a bit of VSCode and IDEA, make it easier for me, plz”.

	▲	Sayrus 3 hours ago \| parent [-]
		I think what they did with first-party support for LSP would be an example of this. However, Neovim explicitely states that they don't want to turn VIM into an IDE. The feature parent is talking about seem to be falling into that type of vertical integration instead of composability.