In what way you where involved in the choice for Eclipse I don't know.

But in my (not so) HO, that was a very bad choice.  Eclipse is a jack-of-all-trades that serves no-one.

If ISC would have made a choice for Git as a SC a long time ago (conflicting probably with long-time parties such as GJS) , Studio could have been vialble. Only on Windows. But I think the developer wars on Win/Lin/Mac are long time settled on VM's and containers.

Building on Studio further, opening up API's (Atelier), supporting Language Server Protocol , ISC could have been less dependent on others.

In the first place I'll have to say that I never understood the choice for Eclipse as the base for an ISC editor/ide.

So I'm not that sad, for this decision.

But what will we get then ?

I think ISC is big enough to have their own IDE (do we need an IDE ?)

It could be home-grown (a little bit too late) or Atom based, which is a editor not an IDE.

If  ISC abandons BPL (which I think is really a very bad thing), it would make a transition much easier.

They're not orthogonal.

Consider a Person class:

Person
    Method AmISmarterThenTheRest() {
        Set AvgIQ=..GetIQ(..HairColor)
    }
    
    ClassMethod GetIQ(HairColor) [Private] {
      ; determine the average IQ by HairColor
    }

The GetIQ method is obviously a class method, but you might not want to expose it to the outside world.

There's where one needs (wants) a private class method