Xi, the backend that it's built on, is unfortunately in maintenance mode and it seems like it has been for a while now.
According to readme it's not a Xi frontend, but rather it uses same algorithms for string manipulations
Lapce – Fast and Powerful Code Editor written in Rust
101–110 of 152 posts
Re: Lapce – Fast and Powerful Code Editor written in Rust
#102Earlier 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…
> 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.
That sounds absolutely amazing. Are there any desktop apps delivered like this yet? Any operating systems or some sort of runtimes (browsers?) that support them?
I want to install apps on my desktop without worrying about it too much. Sadly currently restricted to PWAs.
Re: Lapce – Fast and Powerful Code Editor written in Rust
#103VS 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.
well the bottleneck is electron. The startup times have consistently increased since I first started using it, now it uses north of 1gig RAM for a decent size project, too much for a text editor :(
Don't get started on the popups though!
And I don't use any extension
Re: Lapce – Fast and Powerful Code Editor written in Rust
#104Earlier quoted context omitted.
Care to elaborate on what's wrong with Druid?
Nothing, I edited the message because in the first version of the comment I asked which UI framework they were using, then I saw that info contained in the README and said "ah okay it's using Druid" as in "I saw that" not in "Ah crap you're using Druid"
Ah, my bad — got thrown off by the original wording
Re: Lapce – Fast and Powerful Code Editor written in Rust
#105> Built in remote development support (inspired by VSCode Remote Development) Well... This has me intrigued. This is basically the only thing that keeps me on vscode.
Sadly can't get it to run on linux :( Lot of garbage about loading font config from /etc/fonts/conf.d/... and then: memory allocation of 18446744073709551615 bytes failed Aborted (core dumped)
There is a bug and I found a possible culprit (worked on Win 10):
https://github.com/lapce/lapce/issues/9#issuecomment-9935004...
Re: Lapce – Fast and Powerful Code Editor written in Rust
#106Author here. I didn't expect this will go on Hacker News. Although the editor has been my daily drive for almost one year now, it's really rough on the edges. The plugin system as described in the README hasn't been implemented yet.
This looks very nice. However, the description mentions "lightning fast" and "powerful". Unfortunately, those things don't mean anything without further clarification. If you really want to show your editor is faster than other commonly used editors, consider posting a benchmark of cases where speed matters (like loading a large file, inserting in the middle of a large file, search/replace, latency of pressing a key and having the screen updated, and so on). It is harder to quantify "power" though.
Re: Lapce – Fast and Powerful Code Editor written in Rust
#107Earlier quoted context omitted.
Sadly can't get it to run on linux :( Lot of garbage about loading font config from /etc/fonts/conf.d/... and then: memory allocation of 18446744073709551615 bytes failed Aborted (core dumped)
Trying to allocate memory the size of an underflowed uint64 does not seem safe. Is this possible in safe Rust code? Is there a Rust build flag that would catch this behavior?
It's not underflowing int. Actually it's a divide by 0 bug, because font handling returns 0 sometimes. See my sibling comment.
Re: Lapce – Fast and Powerful Code Editor written in Rust
#108As always, if something is advertised as "fast" (or especially lightning-fast), it would be really nice to see some performance characterizations to explain in what way it is fast. Otherwise it feels so very meaningless label that is so often slapped on things on very weak grounds. And just because the building blocks might individually be said to be fast, it doesn't automatically mean that the conglomerate of them is still fast; performance is a fickle thing.
Re: Lapce – Fast and Powerful Code Editor written in Rust
#109Author here. I didn't expect this will go on Hacker News. Although the editor has been my daily drive for almost one year now, it's really rough on the edges. The plugin system as described in the README hasn't been implemented yet.
This looks very nice. However, the description mentions "lightning fast" and "powerful". Unfortunately, those things don't mean anything without further clarification. If you really want to show your editor is faster than other commonly used editors, consider posting a benchmark of cases where speed matters (like loading a large file, inserting in the middle of a large file, search/replace, latency of pressing a key…
Standard rust marketing, it's a bit tedious tbh, and I don't think anyone who is honest is surprised any more. Everything is "lightning fast" by default just because it compiles to native. I thought we were past that. Never mind that you can write crap code in any language (not making any comment about the editor's author here).
Re: Lapce – Fast and Powerful Code Editor written in Rust
#110Earlier quoted context omitted.
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.
>If you are a professional then just buy more RAM.
That cockiness sounds familiar, and it was the reason why people moved from Java based IDE's to vscode/atom/sublime.