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

Lapce

lapce.dev

Post reply on HN
Print view View original

151–160 of 229 posts

Re: Lapce

#151

Post by nicoburns »

dzhou121 wrote: post #145

Lapce dev here. Firstly sorry for the bad experience for some people. Just a bit of context here to explain the status of the project. The first line of code was started around 2018 as a personal project. And as of today, we still don't have anyone who works on it full time. We don't want to defend ourselves too much here, because there are very good quality code editors out there such as Helix, which is also communi…

Just wanted to stick a link the Floem GUI toolkit mentioned above:

https://github.com/lapce/floem

because IMO it's as interesting as Lapce in it's own right.

Re: Lapce

#152

Post by rpacut »

samtheprogram wrote: post #118
amelius wrote: post #104

Earlier quoted context omitted.

I'm often coding on a server with like 10ms round trip latency, so I'm not bothered by the small latency that my editor introduces. I'm using Vim, by the way.

Same, and despite this, Vim over SSH feels better than regular VSCode (assuming a decent internet connection).

Ever tried the Remote-SSH plugin from Microsoft? With it I had the exact opposite experience, I'd regularly forget I was working on a remote dev machine!

Re: Lapce

#153

Post by eikenberry »

zozbot234 wrote: post #142
lchen_hn wrote: post #85

What’s the benefit for a neovim user? Meaning I already got LSP, treesitter, it works in a terminal. I cannot think of a reason to even try this.

With neovim you're still dependent on plugins written in some scripting language, and their overhead can add up. Lapce plugins are compiled to WASM/WASI, so they should run a bit smoother.

Lua is not some random scripting language, it is designed for embedding and is very fast with minimal overhead. I'm not saying that using WAS* is bad but bashing Neovim when it uses the one of the best proven technologies for extension is just silly.

Re: Lapce

#154

Post by rplnt »

debrisapron wrote: post #25

I am constantly confused by text editors pitching themselves on speed. Is the world really full of developers going crazy with frustration because they’re waiting on vs code to do something? I opened a 100,000 line text file a few days ago & it rendered in like half a second, considering I do this about once a year it’s really more than good enough.

Gonna pile up. VS Code with barely any plugins on M1 is noticeably slower than IDEs I've used 15 years ago on a hardware from 20 years go. Slower to render, slower to react to my inpit. It's bordering on unusable on a x86 laptop from few years back.

Better showcase on how ridiculous the tech stack is would be to open a 500 line file with a code and scroll. Startup isn't great either, though it isn't comically bad as it used to be.

So yeah, I want to see the authors of any desktop software to address this modern problem of writing slow UI. Otherwise I might assume they don't care.

Re: Lapce

#155

Post by cal85 »

alluro2 wrote: post #3

Does anyone have insight into how Lapce and Zed compare to each other? I.e. what are the differences in project goals, current capabilities and roadmap? Thanks!

This is my question too. I think I’m going to have to try both. AFAICT so far, Lapce is ‘just’ someone’s open source project that has got popular, while Zed is made by a funded-looking startup with several employees that announced they were switching to open source just a couple of weeks ago. Zed also has Copilot built in. Both look like great editors at a glance. Zed has more easily findable information about their goals - there’s a blog and a roadmap on their site. (I guess with Lapce it might be possible to get a sense of goals/vision by sifting through GitHub issues and comments, which I haven’t done yet.)

Re: Lapce

#156

Post by roarcher »

dzhou121 wrote: post #145

Lapce dev here. Firstly sorry for the bad experience for some people. Just a bit of context here to explain the status of the project. The first line of code was started around 2018 as a personal project. And as of today, we still don't have anyone who works on it full time. We don't want to defend ourselves too much here, because there are very good quality code editors out there such as Helix, which is also communi…

Don't apologize! It's not like you've taken anyone's money. HN can be a tough audience, but I don't see any (serious) comments that are putting down what you've done--just pointing out issues they personally experienced. I posted one myself. Informal bug reports.

Honestly this is about what I'd expect from pre-alpha software, though I do agree with other commenters that that label should be more prominent on the website to manage expectations.

Taking on something like VS Code as a competitor is ambitious, as is building a native UI library from scratch. Personally I applaud your effort and I hope this project succeeds.

Re: Lapce

#157

Post by mark_l_watson »

Looks like it doesn’t support Lisp languages?

I like the idea of natively compiled editors - fast!

For two days, I have been using the Lem editor written in Common Lisp, super fast and responsive.

Re: Lapce

#158

Post by camel_gopher »

debrisapron wrote: post #25

I am constantly confused by text editors pitching themselves on speed. Is the world really full of developers going crazy with frustration because they’re waiting on vs code to do something? I opened a 100,000 line text file a few days ago & it rendered in like half a second, considering I do this about once a year it’s really more than good enough.

Is it as fast as vim or emacs? If not then a tough sell from my view. Same with chewing up cpu cores.

Re: Lapce

#159

Post by skykooler »

On Manjaro I opened it and it stuttered for a bit and then crashed my entire desktop to a TTY. I get that it's pre-alpha but I was not expecting it to be that unstable.

Re: Lapce

#160

Post by SpaghettiCthulu »

cultofmetatron wrote: post #7
alluro2 wrote: post #3

Does anyone have insight into how Lapce and Zed compare to each other? I.e. what are the differences in project goals, current capabilities and roadmap? Thanks!

it seemes closer ti what I actually need than zed. love zed's speed but remote development is mandatory in thus day and age

What makes you say that remote development is mandatory? I think it has less to do with "this day and age" and more to do with your current employment.
Post reply on HN