Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lapce

lapce.dev

Post reply on HN
Print view View original

101–110 of 229 posts

Re: Lapce

#101

Post by lsllc »

29ebJCyy wrote: post #16

As 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…

Neovim with Lazyvim is pretty good out of the box. In the old days, both Emacs and (Neo)vim although highly extensible, well, it was hard to configure and set up for the things you wanted to do.

Now, we have Spacemacs, Doom Emacs and Neovim with Lazy, Packer etc., so I really can have a 1st class "IDE" without needing to learn LISP or Vimscript (or Lua). So you do need a little bit of that to be able to edit the package.el or init.lua, but it's pretty much uncomment or cut & paste.

If you're looking for a (Neo)vi(m) tutorial, try this:

https://www.barbarianmeetscoding.com/boost-your-coding-fu-wi...

Re: Lapce

#102

Post by nox101 »

SCdF wrote: post #93
debrisapron wrote: post #25

I 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 would invert that: when was the last time you tried using a text editor that boasts speed instead of VSCode? I am forced to use VSCode for extension-based reasons, but have Sublime Text installed as well that I can very occasionally use. The difference each time is staggering, like a slap in the face. Scrolling smoothness, input latency, snappyiness to jump between files, or search workspaces. Each time it's so obv…

my machine must be faster than yours. I have both. I can't tell the difference

Re: Lapce

#103

Post by jimbokun »

reaperman wrote: post #83
Cort3z wrote: post #75

Earlier quoted context omitted.

Sounds like your org is bad at basic arithmetic. 12 2 30s = 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…

Except carpenters bring their own tools, so they can determine the price: value that’s right for their pocketbook.

A lot of developers would be ecstatic to have a tools allowance and the ability to use whatever laptop they buy on the corporate network.

Re: Lapce

#104

Post by amelius »

SCdF wrote: post #93
debrisapron wrote: post #25

I 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 would invert that: when was the last time you tried using a text editor that boasts speed instead of VSCode? I am forced to use VSCode for extension-based reasons, but have Sublime Text installed as well that I can very occasionally use. The difference each time is staggering, like a slap in the face. Scrolling smoothness, input latency, snappyiness to jump between files, or search workspaces. Each time it's so obv…

I'm often coding on a server with like 10ms round trip latency, so I'm not bothered by the small latency that my editor introduces. I'm using Vim, by the way.

Re: Lapce

#105

Post by FpUser »

bloopernova wrote: post #92
veber-alex wrote: post #84

Earlier quoted context omitted.

It's like phones with 120Hz displays. You don't know you need it but once you have it it's hard to go back.

Similarly with monitors, 60Hz LCD panels are OK, but 120Hz panels are just so much easier on the eyes. At least for me. Try dragging windows around or scrolling quickly, and you'll see the difference between 60 and 120 very fast.

I can spot the difference but the value proposition is zilch to me. I would not pay 1 extra cent for it. If I was a gamer this would of course matter.

Re: Lapce

#106

Post by nickstinemates »

whats_a_quasar wrote: post #9

Just 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.

Portable version loaded instantly for me on Windows 10. Remote SSH functionality doesn't work at all unfortunately[1]. Would be nice to try out but I don't do any local dev.

1: https://github.com/lapce/lapce/issues/2985

Re: Lapce

#107

Post by dleink »

mafuyu wrote: post #38
debrisapron wrote: post #25

I 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…

Wow, that's a great way to phrase it. I'm currently setting up a basic laptop with speed like you're describing as a goal. "Confidence in my inputs" is an underrated value in HCI. Of course websites have to implore users to not click on this again while it loads, they don't have confidence in their inputs!

Re: Lapce

#108

Post by lrhegeba »

nox101 wrote: post #102
SCdF wrote: post #93

Earlier quoted context omitted.

I would invert that: when was the last time you tried using a text editor that boasts speed instead of VSCode? I am forced to use VSCode for extension-based reasons, but have Sublime Text installed as well that I can very occasionally use. The difference each time is staggering, like a slap in the face. Scrolling smoothness, input latency, snappyiness to jump between files, or search workspaces. Each time it's so obv…

my machine must be faster than yours. I have both. I can't tell the difference

i guess which and the number of extensions will have a significant effect on lag

Re: Lapce

#109

Post by akdjidensb »

debrisapron wrote: post #25

I 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 less about waiting for vscode to do something and more about the general feel and experience of movement and typing in the editor.

"Speed" is probably the wrong word, it's latency that matters.

Re: Lapce

#110

Post by rstat1 »

spullara wrote: post #60
debrisapron wrote: post #25

I 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.

Just a bunch of people optimizing for the wrong thing.

Optimizing for efficiency and performance is never "the wrong thing"
Post reply on HN