AuroraEditor is a IDE built by the community, and written in Swift for the best native performance and feel for macOS. It will support everything you could expect from an Xcode-inspired application, project planning, and your favourite built in editor tools.
@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.
@0xwdg I was referring to the original commenter’s language and demeanour. Your response was fine
Report
It's a great initiative, However, can we please change the minimum requirements for Mac Users? I am currently using mac Mojave due to my system limitation and all other IDE working fine.
@saydilse007 we've tried to make it as low as possible, since (current) the main developers use an M1 mac, we cannot test on Mojave, if you can, and are willing to help to lower it for Mojave you are more than welcome!
Thanks for your feedback, we try what we can do, cc: @nanashili
Nice design, love the native aesthetic.
I checked out the marketplace link on the homepage but didn't find a list of extensions. It looks like y'all are using VS Code extensions in the marketing screenshot. Is that right? Curious if there's a list somewhere?
Report
Maker
@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?
Report
Why should I use it instead of VS Code or JetBrains IDE?
Tell me a reason.
Can we stop reinventing the wheel?
@novaliine We do it because of the RAM Usage and File size which is bad in the 2 IDE's/Editors you gave as example.
Not all developers have a lot of RAM for their IDE.
@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
Report
This kind of behaviour is unfathomable to me.
Pawning off the CodeEdit's community project as your own.(https://github.com/CodeEditApp/C...)
And before you go ahead and showboat that "You all worked on CodeEdit": I checked, your contributions didn't amount for even 10% of the development efforts. (https://github.com/CodeEditApp/C...)
This kind of predatory practices should be unacceptable in the open-source community.
@shakedlokits we had contact about the fork, and we still have contact about the project(s) both of them.
FYI, I'm also Maintainer/Code reviewer vor CodeEdit, everything was open and clear for both communities.
About the link you sent, the #2 are 90% changes on the README.md, i was the #3, but that does not really matter.
The fact is CodeEdit did know of the fork, and we both where ok with the fork, and now (Januari 2023) we are in contact to have a (possible) merge to get back to one product and combine our effords again.
Report
Looks very neat, and I was surprised at the 2MB download size. It has the potential to be the best editor 🚀
I will try to use it as much as possible, but when you want a productive session, you don't want to be doing hit-and-try for shortcuts.
As VSCode has been mentioned in the product intro, VSCode's approach to capturing Sublime users with Key bindings got me entirely on board; something similar can be helpful to get dev onboard with KeyBinding support from other editors like VSCode, JetBrain's editors etc.
Looking forward for awesome features.
@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.
Report
@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.
Aurora Editor
Arc Boosts
Aurora Editor
Arc Boosts
Aurora Editor
Zomory
Aurora Editor
SiteAssist
Aurora Editor
SiteAssist
Aurora Editor
Aurora Editor