While I don’t have much experience with C# development in the new editor yet, I too find it unsuitable for IronPython development and largely inferior to GHPython. By order of priority of what is stopping me from using the new editor would be:
-
Performance: The IronPython script editor is roughly 25-33% slower than GHPython in the tests I’ve done (including real-life project components). And the CPython editor is MUCH slower than GHPython, specifically when implementing RhinoCommon. While the latter is understandable, the former to me is a deal-breaker (as is the situation with the console/terminal). If you can trim the fat, or let the user turn off features that bog down performance (maybe the debugger could be partially responsible), that would would great. I’d expect a new editor to be more performant, not less.
-
Code legibility: I’m having a harder time reading the text and syntax highlighting than I am in GHPython. I know @Alain is already working in these issues, so hopefully we’ll see some improvements there soon.
-
Design/structure: This was the original intention of this topic. And while there have been great improvements, there are still plenty of remaining issues, which overall make the editor feel quite janky/verbose, and not very balanced, minimal or “zen-like”, if that makes any sense
