121–130 of 152 posts
Xi, the backend that it's built on, is unfortunately in maintenance mode and it seems like it has been for a while now.
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.
Earlier quoted context omitted.
Why did you opt for WASI for plugins instead of native compiled code?
Either the plugin needs to be written in a common language (JS for VSCode, Python for Sublime Text) or native (Terraform does this for custom providers) but need to support many architectures. WASI fits snuggly in between, being a common intermediate language
Earlier quoted context omitted.
> Personally, I just don't feel comfortable working with sensitive information or proto-executables in closed-source software. So, just how the biggest companies, banks, governments, etc. in the world work (using e.g. Excel, Word, Visual Studio, etc)...
Honestly "big companies, banks, governments" do sound like the usual suspects for writing programs insecurely to me (I work for one of those).
Earlier quoted context omitted.
Why did you opt for WASI for plugins instead of native compiled code?
I think native compiled code is hard for plugin distributions. You'll need to target 3 main platforms Linux/macOS/Windows. You can use github actions to do it, but it would be so easier to just compile to WASI and that's it. Also, WASI is compelling to me because of the potential of writing plugins in different programming languages.
I think this is the future really, I've been pining for this to become a thing for so long.
Earlier quoted context omitted.
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).
I still prefer crap lightning fast code to crap tediously slow code though. If the only thing people do is build a native application instead of a webapp and that speeds my stuff up by 80% then that'll make me very happy.
"just keep rebooting to solve the problem, rather than fix it"
Xi, the backend that it's built on, is unfortunately in maintenance mode and it seems like it has been for a while now.
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.
and a self-written wgpu backend hooked with druid. https://github.com/lapce/piet-wgpu
For xi, it only uses it for text manipulation.
Earlier 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.
Sufficient extensibility does not require software to be terrible.
Earlier quoted context omitted.
Webassembly makes a lot of sense for plugins. * sandboxing, so plugins don't need to be as trusted * Easy cross-platform distribution with a single build artifact * plenty fast (if written in a language like Rust/C++ and paired with a good runtime)
I wanted to clarify the cross-platform point: WASM + WASI means a single binary has near-native performance, but can run on any CPU architecture and any OS.
The runtime can be an interpreter or a (JIT) compiler. The latter can get you relatively close to native performance.
This feels like fresh air compared to tons of tools written in Javascript and running in a browser.
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.