It looks really promising. I wonder why code editors have the file explorer on the left side by default, if you resize it you move the whole text (unless you write in a right-to-left language). A colleague made me aware of this a while ago and I cannot stop wondering. I moved it to the right ever since.
Lapce – Fast open-source code editor
21–30 of 231 posts
Re: Lapce – Fast open-source code editor
#22It looks really promising. I wonder why code editors have the file explorer on the left side by default, if you resize it you move the whole text (unless you write in a right-to-left language). A colleague made me aware of this a while ago and I cannot stop wondering. I moved it to the right ever since.
Hm, it depends how you use it, I would say. I totally agree that in a ltr context left side screams "focus point". On the other hand, the project drawers/file explorer is mostly toggled off while I work, so it doesn't take any screen real estate. And when I need it, it makes sense to be on the left side. I prefer to explore via some search mechanism though. Project drawers are only needed for special cases, like gett…
Re: Lapce – Fast open-source code editor
#23Are they using the linkin park logo?
When I thought about Lapce's logo, I took the initials of "Lightning" and "Powerful", so put L and P together to form a logo.
I guess Linkin Park is L and P too.
Re: Lapce – Fast open-source code editor
#24Re: Lapce – Fast open-source code editor
#25- a single binary you can drop in ~/bin
- native Linux version
- really, really fast
- git branches in the top bar by default
Cons (beside being super new and lacking ecosystem):
- Use a custom window border, which is also pretty ugly IMO
- cannot use arrow keys in the command palette (or any file dialog). I guess it's a bug?
- default key bindings are... weird? ctrl+f doesn't prompt a find box for example
- cannot make syntax highlight work even on common formats like MarkDown, JSON or YAML
So, it feels very immature but for sure it is a great starting point, if I get good syntax highlight and code completion with a LSP (although it should already work) I might see me switching from VS Code to it, at least partially.
Re: Lapce – Fast open-source code editor
#26.msi installer marked as Unsafe.
Re: Lapce – Fast open-source code editor
#27I think it's a great project with a lot of potential, but I'll give it at least a year or two before general usability.
Re: Lapce – Fast open-source code editor
#28Nowadays 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."
Free market forces based on individual self-interest have proven to be really bad at doing that, so altruism is needed to fill the gap.
...by that logic, I prefer software written in Rust to software written in C++ or Java Script even if it's worse from a user perspective, as long as it's tolerably worse rather than just unusable.
Re: Lapce – Fast open-source code editor
#29It looks really promising. I wonder why code editors have the file explorer on the left side by default, if you resize it you move the whole text (unless you write in a right-to-left language). A colleague made me aware of this a while ago and I cannot stop wondering. I moved it to the right ever since.
the main reason I change the sidebar's width is to recenter my text depending on my position in front of my screen aha... guess it's a case of the 1172s
Re: Lapce – Fast open-source code editor
#30I would love to know if the IDE frontend could be compiled to Wasm (using WebGL/WebGPU under the hood) so it could run in the browsers, similarly to Makepad [2]