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

81–90 of 229 posts

Re: Lapce

#81

Post by bemusedthrow75 »

Keyframe wrote: post #57
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.

For me it's the latency. It's not a deal breaker, of course. It's more of a first world problem akin to I don't know, guitars? High vs low action if you know guitar "problems". There's no coding problem where it's dependent on speed of typing; programming is mostly about reading anyways. It's more about the feel of it, like we're picky about keyboards and touch feedback we get. I guess spoiled, but nonetheless...

Hm, except high action is also a positive choice for some, not an inherent problem.

(Though I like the attempt at an analogy and I see how it works for you at least)

I am a high-action player —- I know I know, a monster! (but also a brass and heavy glass slide player)

Re: Lapce

#82

Post by verve_rat »

kjqgqkejbfefn wrote: post #80
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.

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

How are they going to run Zed on Windows?

Re: Lapce

#83

Post by reaperman »

Cort3z wrote: post #75
jahsome wrote: post #44

Earlier quoted context omitted.

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

Re: Lapce

#84

Post by veber-alex »

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 like phones with 120Hz displays.

You don't know you need it but once you have it it's hard to go back.

Re: Lapce

#85

Post by lchen_hn »

What’s the benefit for a neovim user? Meaning I already got LSP, treesitter, it works in a terminal. I cannot think of a reason to even try this.

Re: Lapce

#86

Post by serf »

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.

if vs code felt as responsive as emacs or vim, i'd use it. I don't really care about 'start-up time', and if I did then using emacsclient or some such with a daemon takes care of that issue entirely.

there is no convenient way for me to 'plug-in' the responsiveness of something like vim or emacs into vs code.

to be clear : responsiveness is things like opening a context menu of any kind, switching contexts, text drawing and blanking ; just things that add up to create a quick feeling piece of software. vs code/atom/whatever and other 'larger' graphic-heavy text editors feel slow.

Re: Lapce

#87

Post by myaccountonhn »

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.

Yeah I find delays make me lose my train of thought and can be frustrating. Especially once you've experienced an editor where everything is instant (kakoune).

Re: Lapce

#88

Post by xutopia »

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.

If you pair program every ms counts. In video conference another half second does a huge hit.

Re: Lapce

#89

Post by dflock »

hollerith wrote: post #69

I'd give this a try if I could find some way to configure it to wrap long lines. By "wrap long lines", I mean that I will never see a horizontal scroll bar even if there is a very long line of text in the buffer.

The nightly builds got word wrap a few weeks ago, not been released yet afaik, but will be in the next one.

Re: Lapce

#90

Post by FireBeyond »

baby wrote: post #47
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 think it's just that everybody has been looking for THE editor, and so it is natural that people would develop their own. I think what we're seeing is that VSCode is becoming THE editor (if it's not already there). At this point it's hard to compete. I think the biggest contender is IntelliJ, as many people really seem to enjoy it, but I would predict that it's going to be hard to fight against free.

I had such high hopes for Sublime Text, but then development slowed to what seemed like a glacial pace, with every upgrade requiring another licensing fee.
Post reply on HN