hydrogen VS rust-zmq

This acquisition is very much in the context of https://hydrogen.shopify.dev/roadmap/#first-quarter and https://github.com/Shopify/hydrogen - Shopify very much wants to move to the modern era.

And to address your point, it's not gaslighting to say that React enables interactions that would be essentially impossible if restricted to server-side templating. But there's certainly some degree to which trendiness and a desire to attract developers into their ecosystem is driving this as well.

I would say its main selling point is obviously the integration with Shopify. It comes with hooks, components and types to make it really easy to interact with the Shopify API. (They also use an XState state machine for the cart.)

Shopify's got their own headless framework for storefronts built on React called Hydrogen. Just recently came out of beta. Has a built in React hook for GraphQL queries to the storefront.

All the activity around V8 Isolates + "workers" is so cool-- exceptional performance, don't need to think about regions, and CDN-like benefits

Shopify's new store-builder thinks this way too: https://github.com/Shopify/hydrogen

Not sure what documentation you're looking at, because we have a ton here: https://shopify.dev/custom-storefronts/hydrogen

Full Docs and Image Source

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