panekj

6 ms·

1. 1.▲
   by panekj 2y ago

   or #stagex IRC channel on OFTC
2. 2.▲
   by panekj 3y ago

   We're not going to support VSCode extensions, it's not viable for us and would require to bring VSC/NodeJS runtime everywhere Lapce needs to run
3. 3.▲
   by panekj 3y ago

   People like their editor to be fast, work on more platforms, be open source, not being tied to Microsoft, etc. Plenty of reasons why someone would choose Lapce over VS Code.
4. 4.▲
   by panekj 3y ago

   Be a team of 3-4 people working in their spare time to maintain cross-platform native GUI FOSS project that people seem to like
5. 5.▲
   by panekj 3y ago

   Correction: Remote SSH works fine, we haven't reimplemented the remote file picker in new GUI toolkit but that can be workarounded by using `lapce` CLI and built-in terminal.
6. 6.▲
   by panekj 3y ago

   Lapce cannot use that much of memory, it's most likely that Rust Analyzer has allocated majority of it.
7. 7.▲
   by panekj 3y ago

   Probably because "the guy" is not a guy, but who cares, it's easier to just be salty on HN and spread lies about the project.
8. 8.▲
   by panekj 4y ago

   LSP only applies to programming languages and specific configuration files, it's useless when you edit files such as JSON/YAML/etc.
9. 9.▲
   by panekj 4y ago

   We use fork of Druid that uses OpenGL. It was wgpu before instead of OpenGL but there were issues and limitations with it.
10. 10.▲
    by panekj 4y ago

    yes, we plan to switch to Xilem when it's ready for us