Neovim has come a long way today from it’s original goal of being able to support asynchronous jobs. Today it comes packed with a ton of useful and high performance libraries and plugins. To add to that it also has a highly enthusiastic and vibrant community of lua developers who are working tirelessly to make neovim better.

Today we’ll look at how one can easily configure neovim to work similar to a modern Java IDE.

In a recent project, we developed an ingestion pipeline in Rust. We wanted to execute asynchronous tasks in response to messages received from SQS, as a subscriber. Our goal was to leverage Rust generics to allow the subscriber to take ownership of the payload schema and the pipeline implementation details. This approach enables the separation of the SQS subscription logic from the subscriber’s responsibilities, promoting of cleaner separation of concerns. It also facilitates independent testing of both components, ensuring they can be assessed in isolation.