4 ms·
For information, it's not the only Go kernel for Jupyter. There is also https://github.com/gopherdata/gophernotes https://github.com/gopherdata/gophernotes whi
by cosmos72 8y ago
For information, it's not the only Go kernel for Jupyter.
There is also https://github.com/gopherdata/gophernotes https://github.com/gopherdata/gophernotes which uses a different approach: contains a portable Go interpreter, instead of invoking the Go compiler for each Jupyter cell as lgo does (lgo is currently linux only)
- fredley 8y agoA comparison with gophernotes is included in the article. From the things they've chosen to compare, it looks like a step up!
- cosmos72 8y agoYes, from the things they've chosen to compare. I am gomacro author's (gophernotes uses gomacro as Go interpreter) and I find the comparison needs an update. Among other things, gomacro now supports interfaces - although gophernotes still has to catch up. It's also partially incorrect: gophernotes and gomacro are type safe I guess I will have to open an issue... Also, IMHO the comparison criteria are chosen based on what lgo author considers important - not necessarily what's important for someone else. Some quick examples that are important for me: portability on non-Linux systems, redefining a variable or function (lgo can only shadow them), redefining a method, allowing unused local variables... I have great respect for what yunabe accomplished with lgo, including the deep integration with Jupyter (displaying HTML, Javascript, images...), code completion, and many other features, but I think his comparison with gophernotes needs to be updated.