How the new GH1/Rhino workflows will translate to GH2?

[barden00]

Some posts from one topic made me ask this question, but I didn’t want to make an offtopic.

Nothing times one equals one, inconvenient behavior of mathematical operators

I think if GH2 development would have been a bit faster, we could already retire GH1. These bugs are known for more than 10 years, and personally I don’t see a benefit in solving it anymore. Currently there are similar topics active, but I think fixing an almost deprecated software is pointless. It would affect many components. Just ensure not to work with empty strings or branches. This is bad in many ways anyways. The result is obviously wrong, but you may conclude the wrong problem. You im…

For some years Grasshopper development seemed to be stagnant and major changes were up to the 3-rd party plugin developers, some time ago GH2 entered the Alpha stage and then all of a sudden Grasshopper 1 received a new spark of life because of the whole Rhino Tab. Although I’m very happy to see the tighter integration between Rhino and Grasshopper, and I like how components are laid out, I wonder how long they will be used and how they will translate to GH2.
It almost seems like patching some shortcomings in GH1 that couldn’t be tolerated much longer and solving these issues buys some time for the GH2 development. Are these late-stage Grasshopper 1 additions a test to see how to structure certain things in GH2 or it’s known that GH2 will handle Rhino/GH object modifications differently?

For users, moving from GH1 to GH2 will be quite a big task, but even bigger if recent GH1 updates (and thus workflows) go in a different direction in comparison to how things will work in the GH2. Personally, I think I can afford completely different workflows if this would mean better foundations laid for the GH2 development but that’s now, I don’t know how things will look for me in a couple of years.

I don’t know if I’m on a team: let’s squeeze as much as we can from GH1 or, let’s move to GH2 as soon as possible.

@AndyPayne

GH2 is a complete re-write from the ground up and its a little different. It does have ways to set object attributes but it does not use these components to do so. It has it’s own methods that David wrote to do that which fits it’s new system.

[stevebaer]

Grasshopper 1 shipped with Rhino for the first time in Rhino 6. Rhino 7 saw the addition of the grasshopper player, placeholder components, clash detection, and hops. Rhino 8 now has the new “rhino” tab and there are other new components slated for Rhino 9 that we need a bit more time to develop.

I would view GH2 as a completely separate product from GH1. We will continue to ship GH1 when GH2 is ready and will work on ways to use GH1 data in GH2.