Lapce – Fast open-source code editor • Hacker News Board

Re: Lapce – Fast open-source code editor

#121

Post by eek2121 » Thu, Mar 17, 2022, 1:43 PM UTC

Tried it for a bit. A great start.

The good: - Half the memory usage on my machine compared to other graphical editors. - It is extremely fast, though as all the missing features get added, we'll see if it stays that way.

Some basic QoL improvements needed - Needs syntax highlighting for more languages (Ruby/JS in my case) - Needs to use the system dialogs on Windows and macOS. Had a difficult time using other drive mount types. The built-in dialog would not open them at first.

I will be keeping an eye on this one. The only one that beats it speed-wise and memory wise is vim. :)

Re: Lapce – Fast open-source code editor

#122

Post by danielvaughn » Thu, Mar 17, 2022, 1:47 PM UTC

dzhou121 wrote: post #41

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

I love that you're using Treesitter. I haven't followed the editor space much, but afaik, this is one of the first to implement it. The demos I'd seen were very impressive - definitely going to give it a shot!

Re: Lapce – Fast open-source code editor

#123

Post by eggy » Thu, Mar 17, 2022, 1:55 PM UTC

gyulai wrote: post #28

ncmncm wrote: post #15

Nowadays when I see "written in Rust" in the title, it reads like special pleading: "It's maybe not as good as what you use, but we are really proud to have got it working at all."

I think that's a perfectly valid appeal to altruism in a tech-savvy audience. It makes sense to take a hit on your individual needs and wants as a user in the short term, if it helps with keeping the tech ecosystem which we collectively inhabit healthy in the long term. Free market forces based on individual self-interest have proven to be really bad at doing that, so altruism is needed to fill the gap. ...by that lo…

I'd prefer it written in Zig compared to Rust, C++, JavaScript, or Cobol ;)

Re: Lapce – Fast open-source code editor

#124

Post by chrisweekly » Thu, Mar 17, 2022, 2:05 PM UTC

dzhou121 wrote: post #54

reacharavindh wrote: post #51

Earlier quoted context omitted.

It is refreshing to see a new code editor, even with minimal set of features that feels fresh and fast. Thanks for putting it out there. Please please please keep that responsive experience and don't trade it off for a full set of features that will make this tool lose its charm and become just the same as the rest of the powerful tools.

Thanks for your kind words. It will, it's in the DNA. L comes before P.

Awesome.

> " L comes before P."

?

Re: Lapce – Fast open-source code editor

#125

Post by jpetso » Thu, Mar 17, 2022, 2:05 PM UTC

jonkoops wrote: post #82

dzhou121 wrote: post #41

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

Are there any plans to release the app as a Flatpak, they are a great way to package your application cross-distro with a central way of updating (such as Flathub).

No relation to this project. Just wanted to chime in to say that KDE's Kate editor pulled its Flatpak because the sandboxing makes much of the system integration (terminal, git, language servers) hard or impossible.

A Flatpak may have to ship with an independent copy of a lot of basic developer tools, and even then I don't know whether I want two different versions of git access the same local repository with a chance of incompatible repository formats.

Re: Lapce – Fast open-source code editor

#126

Post by chrisweekly » Thu, Mar 17, 2022, 2:06 PM UTC

unfocussed_mike wrote: post #85

dzhou121 wrote: post #41

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

I haven't had a chance to test this yet but this is fantastic to see. Anything like this that progresses the cross-platform remote model that we now have with VSC, particularly if the endpoint is fast and memory-efficient, is really important, because of the variety of dev environments. What I would _really_ like, of course, is an iPad editor that could do the same. If you could make an iPad editor that has VSC-style…

Are in-browser editors ruled out?

EDIT: aha, just saw this, downthread:

> "The main problem is as far as I am aware the same; the browser-side connection can drop quite easily because of the limits of iOS (you can't switch away without losing it)."

Re: Lapce – Fast open-source code editor

#127

Post by klaussilveira » Thu, Mar 17, 2022, 2:09 PM UTC

dzhou121 wrote: post #41

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

How are you rendering fonts? FreeType to render the glyph texture map and then quads for each character? Or SDF?

Re: Lapce – Fast open-source code editor

#128

Post by HereBeBeasties » Thu, Mar 17, 2022, 2:11 PM UTC

chrisweekly wrote: post #124

dzhou121 wrote: post #54

Earlier quoted context omitted.

Thanks for your kind words. It will, it's in the DNA. L comes before P.

Awesome. > " L comes before P." ?

LAPCE == Lightning-fast and Powerful Code Editor

I.e. Lightning-fast comes before Powerful.

Re: Lapce – Fast open-source code editor

#129

Post by dzhou121 » Thu, Mar 17, 2022, 2:12 PM UTC

klaussilveira wrote: post #127

dzhou121 wrote: post #41

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

How are you rendering fonts? FreeType to render the glyph texture map and then quads for each character? Or SDF?

render the glyph texture map and then quads for each character

Re: Lapce – Fast open-source code editor

#130

Post by _fat_santa » Thu, Mar 17, 2022, 2:23 PM UTC

ncmncm wrote: post #15

Nowadays when I see "written in Rust" in the title, it reads like special pleading: "It's maybe not as good as what you use, but we are really proud to have got it working at all."

The same reason "native MacOS app" is a selling point, it's all Electron's fault (only half kidding here).

For the tech savvy crowd, we care about stuff like this because we don't need another electron app hogging memory on our systems. Personally for me "written in rust" translates to "I care about performance" and "I care about my app not hogging your system memory"