Live data from Hacker News

Lapce – Fast and Powerful Code Editor written in Rust

github.com

91–100 of 152 posts

Re: Lapce – Fast and Powerful Code Editor written in Rust

#91
post #61

Earlier quoted context omitted.

Only problem with sublime is the exorbitant price. It's just too much!

$100 for what one (three?) years? Seriously? Forget the exorbitant tech salaries, so many other industries charge way more for essential equipment. That's chaper than a single snap-on wrench out of the hundreds that an automative shop has to buy. It's two months of adobe bundle that most graphic designers subscribe to. I think the perspective here is important.

Not everyone on HN is on Silicon Valley wages. Or even work in international tech hubs like SV or London.

For some in tech, $100 is a hell of a lot of money.

Re: Lapce – Fast and Powerful Code Editor written in Rust

#92
post #34

Earlier quoted context omitted.

Seems like you have been picking the wrong tool for the job.

Seems like Atom and VSCode picked the wrong tool for the job.

They just chose other-people-choosing-the-wrong-tool-for-the-job as a business model.

Re: Lapce – Fast and Powerful Code Editor written in Rust

#93
post #86
post #82

Earlier quoted context omitted.

Apologies for lack of my lack of knowledge in this area, but... Why don't plugins "need to be as trusted"? Obviously bad-actor plugins would be less effective and capable of inflicting any sort of attack on your development OS, but surely the development environment is the perfect vector for attacking the runtime environments that run your artifacts get deployed into? Not to mention the potential for secrets-harvesti…

The clue is in the first part of the GPs sentence which you latched onto: “sandboxing”. The code is running inside a virtual machine rather than natively on the host.

No, I got that. I understand how the host is protected, but didn't understand how everything inside the "VM" was protected... @galgalesh answers that above.

Re: Lapce – Fast and Powerful Code Editor written in Rust

#94
post #82

Earlier quoted context omitted.

Apologies for lack of my lack of knowledge in this area, but... Why don't plugins "need to be as trusted"? Obviously bad-actor plugins would be less effective and capable of inflicting any sort of attack on your development OS, but surely the development environment is the perfect vector for attacking the runtime environments that run your artifacts get deployed into? Not to mention the potential for secrets-harvesti…

It's all about reduction of surface and giving plugins access to the least amount of info. You expect a linter to only have (read) access to the code it lints. It shouldn't be able to modify files, it shouldn't have network access etc. WASI has a pluggable capability-based security system. Some advanced linters might want network access but you can show this to the user, so they can make an informed decision about wh…

Thanks for taking the time to explain. I guess I was pretty ignorant in thinking that a plugin basically has all access to the dev-env it's written in.

I hadn't really heard of WASI, let alone understand it, but it totally makes sense why you would want to leverage this approach, along with any IDE-specific plugin interfaces/integrations.

Re: Lapce – Fast and Powerful Code Editor written in Rust

#95
post #88

Earlier quoted context omitted.

Rust memory management model ?

And what issue related to Rust's memory management is to be resolved?

The fact that it makes you think about it all the time, rather than using a garbage collector?

Re: Lapce – Fast and Powerful Code Editor written in Rust

#96

Earlier quoted context omitted.

The bloating cycle should merit its own xkcd comic I guess. VS Code was specifically successful because it was perceived as much less bloated then IDEs, yet much more user friendly than most editors. Now we hear complaints that it is bloated. What will be next?

All "lightweight", "fast" shiny new things are so because they have plenty of missing features. But anyway is it a widespread opinion that VSCode is bloated? Because for me at least it feels fast, especially considering all its features.

VSCode is bloated [0]. I ran a fresh install on a 1st gen i5, it couldn't process keyboard input on an empty file above 4 char per sec. Levels of lag my brain couldn't remember (and I'm a hp48g lover.. not known for zero latency).

[0] That was last year, so maybe it was a buggy release (doubt it) or maybe they made big improvements since (possible)

Re: Lapce – Fast and Powerful Code Editor written in Rust

#97
post #4

VS Code is so bloated af Waiting for this to be stable! Would love to contribute! Any next features doc, so I can pick a topic and submit some PRs. Awesome work :)

Other than having to put up with Electron, nope it isn't bloated, in fact it is still missing lots of nice IDE like features.

Re: Lapce – Fast and Powerful Code Editor written in Rust

#98

Earlier quoted context omitted.

Hi, thanks for writing some free software! I'm not a Rust person, how do you install this? Is it something like "rustc install" or something like that? Thanks!

There is cargo install, yes :) https://doc.rust-lang.org/cargo/commands/cargo-install.html

Thank you!

Re: Lapce – Fast and Powerful Code Editor written in Rust

#99
post #21
post #4

VS Code is so bloated af Waiting for this to be stable! Would love to contribute! Any next features doc, so I can pick a topic and submit some PRs. Awesome work :)

sublime text is the best editor currently, in my view. apart from code folding.

agree :) daily driver. nova.app pretty great stuff too

Re: Lapce – Fast and Powerful Code Editor written in Rust

#100
post #84
post #77

Earlier quoted context omitted.

Both work fairly well, are popular and performance is satisfactory (unless you try to paste an 80k line JSON file into either of them, that doesn't work). Considering their success, wide availability and vibrant ecosystems, I'd say they picked the right tool for the job.

Not sure if eating memory like complex 3d modeling software (with model in it) for something what is at the end of the day basically just text editing is the right tool for the job. Energy with excluded externalities is cheap. So modern personal computers can bear anything. But should they?

It's a tradeoff. Because they are written using web technologies it means that they are very extensible.

If you are a professional then just buy more RAM.

Post reply on HN