You've got us over a barrel - reading between the lines:
don't extend the editor because we'll change the APIs in 5.1 coming out in ??? and no we won't standardise the frontend APIs either. So if you want to modify the editor, don't. Accept what we do.
Kinda of unfair and for me a good reason not to upgrade. After all, is 5.x going to bring fixes to the backend (e.g jsonata base64 and group catch-all but not handled or even possible function node features) or just detachable windows in the editor ... and dark theming?
Honestly I don't need detachable windows but I do need a working group catch-all nodes and working base64 encoding/decoding.
This is obviously over sensationalised and Nick didn't say any of this - this is me reading between the lines but my point is that I still see the statement as a bit unfair. If folks implement something that is useful for them, why should they wait until there is a "official" NR way to do it?
As I recently wrote, for me, a better approach would be to offer standardised editor APIs and approaches for extending the workspace with foreignobjects so that folks can get on with solving their problems.
It would also allow folks to experiment and try out new approaches which might or might not be better. One size doesn't fit all in this case.
