pynvim VS libuv

In a python remote plugin using pynvim, you could write something like this.

I can't fully recommend one example posted in #520 (because it has some practices that are not quite recommendable IMHO) but you may want to take a look at it.

To my knowledge no, but looks this is a common problem on Windows. Please file an issue on https://github.com/neovim/pynvim/ (a reproduction step would be greatly appreciated) so we can track it.

That should be it https://github.com/neovim/pynvim

You managed to pick two languages I don't use, but I believe it would more than meet your criteria. Neovim has excellent LSP support, and there are several for C/C++/CMake and for Python. See the list here. There's intellisense like completion via coc. For debugging there's also nvim-dap. With something like pynvim you could even write plugins for neovim itself in python. (I've written some in lua myself because of its native lua interface, which is a nice alternative to vimscript.)

pynvim doc is not very good IMO I will gladly use nvim --remote now that the feature is available if I ever need something from python!

As a sidenote, I didn't see another option besides making it as a python remote plugin, since I really needed to use Python's jupyterclient library (basically the Jupyter protocol is pretty complicated, and jupyter-client is its official implementation). And that sucks, because pynvim is badly documented and has a few really weird bugs (e.g. https://github.com/neovim/pynvim/issues/386), which I then had to work around.

Maybe this or this

I'm trying to use pynvim to write tests for a plugin (since I'm a big fan of pytest). However I cannot seem to configure the nvim session through a lua file. I've created an issue but thought I would also post here to see if someone knows what's going on since I haven't had a reply in a few days.

I wound up on a different team with pre-existing Python code so temporarily shelved my use of Go for a bit, and we used Sanic (an async Python framework built on top of the excellent uvloop & libuv that also powers Node.js) to build some APIs for live channel management & operations. We hand-wrote our OpenAPI and used it to generate documentation and a CLI, which was an improvement over what was there (or not) before. Other teams used the OpenAPI document to generate SDKs to interact with our service.

In the source code of the Node.js opensource project, lib folder contains JavaScript code, mostly wrappers over C++ and function definitions. On the contrary, src folder contains C++ implementations of the functions, which pulls dependencies from the V8 project, the libuv project, the zlib project, the llhttp project, and many more - which are all placed at the deps folder.

Libuv, the C library that gives Node.js its asynchronous, non-blocking I/O capability is responsible for managing the thread pool. Node.js gives you the capability of using additional threads for computationally expensive and long-lasting operations to avoid blocking the event loop.

Node.js is written in C, C++, and JavaScript. The core components of Node.js - the V8 engine and the libuv library - are written in C++ and C, respectively, since these languages provide low-level access to system resources, making them well-suited for building high-performance and efficient applications. JavaScript is mainly used to write the application logic.

x8 apparently https://github.com/libuv/libuv/pull/3952

Notably upgrades to libuv 1.45 which has io_uring support. Faster file system access! Awhh yeah, it's on.

Remarkable what a mild & unintrusive PR adding io_uring was. https://github.com/libuv/libuv/pull/3952

Well, the single-threaded nature ultimately leads to its biggest downfall. Node.js utilizes a synchronous event loop engineered using Libuv that takes in code from the call stack and executes it.