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

121–130 of 229 posts

Re: Lapce

#121

Post by pandemic_region »

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.

Is anybody else finding Intellij more and more getting in the way in an obtrusive manner? Code completion suggestions are getting worse, formatting ability is basically none existent if your statement is missing a comma or a lambda, it keeps reindexing my local maven repo, code completions are slow to appear... I was a huge fan of their products but now I'm getting more and more annoyed. Maybe I'm getting old?

Several times I have been on the brink of trying out spacevim for java development , out of pure frustration but the amount of config and tweaking needed scares me. I don't need much, lightning fast auto complete, auto import and Google code formatter integration. One of these weekends I'll bite the bullet I think and set it all up.

Re: Lapce

#122

Post by Cort3z »

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…

This assumed by the way that the speed goes to infinity, which is untrue. But the result would most likely be indistinguishable from instantaneous from the point of view of the developer.

Re: Lapce

#123

Post by akdjidensb »

arghwhat wrote: post #99
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…

This is the case for most orgs with corp IT. Their KPIs are around security, which often manifests itself as a game of "how many security products can one run in parallel". Crapware like Cisco Secure Endpoint (not to mention Umbrella), Thycotic, Netskope, and whatever else is the current cool way for a corp to MITM itself and introduce kernel vulnerabilities. This in turn puts departments at odds, as their argument f…

We should be clear that it isn't ALL of corporate IT that is on board with this, or probably even the majority. Its the windows sysadmins that have to deal with non-technical end users, and are constantly being hounded about trivial shit like people clicking on phishing emails and that sort of thing. In fairness to the windows people, you probably wouldn't believe just how awful the majority of workers are with computers. So it's understandable why windows sysadmins become hyper paranoid and irrational in a lot of cases. The low pay doesn't help either. Windows sysadmin is usually a lower tier job within IT and is the most likely to suffer cost cutting and be forced to "outsource" security work to a pile of rotten security software. It's also entry level, and so sometimes they are only marginally better with computers than their end users.

Ideally, most programmers should be in IT or have some kind of alignment with IT and able to give some pushback about this during CAB for instance, and/or get some exceptions but that is increasingly difficult the more 'agile' an organization becomes and the more it seeks to silo infrastructure people from application people. A good IT department imo is one that doesn't do this and retains a more traditional culture where programmers are part of IT and able to actually influence the technical direction of the company, not just be treated like a product factory for business units.

Just from personal experience working as a programmer on the infrastructure side...complaining about windows sysadmins was the favorite past time of probably the majority of higher tier IT employees. It makes our jobs incredibly difficult for the same reason it makes application developers jobs difficult.

Re: Lapce

#124

Post by pcthrowaway »

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.

> Is the world really full of developers going crazy with frustration because they’re waiting on vs code to do something?

If programming in Rust on a medium-to-large project, you might be waiting minutes for your editor to finish checks to highlight compilation errors every time you save. That was me on a Rust project last year when I was trying to program on a 2019 macbook air with 16GB of RAM and 1.1 GHZ quad-core intel processor. Typical wait times to check what I'd written would be 30 seconds to just over a minute. It was excruciating.

I finally demanded the employer set me up with a cloud VM that I could use when working with that codebase, as the network lag with VS code opening the project remotely was so much more tolerable

Re: Lapce

#125

Post by meet_squad »

Who knew that the existential crisis of the modern developer would be choosing between milliseconds of latency and the perfect shade of syntax highlighting :)

Re: Lapce

#126

Post by arghwhat »

Cort3z wrote: post #117
arghwhat wrote: post #99

Earlier quoted context omitted.

This is the case for most orgs with corp IT. Their KPIs are around security, which often manifests itself as a game of "how many security products can one run in parallel". Crapware like Cisco Secure Endpoint (not to mention Umbrella), Thycotic, Netskope, and whatever else is the current cool way for a corp to MITM itself and introduce kernel vulnerabilities. This in turn puts departments at odds, as their argument f…

I don’t understand. How does speed implies inverse security, even with corporate blinders on? Let’s say the add all the bloatware in the world, how would a slower developmental speed compromise the security? That their ability to push code goes up and their potential for bugs increase?

Security solutions impact speed, rendering reasonable and performant machines borderline useless. There is no implication that working fast is bad for security.

Re: Lapce

#127

Post by SubiculumCode »

warthog wrote: post #97

The reason I am sticking with cursor.so is the AI. It is convenient to be able to a) let AI read whole files b) feed in direct documentation of a certain package to have proper context. Might not be worth to expert coders out here but definitely saves a lot of time for me debugging or onboarding into a new framework Wish Lapce had that. Also Zed does not have the quite depth for AI compared to Cursor

does cursor.so allow use of local llms?

Re: Lapce

#128

Post by koonsolo »

tuan wrote: post #46
twp wrote: post #18

Earlier quoted context omitted.

Use https://github.com/vscode-neovim/vscode-neovim instead.

Since v1.0+ of this extension I have been constantly having issues with neovim's and VSCode's buffers got out of sync. I cannot reliably reproduce the issues however. There are a few similar reports, e.g. https://github.com/vscode-neovim/vscode-neovim/issues/1624 . I've switched to other VIM extension (VSCodeVim) which I found more reliable, albeit less powerful.

That's funny, because I switched from VSCodeVim to NeoVim for a similar reason.

I guess both have issues. But still, the power of VSCode with vim keybindings is still my best setup.

Re: Lapce

#129

Post by Daeraxa »

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'm on the team working on Pulsar, the community fork of Atom. You have no idea how much we hear "Atom is slow", "are you making it fast?" etc. I have honestly yet to work out exactly what is meant by it. Startup times, sure, you are never going to get Pulsar/Atom or VSCode to launch as fast as a terminal editor or a super lightweight native one but that isn't how I personally use that kind of editor - once it is open it stays open for a long time. Keystrokes, context menus, highlighting performance, I honestly don't see where this perceived slowness is.

I'm not saying it isn't valid criticism but I guess the way I work with an editor just isn't the same as others who experience this.

Re: Lapce

#130

Post by danielheath »

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.

A few years back, someone built a webpage that had various text fields with different typing latencies.

A bunch of my friends tried it, and it was really interesting to see that many of them were not bothered in the slightest by even quite high latency numbers.

Personally, I was mildly bothered by the "single frame of latency" example and _intensely_ bothered by all the higher numbers. It just felt really yuck to use; I would hate to be doing that all day.

I can't tell you what exactly it is, but yes: the world contains many developers going crazy with frustration - not because of a 30 second wait, but because of a 30ms render delay.

Post reply on HN