startuptime.vim VS neovim

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 ...

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.