Neovim turned itself into a pop-blink IDE which some people never wanted. It's good that it serves the needs of its fans, but it's also good that Vim stayed in its own tracks. Losing Vim as it is would be a great loss for many.
I wanted to like neovim for its possibly better lsp integration, but if all I need is an IDE with partial vi emulation, I might as well use VSCode.
i.e if you do :!bash in vim you enter bash in neovim you won't
I also think that "stability" and the "community" are two other things that made me switch back to vim.
When I tried it, nvim-qt was hard to associate with file extensions on windows (required something like “-- “filename”” in different shapes and hours of regedit debugging, can’t remember now), then nvim itself had issues with refreshing on manual window resize and with autoresizing the window on setting ‘lines’. And a few more os integration related issues. It was basically unusable gui-wise so I bailed out due to no good reason to stay.
I was probably talking about that astro-thing that works like a christmas tree and was the main selling point at the time.
What does that even mean? Just sounds like a lazy and false argument.
Things may have settled since then, maybe that’s why you think that this phrase looks odd.
I've been using Neovim since it forked and it has always offered a Vim-like experience, it's just that Neovim has given you more options.
Maybe that's why some think it's too "blinky" as it's possible to turn it into a blinky IDE if you really want to because it's more capable (and some do).
It's just in recent years I've migrated to Lua and the large amount of Neovim specific plugins (many that heavily depend on async for non-blocking operation of for instance picking or completion).