Earlier quoted context omitted.
How is a project with 30,000 GH stars a pre-alpha stage project?
Probably because it says in Rust. In Rust we trust.
It doesn't work but it's memory safe in being non-functional
Lapce
71–80 of 229 posts
Re: Lapce
#72I still don't understand how Zed or Lapse can build a viable business out of an OSS editor but at the same time there is an OSS VC funded Python linter so it's probably me.
As far as I know Lapce is not business.
Re: Lapce
#73I 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 hour…
I've tried Lapce several times over the past year or 2, and have never gotten more than 5 minutes in without it hanging or crashing. I wish I was a rust programmer, but Lapce is not a good poster-child for the language, IMO.
It's not the speed, or even the phoning home that make me rage-quit VSCode on the regular. It's the RAM. EVERYTHING slows down if you only have 24GB and try to use VSCode.
Re: Lapce
#74I'm shopping for an IDE with Vim keybindings, but this doesn't seem to be it yet. Points for having Vim-like support out of the box, but most of what I tried failed, including:
- Exiting insertion mode with ctrl+c or ctrl+[
- Shift+U to undo all changes done to the current line
- `di[` to delete the contents inside the current [
- `dta` to delete everything until the next `a`
- Shift+[ and shift+] to jump paragraphs
- Shift+D to remove everything until the end of the line
- `.` to repeat the last action
It's a good start, and I'll definitely check it again in the future, but I'd hold on advertising "Vim-like" editing until the support gets better.
The rest of the editor is awesome, no complaints so far.
Re: Lapce
#75I 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.
Yes. I have an org issued machine with crap specs and dozens of repos I switch between all day long. Waiting 30s-2m doesn't sound like much but it breaks flow and leads to a lot of "what was I doing again...?" Sidetracks
Sounds like your org is bad at basic arithmetic. 12230s = 12 minutes per day minimum. Assuming an engineering salary at perhaps 100k usd /year, that is about 40,7 usd per hour, they would save money by giving you a max specced frame.work(2500$) after 307 days (maximum). Assuming you do this more than “2 dozen” times per day, as you say “all day long”, at minimum they would make that money back in 7.7 days. The same numbers for a max specced MacBook Pro (at 7200 usd) is 22.1 to 884,5 days.
I get mad at this attitude from some companies. It’s like telling a carpenter that they have to build a house, but are not allowed power tools. It makes no sense.
Edit: typo
Re: Lapce
#76Earlier quoted context omitted.
Okay, just as a counterpoint, I opened 2 10,000 line files and tried to do a diff between them in VSCode. It took more than 20 seconds? Yes, it breaks workflow and is incredibly slow. Just like refreshing elements in UI shouldn't take multiple seconds, or a webpage shouldn't take multiple seconds to load on a good connection.
I tried the same in my Linux terminal emulator, and it took 0.2s, when I added colors, 0.3s. That's 100x faster - maybe diff in VSCode means something different than running diff and printing the output? Did you include the time needed to open the files?
Yes, the files themselves open quite quickly, but I will admit that it's a complicated diff (lots of expected differences), and VSCode is not primarily a diff tool.
But also 10k line file should be nothing for a modern PC.
Re: Lapce
#77I 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.
I have a sneaking feeling that the people who use only their keyboards to navigate are the ones who really notice latency in e.g. VSCode.
I navigate with the trackpad on a Mac and seem not to ever feel it, but I know others do not like this way of working, which is fair enough.
Lapce is interesting to me for other reasons: it is one of the few[0] GUI text editors with a remote dev option that matches what VSCode can do. And it might have a smaller footprint on the remote machine/in the container while doing it.
VSC’s remote dev support is very nearly non-negotiable for me now, so I say more power to them; I intend to try it again properly soon.
[0] there is another editor that was mentioned here recently that can achieve this with a plugin, but I forget the name
Update: Zed is that editor.
Re: Lapce
#78It's refreshing to see a new IDE that isn't using Electron. Yes, I know Zed is native as well, but it only is macOS compatible, and I use Linux.
I am using Qt Creator, and it is absolutely amazing for C++/CMake based development, but I will have to give Lapce a try and see how it stacks up.
Re: Lapce
#79I 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 bet…
You are a data point for the notion I mention in my own reply to the parent that keyboard-only navigators might be feeling this more than mouse/trackpad users. Which seems likely to me.
Re: Lapce
#80Just 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.
There are plenty of issues like this in Lapce (no support beyond qwerty layout for instance). Just go for Zed instead.
https://github.com/lapce/lapce/issues/945#issuecomment-12853...