News for hackers. Stuff that matters.
Re:Lapce by cellis on Sunday February 18, 2024 @01:22PM (#39421541)
Find a way to port plugins from VSC and I'm in!
Re:Lapce by guessmyname on Sunday February 18, 2024 @01:36PM (#39421692)
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

[2] https://github.com/lapce-community

[3] https://plugins.lapce.dev/plugins/panekj/lapce-go

[4] https://github.com/lapce-community/lapce-go/blob/volt/src/ma...

Re:Lapce by pentaphobe on Sunday February 18, 2024 @01:56PM (#39421933)
From the landing page:

"You can write a plugin for Lapce with any programing language that compiles to WASI."

Re:Lapce by boomskats on Sunday February 18, 2024 @01:55PM (#39421918)
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-w...

[1]:https://github.com/microsoft/vscode-wasm

Re:Lapce by fbdab103 on Sunday February 18, 2024 @04:21PM (#39423498)
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.
Re:Lapce by Alifatisk on Sunday February 18, 2024 @01:33PM (#39421666)
As long as it supports C and Ruby, I'm happy.
Re:Lapce by panekj on Sunday February 18, 2024 @07:42PM (#39425088)
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