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

Lapce: Fast and Powerful Code Editor Written in Rust

github.com

Post reply on HN
Print view View original

21–30 of 64 posts

Re: Lapce: Fast and Powerful Code Editor Written in Rust

#21

Post by zokier »

truculent wrote: post #10
threatofrain wrote: post #7

Earlier quoted context omitted.

On a tangent — for a numeric library, would you rather NaN or throw? I find a fair amount of division over this question, but people lean towards throw over NaN.

If the operation can fail, that should really be represented in the type, right?

One of my random thoughts is that floats could be represented as enums in type system, e.g. in rust-like syntax:

    #[repr(f32)]
    enum Float32 {
        PositiveInfinity,
        NegativeInfinity,
        Nan(NanPayload32),
        Finite(FiniteFloat32),
    }
You could also then define NonNanFloat32 etc which could be used for certain operations. Of course on machine level its all the same

Re: Lapce: Fast and Powerful Code Editor Written in Rust

#22

Post by duped »

KolmogorovComp wrote: post #12

I don’t care in which language my editor is written in. From the user perspective, what sets it apart from the plethora of available and more mature editors?

It's slower, tbqh. It choked on a decent sized Rust project (scrolling became laggy/unusable) that VS Code handles fine.

Re: Lapce: Fast and Powerful Code Editor Written in Rust

#23

Post by ingenieroariel »

I tried it last month and loved having Alacritty there. It built easily and ran well on both OSX and Fedora Asahi Linux.

That said, it does not seem yet ready to be a daily driver, small rough edges in the terminal behavior or the editor when using Vim mode were too distracting to do a long programming session.

Kudos to the authors, looking forward to giving it a spin again the future.

Re: Lapce: Fast and Powerful Code Editor Written in Rust

#24

Post by lynndotpy »

KolmogorovComp wrote: post #12

I don’t care in which language my editor is written in. From the user perspective, what sets it apart from the plethora of available and more mature editors?

I like knowing something is written in Rust because (1) the staying power of a language has implications for the staying power of the project (how many Ada projects do you see nowadays?) (2) I write Rust so I'm more likely to contribute to this, (3) I care about the safety and speed implications of language choice, but most of all (4) building from source usually isn't a pain with Rust's Cargo, but it is for most other languages.

All these things materially impact how interested I am in using and contributing to the project.

Re: Lapce: Fast and Powerful Code Editor Written in Rust

#25

Post by corethree »

code-blooded wrote: post #14
thefaux wrote: post #11

What exactly does lightning fast mean? Is vim not lightning fast?

To be devil's advocate (despite being a long vim user): Lapce has a GUI, so they are not in the exact same category. Having lightening fast GUI is still a novelty, because the most popular IDEs like VSCode or JetBrains IDEs have slow downs from time to time.

It's not the GUI itself. A console application in a window is still a gui rendering console text. It's the fact that Vscode and jetbrains use a high level language/engine that makes it slow.

For jetbrains it's java and for vscode it's an html rendering engine. An IDE built from vulkan or some other low level graphics API can likely be even faster then vim depending on the console it's running within.

Re: Lapce: Fast and Powerful Code Editor Written in Rust

#26

Post by flohofwoe »

KolmogorovComp wrote: post #12

I don’t care in which language my editor is written in. From the user perspective, what sets it apart from the plethora of available and more mature editors?

For starters, it doesn't seem to use a browser engine to render its UI. Seems to aim for a VSCode look and feel. Installation on macOS is about a third of the install size of VSCode (105 MB vs 330 MB), and it's a single statically linked executable (vs a plethore of files in a VSCode installation).

Re: Lapce: Fast and Powerful Code Editor Written in Rust

#27

Post by dang »

Related:

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)

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

Re: Lapce: Fast and Powerful Code Editor Written in Rust

#28

Post by hnlmorg »

code-blooded wrote: post #14
thefaux wrote: post #11

What exactly does lightning fast mean? Is vim not lightning fast?

To be devil's advocate (despite being a long vim user): Lapce has a GUI, so they are not in the exact same category. Having lightening fast GUI is still a novelty, because the most popular IDEs like VSCode or JetBrains IDEs have slow downs from time to time.

The IDE is only going to be as fast as the slowest LSP service you’re using.

Re: Lapce: Fast and Powerful Code Editor Written in Rust

#29

Post by schemescape »

duped wrote: post #22
KolmogorovComp wrote: post #12

I don’t care in which language my editor is written in. From the user perspective, what sets it apart from the plethora of available and more mature editors?

It's slower, tbqh. It choked on a decent sized Rust project (scrolling became laggy/unusable) that VS Code handles fine.

That seems "open a bug" worthy, for a "lightning-fast" editor.
Post reply on HN