71–80 of 152 posts
Earlier 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"
Earlier 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?
The 0.0.1 release crashes on MacOS 12.0.1, would be nice to try it out when its more stable.
yep, it crashes on Archlinux as well 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".
Why always lightning, why not sound-speed ? As soon as memory management issue is solved, i could see all future software will eventually be written in Rust (or similar language)
What does this refer to?
Why always lightning, why not sound-speed ? As soon as memory management issue is solved, i could see all future software will eventually be written in Rust (or similar language)
> As soon as memory management issue is solved [...] What does this refer to?
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.
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 :)
VS Code isn't bloated if you never install any extension. You can't hold Microsoft responsible for third party bloat.
* LSP uses JSON. Even worse, VSCode uses UTF-16 internally (because Javascript does, more or less). But JSON uses UTF-8. So for correct operation VSCode converts the UTF-16 to UTF-8, and then your language server has to convert it back to UTF-16 to figure out the row/col positions (which are in UTF-16 units).
* LSP has an "easy mode" where the entire document is sent to the language server on every keypress!
* Some functions like `provideDocumentLinks()` operate on the entire document, so on every keypress (maybe it batches them I don't know), all linkifier extensions will run a load of regexes over the whole document.
There's definitely scope for a text editor with an extension API that encourages speed.
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.
Lsp support as well ? You have got to be kidding me. How did you add these feature so quickly ?
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.
I'm not a Rust person, how do you install this? Is it something like "rustc install" or something like that?
Thanks!