Live data from Hacker News

Lapce

lapce.dev

211–220 of 229 posts

Re: Lapce

#211
post #154

Earlier quoted context omitted.

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…

What IDE do you use nowadays if not VS Code? I'm curious because I'm also using an M1 Mac and I've ran through the gamut (Sublime, PyCharm, Atom, etc).

Sublime mostly, not a fully-featured IDE I'd say. For front-end I'm using VS Code, that's only here and there, and that's where the struggle comes from.

Last time I've tried Idea/etc was quite a few years ago. It didn't feel great. But maybe I should force myself into it. Might be better on M1.

I also open regular Visual Studio every few months for C# on Windows, and while it's slow to start, the editor feels really solid, quick, and responsive.

Re: Lapce

#212
post #144
post #107

Earlier quoted context omitted.

Wow, that's a great way to phrase it. I'm currently setting up a basic laptop with speed like you're describing as a goal. "Confidence in my inputs" is an underrated value in HCI. Of course websites have to implore users to not click on this again while it loads, they don't have confidence in their inputs!

Something actively dropping inputs is an entirely different category of problem than it merely being slow to process them.

Yes, But for "confidence in inputs" the difference doesn't matter.

Re: Lapce

#213

I try this editor every few months to see how it's progressing and is still way too early to use as a daily driver. People suggest this over Zed very frequently. In my experience Zed is way more mature and stable. That being said, it's no one near as usable as neovim with a good plugin setup, let alone a mature ide like Jetbrains products. Jetbrains IDEs might be slow, but I'll get a hell of a lot more done in 8 hour…

I too use intellij and neovim for everything and agree mostly, but what's your motivation to check out new editors? Is it for just for fun? In my mind an editor is one of those things I wouldn't consider changing unless the alternative is heavily funded and leagues much better than my current choice.

I try new stuff regularly. People can build cool stuff. Google is releasing a new IDE soon. I'll try it. Cursor.so is a cool idea. I tried it. Zed sounds great (I love high performance) so I tried it. Haven't switched yet though!

But I was 100% vim for years and over time, slowly started using intellij and friends. I hated how slow it felt. But as I learned the features, it became a no-brainer.

If I didn't try new stuff I wouldn't have used it.

I did the same thing with terminals for a while, and settled on Kitty. (I'd never use fig / warp). Speaking of which, IntelliJ 2024 EAP terminal is horrific. I had to downgrade.

Re: Lapce

#214
post #186

Earlier quoted context omitted.

> with a more innovative editing model than vim's I think Helix tries to do that

Kakoune too. But if a project focuses on a novel editing model and not some other aspect of an editor, then implementing it inside Emacs might be the best approach. If implemented inside Emacs, then it composes with the rest of its package ecosystem. Kakoune, Helix, etc. are somewhat set back by having to reproduce functionality equivalent to Magit, Org, LSP mode, and so on in order to be on equal footing for many us…

I don't have a lot of experience with Emacs, let alone evil (and none at all with meow or god). But my experience with it was that evil felt distinctly.. hacky? For example, Evil felt like it interfered with selecting restarts in Sly.

I've had similar issues with VscodeVim being weird in VSC. Ultimately the text editor is so core to a text editor (duh) that deeply modifying it is bound to give a worse experience than implementing it from scratch, even if it does give you a lot of nice stuff 'for free'.

Re: Lapce

#215

I could use a decent Rust IDE. I can't believe I'm saying this, but the VSCode plugin for Rust seems to be the best there is at the moment, way better than the JetBrains plugin. This cannot be the last word on that.

Ultimately, for Rust all you really need is an editor with good LSP support. rust-analyzer offers a lot of what you could want out of an IDE (although when trying RustRover I noticed some other nice things such as the ability to 'factor out' a function from a selection, which I don't think I was able to do with RA).

Which editor that is doesn't really matter. VSCode is probably easiest, but Neovim, Kate, LiteXL, Lapce, Emacs, kakoune, helix, really pretty much all of them should work decently well.

Re: Lapce

#216
post #89

Earlier quoted context omitted.

The nightly builds got word wrap a few weeks ago, not been released yet afaik, but will be in the next one.

Thank you for letting me know! I will definitely be giving it a try! Can it wrap at column 80 or does it only wrap at the right border of the window?

Apparently, currently based on width: https://github.com/lapce/lapce/commit/87e0fc06f1862d9124d3fe...

Re: Lapce

#217
I like lapce. Its simple and easy to use. Ive switched to using the terminal for now but I do like using it from time to time.

its also kind of hilarious to watch people be like "why would we need another editor" and then turn around and POG at Zed lmao

Re: Lapce

#218

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…

I think it might be better for all if the landing page was geared more to contributors (coders and bug finders) as opposed to end users.

From Servo's site:

> These pre-built nightly snapshots allow developers to try Servo and report issues without building Servo locally. Please don’t log into your bank with Servo just yet!

Though I'll say even Servo's site is lacking too.

Re: Lapce

#219
post #33

Earlier quoted context omitted.

Not vim (by design) - but have you tried helix? https://helix-editor.com

Helix is a dream, as far as I can say from having played a lot with it, but only played. To be fully comparable to some IDE or Neovim setup like LazyVim, you need to complement it with other tools and use some workarounds, e.g. working the files (tree) or custom snippets. (I'm still using VS Code to get my stuff done, but in a couple of weeks I got some time to spent to re-evaluate Helix and Neovim.)

You can use a snippet LSP to work around Helix not having a built-in LSP manager. They're listed in https://github.com/helix-editor/helix/issues/395

Re: Lapce

#220
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!

From a developer perspective, Zed's licensing prevents it from being used/inspected outside of the context of other GPL projects. For example, Helix can't use nor read any of the code in Zed because it would pollute the licensing.
Post reply on HN