4 ms·

Find a way to port plugins from VSC and I'm in!

• Alifatisk 3y ago
  As long as it supports C and Ruby, I'm happy.
• guessmyname 3y ago
  That will take a long time because plugins [1][2] are written in Rust too, e.g. Go LSP plugin [3][4]. [1] https://plugins.lapce.dev https://plugins.lapce.dev [2] https://github.com/lapce-community https://github.com/lapce-community [3] https://plugins.lapce.dev/plugins/panekj/lapce-go https://plugins.lapce.dev/plugins/panekj/lapce-go [4] https://github.com/lapce-community/lapce-go/blob/volt/src/main.rs https://github.com/lapce-community/lapce-go/blob/volt/src/ma...
  • boomskats 3y ago
    I think VSCode is also moving in the direction of wasi extensions[0], including for its serverside extensions host[1]. So there's a chance we get some of that for free. [0]: https://code.visualstudio.com/blogs/2023/06/05/vscode-wasm-wasi https://code.visualstudio.com/blogs/2023/06/05/vscode-wasm-w... [1]:https://github.com/microsoft/vscode-wasm https://github.com/microsoft/vscode-wasm
    • fbdab103 3y ago
      That's exciting. While I have some minor gripes about VSCode, it is fine enough. What gets me worried is the plugin ecosystem continually becomes a selling point in which no other editor can compete. I want other editors to be built and have a chance to thrive, but it becomes impossible if all of the good development tools get locked to one program.
  • pentaphobe 3y ago
    From the landing page: "You can write a plugin for Lapce with any programing language that compiles to WASI."
• panekj 3y ago
  We're not going to support VSCode extensions, it's not viable for us and would require to bring VSC/NodeJS runtime everywhere Lapce needs to run