Live data from Hacker News

Lapce – Fast open-source code editor

lapce.dev

81–90 of 231 posts

Re: Lapce – Fast open-source code editor

#82

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).

Re: Lapce – Fast open-source code editor

#84
post #78

This is one of the cases where not having null pointers in Rust really doesn't seem to help: % touch test % lapce test thread 'main' panicked at 'Error in Surface::configure: parent device is lost', /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.12.0/src/backend/direct.rs:214:9 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace % RUST_BACKTRACE=full lapce test thread 'mai…

A panic is a different kind of crash than a segfault, it can not be used to get your credit card information.

Re: Lapce – Fast open-source code editor

#85

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 remoting, that is genuinely a killer app right now for a lot of people.

That would be "just enough" editor for me so I could travel for a few days and still do a couple of hours of work here and there, without the laptop commitment.

I am not big on iOS subscription apps and I'm budget-constrained, but I'd pay $50 per year (probably more, and I figure I wouldn't be alone), without hesitation, for a fast remoting iOS editor that had 80% of the functionality of VSCode Remote and had a viable built in browser to avoid the process switch.

The code-server project definitely works for this, but something a bit more native would be amazing.

https://github.com/coder/code-server

Re: Lapce – Fast open-source code editor

#86
post #78

This is one of the cases where not having null pointers in Rust really doesn't seem to help: % touch test % lapce test thread 'main' panicked at 'Error in Surface::configure: parent device is lost', /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.12.0/src/backend/direct.rs:214:9 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace % RUST_BACKTRACE=full lapce test thread 'mai…

Probably an error in the WGPU rendering code. Rendering APIs have all sorts of implicit constraints and edge cases you need to be aware of (because of the complexity of using a specialized computation device that doesn't work like a CPU), and Rust's memory safety won't help you with most of it (since these are more of domain-specific logic errors rather than memory safety errors). Though Rust might help in designing a better API because it can use other features such as sum types, result types, and traits to model states and errors in a less error-prone way.

(At least the WGPU experience seems better than OpenGL, when you don't even get an assert or a stack trace, just an invisible error that you can only fetch by using glGetError() and is going to be hell of a shitty time trying to debug it and then sometimes you get to the conclusion that it might actually be a driver bug...)

Re: Lapce – Fast open-source code editor

#87
post #27

I was super excited and took it for a spin, but this is not usable (macOS 12, arm). Not "rough around the edges", but "pre-alpha unusable". The command pallet didn't respond to arrow keys. I couldn't figure out how to search for an extension. There's no menu bar items, and it follows very few macOS platform conventions (eg, Cmd+T opens a new tab with its own workspace, but Cmd+W doesn't close it.) For some reason, th…

The UI is actually native, it's just that the native Rust UI tookit it's using (druid) is still work-in-progress and doesn't have some things we expect from a full UI framework (most notably, good text rendering).

Re: Lapce – Fast open-source code editor

#88
Looks like there is some hardware incompatibility - the whole window, except for a small bit in the top left corner where I can see the "Open Folder" icon, is black.

``` $ lapce MESA-INTEL: warning: Haswell Vulkan support is incomplete $ uname -r 5.13.0-35-generic x86_64 x86_64 ``` Ubuntu 21.10

Re: Lapce – Fast open-source code editor

#89
No Electron? That is already one good thing ;)

Why does Rust folks seem to encapsulate and separate their stuff more and more? Own build-tools and infrastructure are one thing. Am I right that Druid is not an very own Toolkit but a layer like WxWidgets?

Re: Lapce – Fast open-source code editor

#90
I like the single lapce.exe and loads reasonably fast.

But this is in a pre pre-alpha stage, so many bugs it's far too early for public feedback. It loads reasonably fast except chrome stats in top left then jerks towards the center. The start page says to bring up the command palette which I was unable to navigate via keyboard.

The open file dialog takes an eternity to load the first time, the path is in a text box that's not editable. Focusing a text file gives an Insert cursor which is in text mode, there's a noticable slow delay before writing the first character, text selection is non existent so lacks basic text editing features.

There is a built-in terminal however there's only a single tab.

The only thing that gives it potential is that the folder/file browsing is super quick even with a node_modules folder so it might be built on efficient rendering that can be improved.

Even for such a basic editor it's 38mb download. For a far smaller + more complete editor checkout Lite:

https://github.com/rxi/lite

Post reply on HN