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.
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.