I personally prefer vscode but can understand why many AutoIt developers would stick with SciTE.
I think moving away from SciTE is a good thing, and no matter what replacement is chosen, i suggest making an LSP solution. this would allow vscode and many other editors to work with maybe only a editor specific extension as a wrapper for the main LSP code.
The biggest issue with vscode is platform support and maybe performance. I was "forced" to upgrade my win7 machine to win10, to continue getting updates to my vscode editor... (win7 support was removed in vscode thanks to electron specific changes )
Removing the editor from AutoIt releases will also reduce the size of downloads a little, something i personally always appreciate
I think most, if not all features found in SciTE when working with AutoIt SHOULD be possible to replicate in vscode.
If vscode is chosen, i think my extension is the least likely candidate, since i feel some core principles of my extension may be in another direction than the regular AutoIt editor experience. But i am more than happy to have a chat about it (expectations, features, core principles and such)
@argumentum I'm sorry to hear that, but i understand there my be multiple things you find off-putting, when doing the switch. If my extension is missing features, you are more than welcome to let me know (PM, Topic or GH issue), i do hope to make a good vscode experience for AutoIt developers