Can I please have something as extensible as Emacs with real multi-threading and modern architecture? I wonder, is that too much to ask?
Lapce Editor, Release v0.2.0
21–30 of 41 posts
Re: Lapce Editor, Release v0.2.0
#22This is a project I'm really excited for. It seems like it has a chance of potentially replacing Sublime Text for me some day, which is something I've been trying to do for a while with zero success. I worry about the plugin system though. It is using WASI for plugins, so people can use any programming language they want. That seems like it could lead to a horribly fragmented ecosystem. It also means plugins are limi…
NeoVim picked Lua and every Lua based plugin I've seen has been extremely impressive in its speed.
I don't love Lua - I don't know it so well and find it a little difficult to read and write - but I can't argue with the results. Python is not the right decision nor is JS.
Only other language I could see is rust given its speed, safety, and interoperability with C but Rust also has a lot of ceremony which is great but not as conducive to the plugin author community (a lot of additional overhead).
Re: Lapce Editor, Release v0.2.0
#23Can I please have something as extensible as Emacs with real multi-threading and modern architecture? I wonder, is that too much to ask?
Re: Lapce Editor, Release v0.2.0
#24Can I please have something as extensible as Emacs with real multi-threading and modern architecture? I wonder, is that too much to ask?
Re: Lapce Editor, Release v0.2.0
#25It only supports 3 languages :(
Re: Lapce Editor, Release v0.2.0
#26This is a project I'm really excited for. It seems like it has a chance of potentially replacing Sublime Text for me some day, which is something I've been trying to do for a while with zero success. I worry about the plugin system though. It is using WASI for plugins, so people can use any programming language they want. That seems like it could lead to a horribly fragmented ecosystem. It also means plugins are limi…
Python is and has been a go to language for writing vim plugins. We've seen its limitations in the vim community. The same is true for Javascript and Typescript (which I personally love). NeoVim picked Lua and every Lua based plugin I've seen has been extremely impressive in its speed. I don't love Lua - I don't know it so well and find it a little difficult to read and write - but I can't argue with the results. Pyt…
Can you link to any example plugins that are written in either python or js/ts and are considered slow? I'm not doubting you, I'm just not a big vim user, so I'm not familiar with many plugins.
> NeoVim picked Lua and every Lua based plugin I've seen has been extremely impressive in its speed.
I'm sure you're impressed by the perceived speed, but I don't believe you have any real (i.e. data-backed) basis for comparison there. If you do, I'd love to see it.
But to counter your anecdotal evidence with another, Sublime Text only supports Python for its plugin system, and the performance of every plugin I have ever used has been extremely fast. Besides network stuff, I've never even noticed plugin operations, since they all seem to finish instantly.
Re: Lapce Editor, Release v0.2.0
#27How have you been finding Druid? I think it's a difficult start for a lot of people because how often it's changing (and how Xilem may fundamentally change it again in the future). I had a similar issue with iced. Rust GUI is in a weird state right now with no strong options unless you go WebRender or something like Tauri.
Re: Lapce Editor, Release v0.2.0
#28How have you been finding Druid? I think it's a difficult start for a lot of people because how often it's changing (and how Xilem may fundamentally change it again in the future). I had a similar issue with iced. Rust GUI is in a weird state right now with no strong options unless you go WebRender or something like Tauri.
I haven’t used druid, but I’m on the hunt for a good option too. What were your impressions with iced leaving aside the early stage changes?
Re: Lapce Editor, Release v0.2.0
#29One 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.
Re: Lapce Editor, Release v0.2.0
#30This is what i've been searching for, for ages - Lightweight - Has necessary features - Has a nice UI - Actively maintained - Small learning curve - Not much config required It only supports 3 languages :(