nvim-ide VS neovim-ide

Yeah, it's not as easy as it can be but embedding neovim right into container in some workflows might be even better than VSCode experience. I have seen some projects that use docker to containerize all tools for development (neovim included) to make programming easier and remove bloat from main system. For example, https://github.com/MashMB/nvim-ide

One more way, that comes to my mind, is really similar to your zip approach but instead uses docker containers such as in this repo for nvim: https://github.com/MashMB/nvim-ide

Here is link number 2 - Previous text "try"

I also wanted to make VIM more like IDE so maybe you will find something useful in my config. It is mainly based on coc.nvim, actually no lua configuration.

Exactly, Vim is simply one part of the workflow (even though plenty of people try to make it an IDE). If your workflow mandates some specific piece of software that you cannot remove for contractual/work mandate reasons (IE Visual Studio), then yes you are likely stuck. But if you can migrate away then it is worth it. Instead of one singular IDE you can use multiple tools together, each one being very good at the thing it does instead of one tool that is mediocre at all of the things. If you want you can integrate things like git, linting, completion, auto-linting, and even compilation and debugging into vim. I would recommend not trying to do all of this at once in the beginning, and even then I personally find it easier to have the compilation and debugging to be external. Linting and code completion are great additions however. But that is the beauty of Vim, you can choose to have as little or as much as you want in it. An IDE is like a premade toolkit that resists any changes you make to it, vim is more like a toolbox that you can fill with what you want. IDEs are easier to start with, but hold you back later when you hit a skill ceiling. Vim (And even more bloated editors like Emacs ;)) are harder to start but have no skill ceiling that stops you from improving. Or if there is one, I have not come close enough to see it yet after more than a decade of regular use.