Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lapce Editor, Release v0.2.0

github.com

Post reply on HN
Print view View original

11–20 of 41 posts

Re: Lapce Editor, Release v0.2.0

#11

Post by funklute »

frou_dh wrote: post #8
funklute wrote: post #7

Earlier quoted context omitted.

I wasn't disputing that though. However, because of the batteries included, it has significantly more overhead than lua.

I don't think the breadth of the standard library necessarily affects startup time. You only pay the cost for a module when someone imports it, surely.

Yes, true - I didn't word that very well. I believe lua is faster than python mostly due to the simplicity of the language implementation itself, but as another comment pointed out, it might not actually be that big a difference (and I don't have any hard numbers at hand).

Re: Lapce Editor, Release v0.2.0

#12

Post by funklute »

bogwog wrote: post #10
funklute wrote: post #5

Earlier quoted context omitted.

> IMO, any application for editing/powerusers with a plugin system should be using Python exclusively. While I agree that python is often a good (or even the best) choice, I think the neovim team made a solid argument for lua (easier than C, faster than python). Would you have chosen python for neovim, and if so, how would you have avoided excessive startup times? (keeping in mind that a terminal-based editor gets st…

I actually have a mild distaste for Lua after spending about a month and a half using LiteXL ( https://lite-xl.com/ ), which is an editor written entirely in Lua. The thing is a spaghetti mess, with a lot of plugins relying in internal implementation details of core features, and some of them even making changes to the core and other plugins. (but to be fair, that's mostly an issue with the design of LiteXL and not L…

> And idk what neovims plugin ecosystem looks like, but if Python's startup times were a real issue, I don't think I would mind having a persistent daemon to reduce the problem, especially if it means better plugins.

That's a very good point!

Re: Lapce Editor, Release v0.2.0

#13

Post by haolez »

bogwog wrote: post #4

This 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…

There might be another advantage here for WASI: you could write a compiler for, say, VimScript and it would translate to this editor's APIs. Sounds like an interesting project to me.

Re: Lapce Editor, Release v0.2.0

#14

Post by rstat1 »

bogwog wrote: post #4

This 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…

Nice thing about using WASM for plugins is that you wanted to (for some unknown reason) write a plugin for this editor in Python you could because it can be compiled to WASM.

>>Imagine trying to maintain a set of plugins all using different programming languages and build systems and package managers. That's a maintenance nightmare.

I would imagine once you got all this setup the first time, it wouldn't be that much of a "maintenance nightmare". Literally just running scripts.

Re: Lapce Editor, Release v0.2.0

#15

Post by bogwog »

rstat1 wrote: post #14
bogwog wrote: post #4

This 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…

Nice thing about using WASM for plugins is that you wanted to (for some unknown reason) write a plugin for this editor in Python you could because it can be compiled to WASM. >>Imagine trying to maintain a set of plugins all using different programming languages and build systems and package managers. That's a maintenance nightmare. I would imagine once you got all this setup the first time, it wouldn't be that much…

> I would imagine once you got all this setup the first time, it wouldn't be that much of a "maintenance nightmare". Literally just running scripts.

Famous last words

Re: Lapce Editor, Release v0.2.0

#17

Post by toastercat »

bogwog wrote: post #10
funklute wrote: post #5

Earlier quoted context omitted.

> IMO, any application for editing/powerusers with a plugin system should be using Python exclusively. While I agree that python is often a good (or even the best) choice, I think the neovim team made a solid argument for lua (easier than C, faster than python). Would you have chosen python for neovim, and if so, how would you have avoided excessive startup times? (keeping in mind that a terminal-based editor gets st…

I actually have a mild distaste for Lua after spending about a month and a half using LiteXL ( https://lite-xl.com/ ), which is an editor written entirely in Lua. The thing is a spaghetti mess, with a lot of plugins relying in internal implementation details of core features, and some of them even making changes to the core and other plugins. (but to be fair, that's mostly an issue with the design of LiteXL and not L…

> The thing I don't like about Lua is that it doesn't really offer much. It's a programming language with practically zero features. Projects end up doing things, like inventing their own class system just to do OOP, and that becomes a problem for interop between projects.

I personally see Lua's minimalism as one of its strengths and one of the reasons it's great for plugin systems. OOP is doable if you need it, but really unnecessary anyway.

Re: Lapce Editor, Release v0.2.0

#18

Post by kbd »

funklute wrote: post #5
bogwog wrote: post #4

This 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…

> IMO, any application for editing/powerusers with a plugin system should be using Python exclusively. While I agree that python is often a good (or even the best) choice, I think the neovim team made a solid argument for lua (easier than C, faster than python). Would you have chosen python for neovim, and if so, how would you have avoided excessive startup times? (keeping in mind that a terminal-based editor gets st…

> how would you have avoided excessive startup times?

I don't think it's a problem? kitty terminal is programmed half in Python and is fast.

Re: Lapce Editor, Release v0.2.0

#19

Post by stephc_int13 »

I tried it on Windows 11.

- Startup is fast.

- Memory usage is a bit high (133MB with no files open)

- CPU and GPU usage on idle is weird (25% and 40%) doing nothing, the window is not even displayed...

That's unfortunate, that is a pass for now...

Re: Lapce Editor, Release v0.2.0

#20

Post by kikki »

How 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.
Post reply on HN