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

Lapce – Fast open-source code editor

lapce.dev

Post reply on HN
Print view View original

181–190 of 231 posts

Re: Lapce – Fast open-source code editor

#181

Post by dzhou121 »

GekkePrutser wrote: post #178
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…

What prompted you to develop it? The market for this is quite crowded with Atom and VS Code. Where you that dissatisfied with them? Just wondering. I like that this is native though. VS Code is one of the rare good electron apps but native is still nicer IMO. Will give it a try.

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.

Re: Lapce – Fast open-source code editor

#182

Post by andrewshadura »

randonee wrote: post #144
pdenton wrote: post #139

Earlier quoted context omitted.

I believe an open source editor should be built from source and I couldn't find links to sources or how to build from source on the website. The getting started documentation points to the download section. It would be cool if one of the downloads would be marked as source (for any OS).

There is a GitHub link on the top of the website. Build instructions are in the readme. https://github.com/lapce/lapce

I don't see it on the phone.

Re: Lapce – Fast open-source code editor

#183

Post by petr_tik »

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

> we are really proud to have got it working at all

On the contrary, the rust crate ecosystem and tooling means a lone developer can compose specialised libraries to produce a working artefact that scratches her own itch. Such productivity is the opposite of getting something working at all.

Trying to build an OSS cpp project or even worse, use an OSS Cpp library in your own project is more along the lines of "getting something working at all". Every third-party and some enterprise-internal Cpp libraries require one answers the following questions:

- how do I build the damn thing?

- how do I run the tests?

- how do I use the library? Vendor into the repo? apt install?

- what APIs does the system/library provide?

- where can I find the documentation and examples?

- how do I set up code completion?

- how do I know am using the library interface correctly?

- how do I know I didn't violate any invariants/safety guarantees?

Compare with the list of dependencies across the Cargo workspace members.

https://github.com/lapce/lapce/blob/master/lapce-core/Cargo....

https://github.com/lapce/lapce/blob/master/lapce-ui/Cargo.to...

https://github.com/lapce/lapce/blob/master/lapce-rpc/Cargo.t...

The cost of adding a new rust dependency when measured by the number of questions you need to answer beforehand is nearly constant. This means a layman can be more productive in rust.

Re: Lapce – Fast open-source code editor

#184

Post by mekster »

gorjusborg wrote: post #119
bobajeff wrote: post #110

Earlier quoted context omitted.

True. But it shouldn't be. It's like tearing down a perfectly good neighborhood to make way for a hotel that doesn't really benefit the town.

In my opinion, that's a main reason developers should favor open source tools, they never truly 'go away'. The code is out there, so keeping it going then comes down to whether someone cares enough to maintain it. Not saying that path is all roses...

It's same. Surrounding environments will change and just because the source of a previous version is there doesn't mean you can stably run it years on.

Re: Lapce – Fast open-source code editor

#185

Post by kybernetikos »

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…

The speed on this is phenomenal and I'm really looking forward to you filling out a few more of the missing pieces. Really impressive achievement.

I wonder if you've considered kakoune style modal editing rather than vim? If you've not come across it, it might be worth looking at, as I think it's a better paradigm and one that I expect will go nicely with the multiple cursors you're working on.

Re: Lapce – Fast open-source code editor

#186

Post by mekster »

GekkePrutser wrote: post #178
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…

What prompted you to develop it? The market for this is quite crowded with Atom and VS Code. Where you that dissatisfied with them? Just wondering. I like that this is native though. VS Code is one of the rare good electron apps but native is still nicer IMO. Will give it a try.

I thought atom was ditched. Competitors would be VSC, Sublime and JetBrains.

Re: Lapce – Fast open-source code editor

#187

Post by mekster »

honkycat wrote: post #142
AlchemistCamp wrote: post #116

Earlier quoted context omitted.

For me, the most important feature is VIM bindings. I used to suffer from severe RSI and VIM was a big part of what helped my wrists recover.

Seriously. I don't know how people text edit without the vim keybindings. I'll never go back!

Only if I rebind keys from the very unintuitive default vim binding. It's like it's trying to twist your brain.

Re: Lapce – Fast open-source code editor

#188

Post by mekster »

NotEvil wrote: post #176
danielvaughn wrote: post #122

Earlier quoted context omitted.

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!

Every editor supports it now

What do you specifically mean by every?

Re: Lapce – Fast open-source code editor

#189

Post by dingoegret12 »

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 don't understand this sentiment. Rust is the only language ecosystem where I find that anything works at all. Whenever I have to build something not built in rust, I'm praying. With rust made tooling, I just never have problems.

Re: Lapce – Fast open-source code editor

#190

Post by mekster »

woile wrote: post #8

It looks really promising. I wonder why code editors have the file explorer on the left side by default, if you resize it you move the whole text (unless you write in a right-to-left language). A colleague made me aware of this a while ago and I cannot stop wondering. I moved it to the right ever since.

Why do you want the text to start at the left edge of your display?

That's worse for your neck than keep it more center aligned.

Post reply on HN