Please improve the UI before adding all the features of VSCODE but better :-)
On a positive note, just to be sure I tried to run Eclipse - its UI is much worse.
HN: please suggest open source code editor with great UI for MacOS.
Lapce
31–40 of 229 posts
Re: Lapce
#32I try this editor every few months to see how it's progressing and is still way too early to use as a daily driver.
People suggest this over Zed very frequently. In my experience Zed is way more mature and stable. That being said, it's no one near as usable as neovim with a good plugin setup, let alone a mature ide like Jetbrains products.
Jetbrains IDEs might be slow, but I'll get a hell of a lot more done in 8 hours with it. Once you learn to use the features well, it's incredibly powerful. I love vim, but generally use jetbrains.
If Jetbrains took 500ms to load a file vs 1ms to load, my productivity isn't going to change dramatically. It's fast enough. Yes initial indexing is slow, but it's easily worth it.
All this being said, I think Lapce is very informative as a resource to anyone trying to build an editor in rust.
Re: Lapce
#33As someone who uses Neovim, I would love to have a near-vim experience in something that has all of the convenience of VSC + a great plugin ecosystem. However, I'm not sure about the fact that in `normal` mode `:` just brings up the `cmd+shift+p` command dialog. Maybe I could get used to it, but the fact that something as simple as my muscle memory for "I'm in `normal` mode, better type `:w` just to make sure I've sa…
Not vim (by design) - but have you tried helix?
Re: Lapce
#34I'm not sure what the selling point is, not criticizing the product, but as an emacs user of some odd ten years, I feel like as soon as I open the page I should see _something_ that would entice me to switch.
Re: Lapce
#35Just installed this on windows 10. First time I tried to open it the window hung for 3 minutes until I killed it. The second time, I couldn't reposition the window by clicking and dragging. Third time I loaded it, it hung again. It's an exciting product pitch but isn't working for me. I see now that there's a "pre-alpha stage" disclaimer on the download page and wish that were in larger font.
How is a project with 30,000 GH stars a pre-alpha stage project?
It boggles the mind. Good for the team building this, lots of respect entering this crowded and race to the bottom pricing product. But I don’t get how this differs from vs code or why someone would be excited about it. I get the feeling people like trying new editors so they throw stars around for every ide project they come across.
None of the features advertised beat neovim nor does it have the crazy plugin ecosystem.
Re: Lapce
#36As someone who uses Neovim, I would love to have a near-vim experience in something that has all of the convenience of VSC + a great plugin ecosystem. However, I'm not sure about the fact that in `normal` mode `:` just brings up the `cmd+shift+p` command dialog. Maybe I could get used to it, but the fact that something as simple as my muscle memory for "I'm in `normal` mode, better type `:w` just to make sure I've sa…
What are you missing from neovim?
There are plenty of out of the box configs that do most of the work for the user in terms of configuration that begs the question: why demand vim in other code editors?
Re: Lapce
#37As someone who uses Neovim, I would love to have a near-vim experience in something that has all of the convenience of VSC + a great plugin ecosystem. However, I'm not sure about the fact that in `normal` mode `:` just brings up the `cmd+shift+p` command dialog. Maybe I could get used to it, but the fact that something as simple as my muscle memory for "I'm in `normal` mode, better type `:w` just to make sure I've sa…
Agreed. : should be standard Vim commands. Command pallete should be a separate keybind.
Re: Lapce
#38I 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 the small latencies that add up for me. I usually use a tmux + nvim setup, but for codebases that require a bit more language server support (eg. C++20 and sometimes Rust), I have a VS Code setup with the nvim plugin that I’ve spent way too many hours tweaking hot keys and things.
Despite all my tweaking, VSCode sometimes just feels like it’s a beat behind, and keyboard commands get dropped in the transition between panes and such. Even just scrolling with nvim keybinds feels a bit off. My key repeat rate is fairly high, and I’ll hold down ^D to skim through a source file. VSCode’s renderer struggles to keep up smoothly sometimes.
This is all nitpicky stuff, not enough for me to swear off VSCode or anything. But it’s just annoying enough that every once in a while I end up in some rabbit hole of VSCode internals and css tweaks, instead of doing actual work. Most coding does not require a ton of bouncing around, but it does feel very liberating to have confidence in my inputs as I navigate around.
Re: Lapce
#39I'm not sure what the selling point is, not criticizing the product, but as an emacs user of some odd ten years, I feel like as soon as I open the page I should see _something_ that would entice me to switch.
“All the features of vs code but ‘fast’” even though as you’ll read in this thread, people are highly questioning that assertion.
Re: Lapce
#40I 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.
Vscode is nearly unuseable when my 5 year old thinkpad isn't plugged in. So yeah.