What exactly does lightning fast mean? Is vim not lightning fast?
Lapce: Fast and Powerful Code Editor Written in Rust
11–20 of 64 posts
Re: Lapce: Fast and Powerful Code Editor Written in Rust
#12I 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?
Re: Lapce: Fast and Powerful Code Editor Written in Rust
#13Earlier quoted context omitted.
People who think the programming language magically makes bugs disappear don't know what they're talking about. Yes, Rust makes a few categories of bugs disappear, but there's a vast number of bugs that you can still easily create even using Rust with all linters you can find enabled... just saw on another thread someone complaining a Gemini (poor man's internet) server responded with a Rust panic coming from an `unw…
Well if you're not using unsafe, you would expect zero segfaults when using rust, no? Though I imagine it's impossible for anything with graphics to avoid unsafe code entirely.
> Yes, Rust makes a few categories of bugs disappear, but
Segfaults are only one of many ways for software to go wrong.
Re: Lapce: Fast and Powerful Code Editor Written in Rust
#14What 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.
Re: Lapce: Fast and Powerful Code Editor Written in Rust
#15Earlier quoted context omitted.
Hot Take: Rust Panic's are about as bad as Sig11s from the C world. I don't get good debug information in the typical case - and library authors get to decide when my program crashes (which I disagree with).
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.
I'd definitely go with throw - it's indicative of a logic bug, and I'd rather notice it during dev (or if not, catch in prod, complete with stack trace and whatnot), than to have it silently corrupting anything that relies on that calculation happening correctly, without me even being aware of it.
Like, if I'm doing x + y, and y just accidentally happens to contain the wrong data because of a mistake in the code, a NaN means the code will proceed as normal, and nobody will notice anything is wrong. If it's not a noticeable bug, it might be a long time until it's spotted by someone. And when they do, who knows how much damage it will have caused.
Re: Lapce: Fast and Powerful Code Editor Written in Rust
#16Earlier quoted context omitted.
Well if you're not using unsafe, you would expect zero segfaults when using rust, no? Though I imagine it's impossible for anything with graphics to avoid unsafe code entirely.
> Yes, Rust makes a few categories of bugs disappear, but Segfaults are only one of many ways for software to go wrong.
And all software that interfaces with... Well, anything, contains unsafe code.
Re: Lapce: Fast and Powerful Code Editor Written in Rust
#17>VSCode Remote Development
VSCode does this feature the best. No other IDE comes close. I'm a jetbrains guy and I would've given up on vscode completely if it were not for this feature. This thing is extremely important for embedded systems and development on the edge and only vscode really does it well enough to be useable.
Glad to see Lapce has it to. Going to try it out.
Re: Lapce: Fast and Powerful Code Editor Written in Rust
#18I 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 agree with your sentiment.
That said, I can totally see why it would matter to some people why language something is written in: you may want to study or contribute to an editor and you may prefer to focus on your preferred language
Re: Lapce: Fast and Powerful Code Editor Written in Rust
#19Earlier quoted context omitted.
Hot Take: Rust Panic's are about as bad as Sig11s from the C world. I don't get good debug information in the typical case - and library authors get to decide when my program crashes (which I disagree with).
You're not supposed to be afraid of segfaults, you're supposed to be afraid of the incorrect memory accesses that don't get caught by segfaults.
Yeah, the problem is when one of these faults comes from a 3rd party library and doesn't include stack trace info.
Re: Lapce: Fast and Powerful Code Editor Written in Rust
#20I 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?
- Truly open source, presumably without the caveats that VS Code has such as a few "features" (extensions) being closed source and the extension marketplace being closed to de-microsofted builds
- Designed from the beginning to support an extension API with a richness comparable to VS Code's (unlike Sublime, Jetbrains etc)
- Presumably aiming to put performance as a higher priority than is usual