telescope-fzy-native.nvim VS neovim

I recommend the fzy native extension for telescope. https://github.com/nvim-telescope/telescope-fzy-native.nvim it’s still not quite as fast as the old fzf solution but I don’t notice it unless I’m working on some huge legacy codebase.

This plugin provides precompiled libzf libraries packaged into a sorter for Telescope, similar to telescope-fzf-native.nvim and telescope-fzy-native.nvim. This gives the speed improvement of native code, and the benefits of the zf algorithm inside telescope for all pickers.

fzy-lua-native similary doesn't use fzy, it's a matcher based on the algorithm that fzy uses. This is actually the same matcher used under the hood in telescope-fzy-native.

Are you using the fzy-native extension?

Is it faster than telescope-fzy-native (fzY)? Does it provide better results?

I want to give a little update on the speed problem, since this is coming up more or less on every Telescope thread. Having bugged the developers opening regular GitHub issues, it seems that you can get a consistent jump on search speed by using the native sorter

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.