Script component vs GHPython and C# components

[Chris37 (Chris)]

Lately i’ve been converting scripts to either python and C# to learn these languages and have been using the legacy GHPython and C# components for this. I’ve seen the new Script component, but never gave it a try … just the habit of just typing “pyt…” in the search box i guess. When I open file shared on the forum, some people also still use the legacy components.

“This Script component is designed to work with any of the supported languages. While being completely new and internally different from the legacy GHPython and C# components, it tries to replicate the same behaviors as those legacy components and stay familiar as much as possible.”

Long story short > What are the benefit of using one above the other?

• I assume Script component is designed with the latest features and optimizations, potentially offering better performance and more capabilities than the older, language-specific components, including setting breakpoints, inspecting variables during runtime, and step-by-step execution of scripts.
• For C# and Python scripts respectively, directly specify and manage external packages
• Autocomplete, syntax highlighting seems the same
• Dynamic management of inputs and outputs seems the same, or am i missing something
• portability to gh v2??

[AndersDeleuran]

@Chris37

… potentially offering better performance …

Specifically comparing to GHPython, this is not exactly the case:

Rhino 8 Regression: CPython/IronPython RhinoCommon Performance Is Worse

Hi McNeel, I’ve noticed that CPython scripts will perform substantially worse when implementing RhinoCommon than IronPython (presumably because of Python.NET) . And that the new script editor with IronPython performs slightly worse than GHPython (presumably because of the new editor, since they’re both running 2.7.12 .NETCoreApp). Here’s a quick demonstration making a whole bunch of Point3d within for loops: [2024-02-05 14_54_27-Grasshopper - 230801_ScriptsMillionPoints_00_] 230801_ScriptsMi…

At least when implementing .NET and RhinoCommon. The new CPython script editor appears to be more performant than GHPython when the code is pure Python though. But then there is also this (for me) deal breaker:

Rhino 8 Grasshopper Script Editor - Design Feedback

Hi @eirannejad, it’s really great to see all the new features and edits in the last beta update! I’ll report back with feedback when I get a chance, but for now I found a higher priority functional issue. Basically, the same one I reported back here when GHPython was updated for Rhino 6, where printing to the terminal is much slower than in GHPython and eventually will become unresponsive: Here’s a quick side-by-side, where GHPython allows one to print a million integers and the new script ed…

There are a lot of regression reports in that topic, in general, that might interest you.

[Chris37 (Chris)]

wow, you’ve got some history on this topic , haha Good reads and great to see your involvement to improve those gh tools, from both performance and UI.