Aurora Editor

@keinsell thanks for your feedback, we're early in development so things can change. I appreciate the feedback.

@keinsell this seems cruel. Maybe not intended but your choice of words. Anyway, while I also don’t intend switching I can see how if this IDE is good at one thing it could be my preferred IDE for that single thing. Great job with it and good luck.

@keinsell @neoighodaro Thanks, maybe i did not used the best words, we appreciate all kinds of feedback.

@0xwdg I was referring to the original commenter’s language and demeanour. Your response was fine

@rohid it's a "fork", we used to work on CodeEdit See also this for more information about that https://github.com/AuroraEditor/... I also work, and worked on CE, but we've decided to split because CE had other intentions then we had, and we could not really come together as development styles.

@0xwdg I got your intention, but I still think working on the same goal on two different projects will slow down both. VS-Code's user base is huge although it is slow, ram hungry, and built with HTML, CSS, electron, *CHROMIUM*, etc. So, it's not the speed, it's the convenience. Anyway, All the best

@laurieherault Hi, at this current moment not yet. As we continue to build AuroraEditor we will add support for LSP. It has been planned to add LSP as part of the editors main features. 🙂

@joshtoasts Hi, at the moment the extension architecture is still in development and we are still finalising approaches to how we would handle it without hitting performance issues. Regarding VS Code extension list in the screenshot it’s just a mockup of what to expect. We have this idea of trying to make some VS Code extensions work out of the box on AuroraEditor making it easier for developers to transfer their existing extensions like language support over to AE without a lot of effort and also give users a wide range of extensions by day one. Hope this answers your question?

@duc_k Yes, please see other comments or https://github.com/AuroraEditor/... for more information.

@patel_pankaj_ Thanks, my (personal) vision is to use as-less as possible external frameworks to keep the download size as low as possible, The cutom keybindings is a thing what we really want to make (in a later stage), our first priority is to get the editor (highlighting) working properly as we want.

@0xwdg I understand the priorities; I am excited to see something that focuses on performance natively. Keep up the work, and I wish I could help, but being a JS dev, at least the website is an excellent place to help; I would be happy to contribute.

@anfas_ashrf Thanks!