Our great sponsors
-
coc is easier to set up if you start out, since it's one plugin that does everything. the built-in lsp is more modular and requires a bunch of plugins, and some boilerplate for the related plugins to get going. nvim-zero has pretty much all the boilerplate form the different plugins collected in one place.
-
mason.nvim
Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.
native LSP using mason.nvim
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
-
Getting the "basic LSP features" is easy with nvim-lspconfig. The minimal config can be like 20 lines of code, where 19 of those is setting up keybindings. It takes literally one line of code to connect the LSP server with Neovim.
-
The problem then becomes how to get other LSP related plugins to work well with each other. This is where familiarity with lua or vimscript plays an important role. Copy/pasting code from examples and other peoples config sometimes doesn't work, and you need to tweak the code to make it work in your system. I believe this is where a lot people stuggle. Classic example being the autocompletion setup with nvim-cmp.
-
the PR for call hierarchies in neovim's lsp client seems have been merged back in mid-2021
-
maybe litee-calltree?
-
Other things I miss: - Org-mode for outlining, notes, work journaling, org-roam - Introspection of the running environment was unsurpassed, between built in stuff and things like Helpful - Emacs users seemed way less fixated on color themes, aesthetic plugins, and tricking out their UIs. (Insert quips about how hideous a default install is here.) It's a Big Thing in the Neovim community spaces, I would go as far as to say overrepresented. - Direnv support felt a little better - I'm a little nostalgic for Elisp, but Lua(JIT) is great and it's largely a skill/practice issue. Might try out Fennel. - Elisp macros and advising functions in particular were double-edged but sometimes suited the problem at hand so well - No split ecosystem - all Emacs extensions that aren't in core, and much of core, are always Elisp. Neovim has the double-language issue dividing the ecosystem a little bit. I can't read or write VimL and don't care to.
-
InfluxDB
Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.
-
My configs for each are public for the morbidly curious, neither is very clever or sophisticated IMO: https://github.com/shanesveller/nix-dotfiles-public-snapshot/blob/public-snapshot-2021-11/config/doom/config.org
-
-
Clear leader by an extremely wide gap is that I miss Magit and none of the Vim-compatible Git tooling is even close. I still drop back into it for gnarly rebases.