Our great sponsors
-
-
extism
The framework for building with WebAssembly (wasm). Easily load wasm modules, move data, call functions, and build extensible apps.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
universal-format-on-type
Adds the format-on-type functionality to any language supporting range formatting.
> Perhaps using WASM via something like https://extism.org/. That would also open it up to building plugins in multiple languages.
https://github.com/lapce/lapce already says,
> Plugins can be written in programming languages that can compile to the WASI format (C, Rust, AssemblyScript)
so it sounds like they did that?
Perhaps using WASM via something like https://extism.org/. That would also open it up to building plugins in multiple languages.
Tangential to this I've wondered if it's possible or advisable to have a utility to port VS Code plugins to a plugin that's compatible with the JetBrains IDEs.
Actually WASI[0] will be a better alternative, IIRC extism serialize and deserialize the data that you want to pass every time, adding a lot of overhead.
[0] https://wasi.dev
> I don't think Electron is required in order to have rich extensions - just see Vim/Neovim, Emacs, or any IDE
At the cost of difficulty. Recently I wrote a VSCode extension myself with zero prior knowledge (shameless plug: https://github.com/CrendKing/universal-format-on-type/), in probably one day. All I needed to study is their extension API that I cared about. No need for learning a whole new DSL like Vim. Also easy to debug since there is no compilation and no environment setup.
There is a good reason even though everyone acknowledge about Electron's performance cost, everyone is still using it.