Tbh, it just fits my workflow better. I would find myself editing stuff in nano more so than something like vscode because navigation in a file browser gets a little clunky for me. So it seemed fitting to learn neovim. I find the features more of a nuisance than a benefit at this stage and I want to properly understand how to use the underlying technologies these programs extract away.
I typically know exactly what I’m looking for and if I need more help I could check something out like fuzzy find. Those search boxes on file browsers are hit and miss for me, especially with Dot files. I store my scripts in a folder called .scripts and I reference them alot while building my apps.
Actually most my apps start out as scripts because prototyping is easier when you don’t initially worry about UI or optimization and focus on the core functionality.
With 20+ years of using various Unix OS’s as my primary OS, I can say for sure that my answer to “vi or emacs?” is “neither.”
Tbh, it just fits my workflow better. I would find myself editing stuff in nano more so than something like vscode because navigation in a file browser gets a little clunky for me. So it seemed fitting to learn neovim. I find the features more of a nuisance than a benefit at this stage and I want to properly understand how to use the underlying technologies these programs extract away.
I typically know exactly what I’m looking for and if I need more help I could check something out like fuzzy find. Those search boxes on file browsers are hit and miss for me, especially with Dot files. I store my scripts in a folder called .scripts and I reference them alot while building my apps.
Actually most my apps start out as scripts because prototyping is easier when you don’t initially worry about UI or optimization and focus on the core functionality.