I will be releasing hackerman.ai text editor later this year (or ASAP), also somewhat niche product with support for creating/editing lexers (eg for your own languages), able to customize almost everything, set key bindings to use self-defined functions (scripting), and ofc integrated AI features, which can also be customized and added as commands etc.
> 1. Perpetual fallback licenses on SaaS products are (unfortunately) not terribly common - so if it's not explicitly stated then you can bet your bottom dollar that it's highly unlikely.
I also think perpetual fallback licenses are great and will def use this for hackerman.ai text editor (when released later this year).
I also wish devs would start offer one time payments again (especially for downloadable software).
Great question - we're doing a VS Code clone to have access to features like language servers, debugging, extensions, etc - these are really annoying to build from scratch. We also think it's nice for users to just be able to do a one-click switch from VS Code to Void, and hard to win over Cursor users without it. I'm curious about how you're building your editor - are you building everything from scratch?
I've also made an editor/IDE from scratch and it is painful, for example implementing text rendering and Unicode support (emojis) is a PITA and takes a lot of optimization if you want below 1ms screen of text rendering. I however took the approach "every feature is a plugin", so when adding features I first made the core API able to handle the feature then implemented the feature as a plugin. So a few years into development I rarely need to touch the core API and can implement new features with a high level easy to use API in just days.
About adaption, it's very hard to make people switch over to a new editor, so by forking an popular editor you shaved off years of development, and it will be easier for users to switch over. But probably at the cost of implementing new features takes longer and large refactors more difficult.
