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

41–50 of 229 posts

Re: Lapce

#41

Post by franky47 »

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.

Frustration often comes with extensibility: adding extensions on top of VSCode that need to run at file save time (eg: formatters) can lead to pretty significant performance drops.

This extensibility is probably what made VSCode popular though, especially for web devs since the extension mechanism is JavaScript-based.

Makes me wonder if those Rust-based tools (Lapce, Zed) will have as much success with Rust-based extensions authoring.

Re: Lapce

#42

Post by sph »

Making a fast editor is such a common hobby, everybody seems to be working on one these days apparently, yet memory safety and speed has never been a real problem in editors.

It would be much more impressive to explore a novel approach for editors more extensible than Emacs, or with a more innovative editing model than vim's.

If we are reinventing the wheel, why not at least try to make a better wheel that's never been done before?

Re: Lapce

#43

Post by ribelo »

e12e wrote: post #33
29ebJCyy wrote: post #16

As someone who uses Neovim, I would love to have a near-vim experience in something that has all of the convenience of VSC + a great plugin ecosystem. However, I'm not sure about the fact that in `normal` mode `:` just brings up the `cmd+shift+p` command dialog. Maybe I could get used to it, but the fact that something as simple as my muscle memory for "I'm in `normal` mode, better type `:w` just to make sure I've sa…

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

Helix is a very good and well-managed project, but it's quite hostile towards its own community. There are no plugins, and they won't be in Wasm like users want, but in Scheme dialect named Steel, that nobody want... if at all. Missing features like copilot or file browser expected by the community are essentially never merged into the master. This might be a better path than total dispersion and destruction of what works, but my expectations do not align with what the creators offer, so I give them the freedom to choose. I keep my fingers crossed for its development, but I personally use something else.

Re: Lapce

#44

Post by jahsome »

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.

Yes. I have an org issued machine with crap specs and dozens of repos I switch between all day long. Waiting 30s-2m doesn't sound like much but it breaks flow and leads to a lot of "what was I doing again...?" Sidetracks

Re: Lapce

#45

Post by FpUser »

jjallen wrote: post #23
whats_a_quasar wrote: post #9

Just installed this on windows 10. First time I tried to open it the window hung for 3 minutes until I killed it. The second time, I couldn't reposition the window by clicking and dragging. Third time I loaded it, it hung again. It's an exciting product pitch but isn't working for me. I see now that there's a "pre-alpha stage" disclaimer on the download page and wish that were in larger font.

How is a project with 30,000 GH stars a pre-alpha stage project?

Probably because it says in Rust. In Rust we trust.

Re: Lapce

#46

Post by tuan »

twp wrote: post #18
29ebJCyy wrote: post #16

As someone who uses Neovim, I would love to have a near-vim experience in something that has all of the convenience of VSC + a great plugin ecosystem. However, I'm not sure about the fact that in `normal` mode `:` just brings up the `cmd+shift+p` command dialog. Maybe I could get used to it, but the fact that something as simple as my muscle memory for "I'm in `normal` mode, better type `:w` just to make sure I've sa…

Use https://github.com/vscode-neovim/vscode-neovim instead.

Since v1.0+ of this extension I have been constantly having issues with neovim's and VSCode's buffers got out of sync. I cannot reliably reproduce the issues however. There are a few similar reports, e.g. https://github.com/vscode-neovim/vscode-neovim/issues/1624. I've switched to other VIM extension (VSCodeVim) which I found more reliable, albeit less powerful.

Re: Lapce

#47

Post by baby »

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.

I think it's just that everybody has been looking for THE editor, and so it is natural that people would develop their own. I think what we're seeing is that VSCode is becoming THE editor (if it's not already there). At this point it's hard to compete. I think the biggest contender is IntelliJ, as many people really seem to enjoy it, but I would predict that it's going to be hard to fight against free.

Re: Lapce

#48

Post by antisthenes »

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.

Okay, just as a counterpoint, I opened 2 10,000 line files and tried to do a diff between them in VSCode. It took more than 20 seconds?

Yes, it breaks workflow and is incredibly slow.

Just like refreshing elements in UI shouldn't take multiple seconds, or a webpage shouldn't take multiple seconds to load on a good connection.

Re: Lapce

#49

Post by anton-107 »

Sytten wrote: post #26

I still don't understand how Zed or Lapse can build a viable business out of an OSS editor but at the same time there is an OSS VC funded Python linter so it's probably me.

getting acquired by a big tech who wants to catch up with Microsoft's dominance in developer tools is one possible out

Re: Lapce

#50

Post by oorza »

Opened in macOS and it appears impossible to open a folder of any sort. I type the folder path into the Open Folder thing at the top and it just silently fails.

There's no menu or anything to open a folder either. This seems lacking some _basic_ UX principles that should never be overlooked.

I did eventually figure it out and the TS integration doesn't work at all. The file browser icons constantly and consistently do not render correctly.

Guess this is something to check back in on in a year or three. It's a long way away from being complete, let alone usable.

Post reply on HN