-j
--
You received this message because you are subscribed to the Google Groups "gonum-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gonum-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
hi yunabe,On Tue, Jan 9, 2018 at 1:55 PM, Yu Watanabe <yunabe...@gmail.com> wrote:nice!so now we have 3 kernels for Go :)gophernotes is LGPL because of the Go REPL it uses underneath (gomacro)it's also a bit cumbersome to install because of the C++ 0MQ library.I suspect yours also needs that C++ library.
but you do have very nice jupyter integration (code completion and code inspection!) and a nice license (BSD-3)ng (BSD-2) and its jupyter frontend do not have (yet!) proper code completion/inspection but it's on the road map :Pbut, IMHO, (I worked primarily on ng, so I may be biased) it has that very nice feature that it doesn't require the C++ library to be installed to work correctly (so it really is just a go-get away to play with)
see:or, directly:perhaps we could have a single jupyter package that is shared between these 3 frontends to deal with the rather complicated/under-documented jupyter messages protocol...
Thank you for the feedback, Sebastien.
but you do have very nice jupyter integration (code completion and code inspection!) and a nice license (BSD-3)ng (BSD-2) and its jupyter frontend do not have (yet!) proper code completion/inspection but it's on the road map :Pbut, IMHO, (I worked primarily on ng, so I may be biased) it has that very nice feature that it doesn't require the C++ library to be installed to work correctly (so it really is just a go-get away to play with)Good point. lgo works only on Linux and I accepted the dependency to C++ ZMQ because it relatively easy to install it with package managers.But it's nicer if we can get rid of dependencies to C++ ZMQ library completely.Do you know there are reliable ZMQ packages in pure Go?I'm not familiar with ZMQ protocol and I just chose the package from http://zeromq.org/bindings:go.
see:or, directly:perhaps we could have a single jupyter package that is shared between these 3 frontends to deal with the rather complicated/under-documented jupyter messages protocol...My jupyter package is here:It's isolated from Go execution mechanism and we can swap the backend easily.Here is a simple example kernel using this package:This package supports graceful code cancellation and kernel shutdown, code completion, inspection, etc... , which ng/gophernotes kernel does not look support now.So, it might be helpful for ng too :)
and a pure-Go simple web server that would serve very simple jupyter notebooks (a bit like nteract) so playing with jupyter notebooks could be as easy as:$> go get jupyter-serveron all Go-supported platforms, with no 3rd party C/C++ libraries to be installed.
that would be a great thing to create for Go.-s
--
You received this message because you are subscribed to a topic in the Google Groups "gonum-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gonum-dev/cXJLkRxEFWY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gonum-dev+unsubscribe@googlegroups.com.