> In this sense it's not just the literature that needs to be reviewed, it's also feature lists (functional at least, and sometimes UI) of prior commercial and open source products.

Truly agree with you on this. Building a whole new editor today would be a hard battle for us, getting adoption even harder. We went with the route of modding VSCode for the sole purpose to ease market adoption and the foundation which VSCode provides. We don't want to stick here, but see how much we can push the editor.

I don't think the editors in the future will even look like the traditional code editors we have today, if AI can write functions, modules, whole services, would it really be code we will look at or something else (I don't want to use the word no-code here... and also because I don't want to be in that world where I am so far away from the code)

Not sure where we will end up in the future with editors, but I do believe its going to look and behave vastly difference. There will be new workflows for us to learn, and discover as we figure out how these AI agents can complement and help us out, an early sign with copilot is how my code has gone from

``` // comment if I want to {code} {mode_code} ```

to

``` // comment {copilot_generated} // comment {copilot_generated} ```

These are just early behaviour changes, but the future does look pretty interesting!