hydrogen VS rust-zmq

Hydrogen got an update to fix this issue, but it was never published on Pulsar's backend. You can install it with pulsar -p https://github.com/nteract/hydrogen.git -t v2.16.5

Folks who know Pulsar and Zed internals: which one of them is more likely to gain support for Atom packages? I find Hydrogen[1] invaluable as a data science scratchpad since it supports python/r/julia/etc under a common interface via jupyter, and have been unable to construct a comparable workflow in vscode or any other editor [using scripts as opposed to notebooks, which i find far too bloated].

[1]: https://github.com/nteract/hydrogen

Finally, newer Pulsar versions (from the master branch on the CI) allow you to install ppm and pulsar from the command-line. We also fixed some of the issues on installing a package directly from github - for example, you can run "pulsar -p https://github.com/nteract/hydrogen.git -t v2.16.5" to install hydrogen on tag v2.16.5 now (tested on Linux and Silicon mac). Package publication is an ongoing process - we fixed lots of issues of the first version, and now it's working for some people, but we are still aware that we have some bugs too... it's hard because we need to "reverse engineer" the old API :(

But with Hydrogen you could do that in a regular Python script without needing to create a notebook or think in terms of cells. There's an example of this in the Hydrogen readme: https://github.com/nteract/hydrogen#hydrogen-

I personally found Atom + Hydrogen [0] to be the most productive interactive Python environment I've ever used. I really want to see VSCode adopt some way to run a Jupyter kernel for a Python file (with a notebook UI) and have rich results in line with the code (i.e. not a terminal output off to the right side of the screen).

[0] https://github.com/nteract/hydrogen

It depends how useful you think the patch is, and maybe also how likely you think it will get merged.

In most cases I simply keep my fork as a PR and use the package either by vendoring or directly from the repo. If anyone else encounters the same bug, they will see my PR referencing the issue, they can do the same.

If many people are encountering the bug and using the package, and/or if the project seems dead, then it's a good idea to publish. You can do username prefix or you can just add "2" at the end. I've seen this for other repos, This is what https://crates.io/crates/zmq2 did while https://crates.io/crates/zmq was inactive, though it seems like the latter's maintainer became active and merged what the former's maintainer had done.

I have been using https://crates.io/crates/zmq since 2015 (shortly after rust 1.0 was announced) in production with pub-sub, request-reply and router without any issue. Processes about 5k msg/seconds (mid-freq market data).

I learned a lot about sockets with the library ZeroMQ, although at that time I was using the Python version. This library also has a Rust library, although it doesn't look like the amazing guide about sockets allows you to select Rust as of yet. Still I would recommend going through this guide, as it is not just teaching you how to use a library, but also teaches you about sockets at a theoretical level. It's entertaining to read as well.

I think maybe the ZeroMQ rust crate as a case study is something that is non-trivial: https://github.com/erickt/rust-zmq