ecode VS lapce-cpp-clangd

I'm working on an code editor with a similar philosophy (or at least I'm trying to achieve similar goals) but it's completely open-source (MIT licence). It's called ecode and can be found here: https://github.com/SpartanJ/ecode . It's also GPU accelerated, native code (no electron), has LSP integration and has many similar feature set.

I'm looking for collaborators, if someone is interested please message me.

That's a good list, Lapce checks many of those. I asked previously because I'm also working on a code editor (ecode) and I'm really interested in knowing what devs consider essential from a code editor. Also, my editor is in the early stages but check many of those in the list (and some are currently in development), so I'm happy that I'm moving in the correct direction.

Having said that, I'm working on an alternative GPU accelerated and retained-mode GUI called eepp (https://github.com/SpartanJ/eepp/) while I work on a new code editor similar to Zed called ecode (https://github.com/SpartanJ/ecode). The framework still needs a lot of work but presents some ideas that might be interesting to some. Retained-mode GUIs are a complex beast and it's hard to achieve simplicity (I think immediate-mode GUIs can't be beaten in that regard, but they have their own downsides). So I invite anyone interested in GPU accelerated GUIs to take a look at my projects (online demos are available), I'm looking for collaborators! (sadly C++ isn't very appealing these days, but my code-base is huge and I can't write everything from scratch in a new fancy and cool language).

For language support. You need to install plugins. In this case, you need to install the clangd plugin https://github.com/lapce-community/lapce-cpp-clangd However, it might still not work for you because of your weird file extension policy. AFAIK, the language detection is hardcoded although this can be fixed I think quite easily I think.