startuptime.vim VS barbar.nvim

You could use https://github.com/tweekmonster/startuptime.vim. Then you can run :StartupTime -- big-file.txt

tweekmonster/startuptime.vim is inaccurate. I think it doesn't take Lua into account. Don't use this plugin.

I recently had a look at startup performance. Using the startuptime plugin both moonfly & nightfly were taking around 4.5ms to load on my quad-core Linux desktop (not too bad for traditional Vimscript-based colorschemes). Some profiling did indicate that clearing highlights and resetting syntax are actually quite expensive. We really don't need to do either when loading a colorscheme at Vim start time; it is only really needed when changing colorschemes within an existing edit session. Putting in a simple guard results in moonfly & nightfly now taking only 2.5ms to startup (on my machine).

Lastly, I also had a look at startup performance. Using the startuptime plugin both moonfly & nightfly were taking around 4.5ms to load on my quad-core Linux desktop (not too bad for Vimscript-based colorschemes). Some profiling did indicate that clearing highlights and resetting syntax are actually quite expensive. We really don't need to do either when loading a colorscheme at Neovim start time; it is only really needed when changing colorschemes within an existing edit session. Putting in a simple guard results in moonfly & nightfly now taking only 2.5ms to startup (on my machine). That is quite similar to some of the nice new Lua-based Neovim colorschemes now available. A win, albeit a small one.

Using the :StartupTime provided by https://github.com/tweekmonster/startuptime.vim ...

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