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

161–170 of 229 posts

Re: Lapce

#161

Post by School-Cotton »

camel_gopher wrote: post #158
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.

Emacs is not known for being particularly fast.

Re: Lapce

#162

Post by ribelo »

e12e wrote: post #135
ribelo wrote: post #43

Earlier quoted context omitted.

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…

As a user, I certainly do not find it hostile. In a "batteries included" edit a service like copilot that expose all data to a third party is a terrible anti-feature. As for script-oriented plugins vs wasm - I see a tradeoff - and don't think neither are right or wrong. Cross editor plugins via a common wasm api might be fun, but perhaps not very practical. Edit: link to relevant issues and discussion: https://github…

Copilot has many fans, and for many, the ability to use Copilot is more important than all the other "batteries-included" features. It's not for me or anyone else to judge. Everyone should make their own choices.

Regarding plugins, I'm with Helix from the beginning, i have read everything, and I understand the motivation well and can accept it. Perhaps this is what the ideal editor looks like for creators, but it definitely doesn't look like the ideal editor for me. I respect their decision, but I'm sticking with Neovim and might switch to ZED when Linux support becomes available.

Re: Lapce

#163

Post by maccard »

Daeraxa wrote: post #129
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'm on the team working on Pulsar, the community fork of Atom. You have no idea how much we hear "Atom is slow", "are you making it fast?" etc. I have honestly yet to work out exactly what is meant by it. Startup times, sure, you are never going to get Pulsar/Atom or VSCode to launch as fast as a terminal editor or a super lightweight native one but that isn't how I personally use that kind of editor - once it is ope…

> Startup times, sure, you are never going to get Pulsar/Atom or VSCode to launch as fast as a terminal editor or a super lightweight native one

Would you consider something like emacsclient's approach - a daemon running in the background that a window connects to?

Re: Lapce

#164

Post by ribelo »

jupblb wrote: post #63
ribelo wrote: post #43

Earlier quoted context omitted.

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…

"good and well-managed" vs "[merges everything] users want" - pick one

I pick to stay with neovim.

Re: Lapce

#165

Post by perrygeo »

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.

It's not about speed in terms of absolute cumulative time. It's about the interleaving, the user experience of latency, and the effect that has on our cognition.

A few ms of noticeable latency here and there, a few hundred ms freeze every once in a while, it's maybe an extra minute per day in clock time. If it was just a 1 minute startup penalty, that would be different. But this 60,000 ms is split up throughout the working day into hundreds of small pauses, making the system feel laggy and unpredictable. If you're lucky, it's merely a subconscious drag on your attention. If you're unlucky it will, have you constantly breaking concentration to wonder "is my editor frozen? Oh wait, never mind." Hundreds of times a day.

Now contrast that to a text editor with literally zero instances of noticeable lag. It's not that it has zero latency, it's that the I/O latency on modern hardware is faster than our fingers and eyes can work. So we don't experience it.

Hundreds of noticeable pauses versus zero pauses. Once you cross the threshold below which our fingers type and brain can read, you're lag free. Getting a faster text editor doesn't just slightly improve the lagginess, it completely solves it.

Re: Lapce

#166

Post by dan-allen »

SCdF wrote: post #93
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 would invert that: when was the last time you tried using a text editor that boasts speed instead of VSCode? I am forced to use VSCode for extension-based reasons, but have Sublime Text installed as well that I can very occasionally use. The difference each time is staggering, like a slap in the face. Scrolling smoothness, input latency, snappyiness to jump between files, or search workspaces. Each time it's so obv…

I have exactly the same workflow: VSCode when I want a specific extension and Sublime as a fallback.

I think a lot of people don’t notice the difference but I can’t un-notice it.

Huge generated files and whatnot, VSCode just spins but Sublime opens them instantly.

Not to knock VSCode: it’s amazing what they’ve done especially comparing it to other web-stack apps (like what is Slack doing that it’s slower than VSCode with 6 extensions running?!).

Even when things are running smoothly, the just-perceptible delay in switching files or a slight stutter scrolling feels like the digital equivalent of working with a cheap tool.

The cheap ratchet is a little sloppy and occasionally the pawl doesn’t catch but it still does all the same stuff. Yet Snap-On still has customers.

Re: Lapce

#167

Post by dang »

Lapce: Fast and Powerful Code Editor Written in Rust - https://news.ycombinator.com/item?id=38796524 - Dec 2023 (63 comments)

Lapce Editor 0.3 - https://news.ycombinator.com/item?id=38262775 - Nov 2023 (98 comments)

Lapce – A code editor with LSP and DAP support - https://news.ycombinator.com/item?id=38100570 - Nov 2023 (2 comments)

Lapce Editor, Release v0.2.0 - https://news.ycombinator.com/item?id=32714191 - Sept 2022 (40 comments)

Lapce – Fast open-source code editor - https://news.ycombinator.com/item?id=30708505 - March 2022 (224 comments)

Show HN: Lapce – open-source code editor inspired by Xi-editor - https://news.ycombinator.com/item?id=30526693 - March 2022 (2 comments)

Lapce – Fast and Powerful Code Editor written in Rust - https://news.ycombinator.com/item?id=29549173 - Dec 2021 (145 comments)

Re: Lapce

#168

Post by denysvitali »

skykooler wrote: post #159

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.

To be honest, if an application manages to crash your whole Window Manager, I don't think it's the fault of the application

Re: Lapce

#169

Post by [deleted] »

nicoburns wrote: post #140
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 the world really full of developers going crazy with frustration because they’re waiting on vs code to do something? Absolutely. How new/fast is your developer machine? A lot of developers are working on computers that are several years old and may not have been that high-spec to begin with. It's generally not basic editing that's slow on it's own. It's trying to run several editor windows at once (say a fronten…

[deleted]

Re: Lapce

#170

Post by jmrm »

rplnt wrote: post #154
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…

Some people need to use at least one time in life IDEs like Visual Basic 6 in a Pentium 4 to feel what it's like to use a fast IDE
Post reply on HN