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

51–60 of 229 posts

Re: Lapce

#51

Post by stracer »

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.

Some corporate employees use a notebook loaded with extremely invasive and performance-degrading security and spying software that can't be uninstalled. When your available cpu and disk time is 10% of what the hardware can do, you need as efficient editor as you can get.

Re: Lapce

#52

Post by anton-107 »

behnamoh wrote: post #27

No thanks, I don't want fake open-source apps anymore. Some fake open-source software that are actually in it for the money: - Langchain (and most "open-source" LLM software) - Zed

Warp terminal comes to mind as well. But I believe they are just plain closed-source. What makes these projects fake open-source?

Re: Lapce

#53

Post by jlengrand »

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.

Not that I disagree, but IntelliJ has a free version, and they're building up Fleet as an attempt to compete. Future will tell.

Re: Lapce

#54

Post by tomlin »

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.

They are saying it's made in rust, so they are probably trying to counter concerns.

Re: Lapce

#55

Post by Fervicus »

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.

No opinions on the editor itself yet, but just wanted to chime in here to say that I didn't have any such issues on Windows 10.

Re: Lapce

#56

Post by jonathankoren »

jahsome wrote: post #44
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.

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

What are you waiting two minutes to do?

Re: Lapce

#57

Post by Keyframe »

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

Re: Lapce

#58

Post by stracer »

sph wrote: post #42

Making a fast editor is such a common hobby, everybody seems to be working on one these days apparently, yet memory safety and speed has never been a real problem in editors. It would be much more impressive to explore a novel approach for editors more extensible than Emacs, or with a more innovative editing model than vim's. If we are reinventing the wheel, why not at least try to make a better wheel that's never be…

Editors don't get made in Rust because people want better memory safety in an editor. They're made in Rust because people like Rust, and the Rust trademark makes anything associated more cool, no other language has reached such a godlike marketing status.

Re: Lapce

#59

Post by formerly_proven »

jonathankoren wrote: post #56
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

What are you waiting two minutes to do?

With corporate Windows laptops the real question is "what aren't you waiting two minutes to do?"

Re: Lapce

#60

Post by spullara »

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.
Post reply on HN