3 ms·

I gave it a fair try Cons: - spawning nodejs whenever you edit JSON files seems overkill, i'd prefer they use something native and more lightweight, or a way

I gave it a fair try Cons: - spawning nodejs whenever you edit JSON files seems overkill, i'd prefer they use something native and more lightweight, or a way to completely disable it - text still looks a bit blurry on low DPI screens - doesn't support LSP properly, completion items are missing some data - Rust for plugins.. this is painful, compare it to Sublime Text's python API, it's night and day.. Pros: - Fast and responsive - UI is simple yet effective - drag&drop layouting, something i wish Sublime Text had.. - built-in terminal - built-in Debugger (not yet ready) Few more months of developments, and i'll certainly switch from Sublime Text, i'll be a little sad because i wrote plenty of plugins for it I however worry about their business model, i have 0 interests in their AI/collaboration stuff, i'll probably maintain a fork to get rid of all that crap, they should setup something as a back up plan, a small paid license, just for support, i'll be happy to buy one

nilslice 2y ago
> - Rust for plugins.. this is painful, compare it to Sublime Text's python API, it's night and day.. Yes, this is unfortunate as they've unsuitably chosen the barely usable & unstable "component model" for their Wasm plugin layer. It's really only half-decent in Rust (to write the code & compile to CM non-standard version of wasm binary. it's also only truthfully usable to call components _from_ rust too.) I think they are banking on the eventual support for cross-language async - which likely could never come, or could take longer than the company stays solvent!
kelnos 2y ago
> I however worry about their business model For me, this is a showstopper. I don't want to use a text editor that even has a business model.
- WhereIsTheTruth 2y ago
  It doesn't really matter, it's open source with a growing community already, so it can only keep going if the company dies

nilslice 2y ago

> - Rust for plugins.. this is painful, compare it to Sublime Text's python API, it's night and day.. Yes, this is unfortunate as they've unsuitably chosen the barely usable & unstable "component model" for their Wasm plugin layer. It's really only half-decent in Rust (to write the code & compile to CM non-standard version of wasm binary. it's also only truthfully usable to call components _from_ rust too.) I think they are banking on the eventual support for cross-language async - which likely could never come, or could take longer than the company stays solvent!

kelnos 2y ago

> I however worry about their business model For me, this is a showstopper. I don't want to use a text editor that even has a business model.

WhereIsTheTruth 2y ago
It doesn't really matter, it's open source with a growing community already, so it can only keep going if the company dies