Why so complicated syntax for interact?

I was just playing with tutorials and was fascinated by the one called `interactive`. But there is a confusing thing. Why does one have to create method then convert it to closure?

The [code](https://github.com/twosigma/beakerx/blob/0c1619506d473b87f7b2480c49b53478170bc3cb/kernel/groovy/src/main/java/com/twosigma/beakerx/groovy/widgets/Interactive.java#L34) also does not make a lot of sense. It uses `MethodClosure` instead of generic `Closure`. It could be done to use enclosing instance for the method, but:
1. It does not seem to be the case.
2. It is much better to use Closure `rehidrate` method for this purpose.

Also it is better to use closure as a last parameter, in order not to create a separate closure.

So my question is this: is this design intentional? If not, I can try to fix it and create a pull request (if I figure out developer installation, I hate working with python ecosystem).