Author 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.
What makes you say that the development of Amp has stopped? There doesn't seem to have been a release since Feb 2020, but last push to main was 17 days ago.
Yeah, this reads like my bucket list of Rust technologies if I ever decided I'd want to implement a text editor. Definitely going to try this out. Thank you for bringing this to our attention, OP!
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 :)
VSCodium is fine, so is emacs and vim. I use them along with IntelliJ IDEA. This "code editor" looks pretty minimal in comparison to the ones I mentioned... at least as far as the screenshot goes.
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?
Ya...it's going downhill :-( I liked it as a lightweight editor. Now it's just another IDE. But instead I have to sift through thousands of half-baked 3rd party plugins to get the functions I need. Editors/IDEs should do one thing or the either well.
https://github.com/lapce/lapce/blob/master/docs/why-lapce.md strikes me as really nice -- the author tried really hard, with lots of code to show for it, to get what they wanted from vim, then neovim, then xi, and only after thoroughly understanding the tradeoffs each made embarked on creating their own editor.
Just wonder, what is the point of promoting something as "being written in Rust", if at the end it crushed the same way as "being written in C/C++/whatever".
Druid is also in a poor state at the moment (it pulls master from git) and it's not using wgpu at all. I assume it used to use a piet wgpu branch but it is not anymore.
As 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.
[+] [-] dzhou121|4 years ago|reply
The plugin system as described in the README hasn't been implemented yet.
[+] [-] gsliepen|4 years ago|reply
[+] [-] spyremeown|4 years ago|reply
I'm not a Rust person, how do you install this? Is it something like "rustc install" or something like that?
Thanks!
[+] [-] alskdj21|4 years ago|reply
[+] [-] DeathArrow|4 years ago|reply
[+] [-] thecleaner|4 years ago|reply
[+] [-] lnxg33k1|4 years ago|reply
[+] [-] syrusakbary|4 years ago|reply
[+] [-] vmchale|4 years ago|reply
[+] [-] chespinoza|4 years ago|reply
[+] [-] cassepipe|4 years ago|reply
There's also Amp (Vim inspired, written in Rust) although it looks as though development has stopped https://amp.rs/
[+] [-] depressedpanda|4 years ago|reply
[+] [-] chespinoza|4 years ago|reply
[+] [-] DeathArrow|4 years ago|reply
[+] [-] manojlds|4 years ago|reply
[+] [-] amelius|4 years ago|reply
[+] [-] buster|4 years ago|reply
[+] [-] runiq|4 years ago|reply
[+] [-] debdut|4 years ago|reply
[+] [-] throw_m239339|4 years ago|reply
[+] [-] johnisgood|4 years ago|reply
[+] [-] jokoon|4 years ago|reply
apart from code folding.
[+] [-] sharikous|4 years ago|reply
[+] [-] hdjrudni|4 years ago|reply
[+] [-] pjmlp|4 years ago|reply
[+] [-] mlinksva|4 years ago|reply
[+] [-] Ygg2|4 years ago|reply
[+] [-] forgotmyoldacc|4 years ago|reply
[+] [-] megapoliss|4 years ago|reply
Just wonder, what is the point of promoting something as "being written in Rust", if at the end it crushed the same way as "being written in C/C++/whatever".
[+] [-] karavelov|4 years ago|reply
[+] [-] geniium|4 years ago|reply
[+] [-] sharikous|4 years ago|reply
[+] [-] darkblackcorner|4 years ago|reply
[deleted]
[+] [-] stormbrew|4 years ago|reply
Well... This has me intrigued. This is basically the only thing that keeps me on vscode.
[+] [-] chrysoprace|4 years ago|reply
[+] [-] panzerklein|4 years ago|reply
[+] [-] rapsey|4 years ago|reply
[+] [-] zokier|4 years ago|reply
[+] [-] Dave3of5|4 years ago|reply
I literally couldn't open any folder.
Also on windows by default it leaves a separate command window hanging which seems odd. Why isn't this logging done within the app terminal itself.
[+] [-] revskill|4 years ago|reply
As soon as memory management issue is solved, i could see all future software will eventually be written in Rust (or similar language)
[+] [-] yisonPylkita|4 years ago|reply
Will this editor allow me to run it with rust-analyzer code completion?
[+] [-] slowtec|4 years ago|reply
[+] [-] schrute|4 years ago|reply
[+] [-] jokoon|4 years ago|reply
[+] [-] trbn|4 years ago|reply
[+] [-] geniium|4 years ago|reply
[+] [-] cortexio|4 years ago|reply
[deleted]