dzhou121's comments

dzhou121 | 2 years ago | on: Lapce

Lapce dev here. Firstly sorry for the bad experience for some people.

Just a bit of context here to explain the status of the project. The first line of code was started around 2018 as a personal project. And as of today, we still don't have anyone who works on it full time. We don't want to defend ourselves too much here, because there are very good quality code editors out there such as Helix, which is also community developed. But still, GUI is just such a beast of complexity, which consumes lots of time and energy which we already lack. That said, we had developed our own cross platform GUI toolkit called Floem, because as you may know there aren't any good ones that exist.

The journey was fun and challenging, but the aim of the project isn't a toy, and we believe by taking slow but firm steps, we'll reach production quality, one day. Before that, please do bear with us, and help us if you can (as in code).

dzhou121 | 3 years ago | on: Lapce Editor, Release v0.2.0

Lapce dev here. Thanks for posting this.

One thing I would like to highlight about the WASI based plugin system is that, on this release we’ve finalised our API design. We call it "Plugin Server Protocol", which includes everything that LSP has and extends it with more stuff that a code editor needs. We hope that "Plugin Server Protocol" can evolve into something great that future code editors can use. It will be win-win-win for editor authors, plugin writers, and users. New editors don't need to start from zero for plugins. Plugin writers write once to support all editors that are compatible with this API. Users have more plugins to choose from.

dzhou121 | 4 years ago | on: Lapce – Fast open-source code editor

It's mainly speed.

I don't know if it's fixed now. Previously when I was using VSCode, sometimes the "go to definition" hangs and it will freeze the whole editor, which was unacceptable. So in Lapce, nothing blocks the main thread other than your key press.

dzhou121 | 4 years ago | on: Lapce – Fast open-source code editor

Author here. Thanks for all the feedback.

I'm aware that Lapce lacks lots of basic stuff. It's a personal project so the initial set of features and key bindings are tight to my personal preferences.

I'm currently working on the missing pieces, like multi cursor support(in master but not released yet), mouse support, sane default key bindings(probably I'll stick to an existing editor), basic UX etc.

Feel free to submit a feature request or bug report in Github Issues or leave your feedback here.

dzhou121 | 4 years ago | on: Lapce – Fast open-source code editor

It is a bit similar.

When I thought about Lapce's logo, I took the initials of "Lightning" and "Powerful", so put L and P together to form a logo.

I guess Linkin Park is L and P too.

dzhou121 | 4 years ago | on: Lapce – Fast and Powerful Code Editor written in Rust

I think native compiled code is hard for plugin distributions. You'll need to target 3 main platforms Linux/macOS/Windows. You can use github actions to do it, but it would be so easier to just compile to WASI and that's it.

Also, WASI is compelling to me because of the potential of writing plugins in different programming languages.

dzhou121 | 4 years ago | on: Lapce – Fast and Powerful Code Editor written in Rust

Author here. I didn't expect this will go on Hacker News. Although the editor has been my daily drive for almost one year now, it's really rough on the edges.

The plugin system as described in the README hasn't been implemented yet.

page 1