gloo VS gloo

These are two separate libraries that do very different things but share the same name. They are also written in two separate languages. That is a sizable gap between them, and reusing names happens often with libraries. Gloo (rust-wasm, this post) is also not new. Though, relative to Gloo (Go, solo-io), it is newer. But, there is also a Github repo even older than Gloo (solo-io): https://github.com/facebookincubator/gloo. As well, even if these were for some odd reason all about wasm, none of them are actually that popular. solo-io Gloo has the most stars (though that isn't the best metric of popularity, since it is relative to the community that actually uses it), but 3k simply isn't that much. There is certainly a good argument to look down on libraries that reuse popular library names, but this isn't really the case here. Both started not too long after each other (solo-io would not have most of the stars it currently has when Gloo-Rust started), are in separate languages (thus separate communities), and do very separate things.

backends from native torch distributed configuration: nccl, gloo, mpi.

In the rust world I’m learning yew and trying to contribute to gloo_net.

What about adding it to gloo?

Hoping to get this PR finished up and merged. It's mostly done, just need a second set of eyes to make sure I didn't fuck something up

Gloo is in need of an icon. See gloo#143 for more details.

Yew and Gloo

See gloo#18

I've been using it for keyboard and mouse event handling in a wasm project I've been working on and it's quite helpful. There's a proposal that would make this even better.