Good point.
I might oversate the performance. However, we can see the same word choice in introduction to filetype.lua in neovim.
Well, creating thousands of autocommands on startup is not exactly very performant. Indeed, filetype.vim is one of the slowest (perhaps the slowest) startup files shipped with Neovim. (...)
This is the approach filetype.lua takes, which means that it is considerably more performant than filetype.vim. reddit.com/r/neovim/comments/rvwsl...
In my environment, filetype.vim takes around 10ms.
We may feel a delay if it takes 33ms (i.e., 1 frame for 30 fps).
It is valuable to reduce 10ms, isn't it?
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin.
Back in the day, I had a geekcode which I'm not going to share with you.
418 I'm a teapot.
I think at the point where we're measuring 1-off improvements in tens of milliseconds, it's not valuable. If this was in a library being called hundreds of times, then sure. Otherwise, it's only valuable so long as it doesn't impact anything else, such as code readability or cross-platform compatibility. I mean, for example, if you get an optimisation for one platform by splitting the code, for example, then it's debatable whether you've improved the final product.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good point.
I might oversate the performance. However, we can see the same word choice in introduction to filetype.lua in neovim.
In my environment, filetype.vim takes around 10ms.
We may feel a delay if it takes 33ms (i.e., 1 frame for 30 fps).
It is valuable to reduce 10ms, isn't it?
I think at the point where we're measuring 1-off improvements in tens of milliseconds, it's not valuable. If this was in a library being called hundreds of times, then sure. Otherwise, it's only valuable so long as it doesn't impact anything else, such as code readability or cross-platform compatibility. I mean, for example, if you get an optimisation for one platform by splitting the code, for example, then it's debatable whether you've improved the final product.