Live data from Hacker News

Lapce – Fast open-source code editor

lapce.dev

191–200 of 231 posts

Re: Lapce – Fast open-source code editor

#191
post #89

No Electron? That is already one good thing ;) Why does Rust folks seem to encapsulate and separate their stuff more and more? Own build-tools and infrastructure are one thing. Am I right that Druid is not an very own Toolkit but a layer like WxWidgets?

Will people stop complaining about Electron once their machine has 8 or more GB of ram?

Re: Lapce – Fast open-source code editor

#192
post #15

Nowadays when I see "written in Rust" in the title, it reads like special pleading: "It's maybe not as good as what you use, but we are really proud to have got it working at all."

> we are really proud to have got it working at all On the contrary, the rust crate ecosystem and tooling means a lone developer can compose specialised libraries to produce a working artefact that scratches her own itch. Such productivity is the opposite of getting something working at all. Trying to build an OSS cpp project or even worse, use an OSS Cpp library in your own project is more along the lines of "gettin…

No post body was provided.

Re: Lapce – Fast open-source code editor

#193
post #15

Nowadays when I see "written in Rust" in the title, it reads like special pleading: "It's maybe not as good as what you use, but we are really proud to have got it working at all."

I don't understand this sentiment. Rust is the only language ecosystem where I find that anything works at all. Whenever I have to build something not built in rust, I'm praying. With rust made tooling, I just never have problems.

I don't know of any essential tool coded in Rust. Literally every single thing I rely on is coded in other some other language, and works. There is exactly one in Haskell: pandoc. No Java or C# (although I guess some people feel they need Minecraft or Kerbal Space Program). No Lisp, except Emacs. No Erlang, Clojure, Scala, OCaml, Dart, or Ada. Does TeX still count as Pascal?

The only case I know of where I would need a Rust program is to check a blake3 hash. That won't last.

Re: Lapce – Fast open-source code editor

#194
post #65

Author here. Thanks for all the feedback. I'm aware that Lapce lacks lots of basic stuff. It's a personal project so the initial set of features and key bindings are tight to my personal preferences. I'm currently working on the missing pieces, like multi cursor support(in master but not released yet), mouse support, sane default key bindings(probably I'll stick to an existing editor), basic UX etc. Feel free to subm…

Off Topic: https://www.lapce.dev has a certificate issue. Also, the editor does not seem to run on Windows 7 ("createpseudoconsole could not be located" in KERNEL32.dll)

Pseudoconsole/ConPTY is a big deal and this would need a complex fallback for Windows 7 and 8. Probably not worthwhile.

Re: Lapce – Fast open-source code editor

#195
post #193

Earlier quoted context omitted.

I don't understand this sentiment. Rust is the only language ecosystem where I find that anything works at all. Whenever I have to build something not built in rust, I'm praying. With rust made tooling, I just never have problems.

I don't know of any essential tool coded in Rust. Literally every single thing I rely on is coded in other some other language, and works. There is exactly one in Haskell: pandoc. No Java or C# (although I guess some people feel they need Minecraft or Kerbal Space Program). No Lisp, except Emacs. No Erlang, Clojure, Scala, OCaml, Dart, or Ada. Does TeX still count as Pascal? The only case I know of where I would need…

> No Java

I am not sure what "essential tool" means if pandoc included in it. For me Intellij, Eclipse, Dbeaver are more essential (+ few other Specific tools based on Eclipse).

C# - I am not sure, MS Office?

Re: Lapce – Fast open-source code editor

#196
post #15

Nowadays when I see "written in Rust" in the title, it reads like special pleading: "It's maybe not as good as what you use, but we are really proud to have got it working at all."

> we are really proud to have got it working at all On the contrary, the rust crate ecosystem and tooling means a lone developer can compose specialised libraries to produce a working artefact that scratches her own itch. Such productivity is the opposite of getting something working at all. Trying to build an OSS cpp project or even worse, use an OSS Cpp library in your own project is more along the lines of "gettin…

Correct use, documentation, and other concerns are imporant for all libraries, whether got via cargo or otherwise, so this amounts to special pleading again.

More importantly, though: how hard is it to use a library coded in C++ from your Rust program? You have to make and maintain some sort of shim layer. Even a C library needs some such effort. For any given need, you are much less likely to find an existing and suitable Rust library already written, released, and maintained than one in some other, more widely used, language.

Re: Lapce – Fast open-source code editor

#197
post #193

Earlier quoted context omitted.

I don't know of any essential tool coded in Rust. Literally every single thing I rely on is coded in other some other language, and works. There is exactly one in Haskell: pandoc. No Java or C# (although I guess some people feel they need Minecraft or Kerbal Space Program). No Lisp, except Emacs. No Erlang, Clojure, Scala, OCaml, Dart, or Ada. Does TeX still count as Pascal? The only case I know of where I would need…

> No Java I am not sure what "essential tool" means if pandoc included in it. For me Intellij, Eclipse, Dbeaver are more essential (+ few other Specific tools based on Eclipse). C# - I am not sure, MS Office?

I acknowledge that some people depend on Java and even C# programs.

Re: Lapce – Fast open-source code editor

#198

Earlier quoted context omitted.

At least they went with "lighting-fast" instead of "blazing-fast"

“Lightning fast” is no less meaningless in practice than “blazing fast”. Both get used extensively by projects in such languages as JavaScript and Rust, on projects of similar scope that nonetheless have at least an order or two of magnitude’s performance difference.

If the title claims "lightning fast" or "blazing fast", I expect to see quantitative comparisons to alternatives. Which operations are faster than in other programs?

alacritty is a Rust program that is promoted as uniquely fast, but is substantially slower than (e.g.) kitty.

Re: Lapce – Fast open-source code editor

#199

Earlier quoted context omitted.

“Lightning fast” is no less meaningless in practice than “blazing fast”. Both get used extensively by projects in such languages as JavaScript and Rust, on projects of similar scope that nonetheless have at least an order or two of magnitude’s performance difference.

Vite is a tool that deserves this moniker

What would one use Vite in place of?

Re: Lapce – Fast open-source code editor

#200
post #143
post #136

Earlier quoted context omitted.

That should really apply to any systems language other than C for a text editor. As long as you have bounds checking and a test suite you're golden.

> As long as you have bounds checking and a test suite you're golden. And other hilarious jokes you can tell yourself

I wouldn't recommend such a simple approach for something like a compiler, but for a text editor I don't think it's unreasonable. How many allocations can it actually need within any given subsystem which you can test individually?
Post reply on HN