impatient.nvim VS barbar.nvim

You could use impatient.nvim or the new vim.loader module if you’re on nightly. Both work really well. I used impatient for a long time and it reduced my startup time by half. I’m using vim.loader now and it reduces it by about the same amount

The 20-30 ms promise depends on your hardware. In my case, vanilla Neovim takes about 18 ms to startup, so a realistic good startup time for my config is around 50-60 ms. Lines of code isn’t a great reference either because you could just lazy load a bunch of plugins and have more LoC but still better startup times. What I would recommend is using lazy.nvim or if you wanna stick with packer, then pairing it with impatient.nvim .

automatically caches all startup code before :h VimEnter or :h BufReadPre (basically what impatient.nvim does)

there is an amazing plugin called impatient.nvim that cache a lot of stuff and make other pluggins go so fast !

Try installing https://github.com/lewis6991/impatient.nvim first.

:lua vim.pretty_print(vim.mpack.decode(vim.mpack.encode({some = { thing = false }}))) used by impatient.nvim

Did you defined your [[ and ]] mappings in that file or just created it? the after directory runs at the end of your config so you can override this kind of settings. Maybe you are using impatient.nvim? From their README:

Are you using impatient.nvim? It caches lua modules. My startuptime with 72 plugins (including it) and zero lazy loading is 600ms.

considering your vscode background when you say tabs your really mean buffers( Trust me even i had this problem when I made the switch). So your solution here is using a plugin. There are many but I personally use barbar.nvim

you can check out https://github.com/romgrk/barbar.nvim

Nice! I personally use barbar.nvim's : BufferCloseAllButVisible which closes all buffers that aren't currently visible in a window.

There has been discussion of adding that feature to upstream barbar.nvim, but no concrete work has begun yet.

I'm using barbar.nvim, a simple but efficient bufferline plugin.

LuaLS has trouble identifying vim functions. I just went through and annotated a bunch of functions with doc comments in a project to help it figure things out.

I use barbar.nvim for displaying buffers as tabs and whenever I feel like I have too many open I run :BufferCloseAllButVisible (from a mapping), and it closes every buffer except those I have currently visible

i use barbar