custom-elements VS pushgen

Not quite finished and no docs yet but code and examples for Yew and vanilla web_sys on Github.

Here're a few projects I considered interesting (including my own project) and relatively easy to participate: - pushgen Push-style design pattern for processing of ranges and data-streams. - compact_str A memory efficient immutable string type that can store up to 24* bytes on the stack - openssh-rs Scriptable SSH through OpenSSH in Rust - pegasus A multi-node parametrized command runner with a focus on simplicity - concurrent_arena Container that can have elements insert/removed concurrently and uses a 'u32' as key.

For me, its the explicitness in Python that is killer. I can see a name and match that to an import and match that to a package. Grabbing a function pointer works exactly as I would expect.

Stealing from Krister Stendahl's laws for religious discourse, Ruby's composable iteration is one area I have holy envy, particularly after I got used to it in Rust. I've used Python's generators many times just to have to switch to an explicit for loop. Things are generally better with a composable iteration model but occasionally I find myself switching to loops in Rust.

Unlike Ruby, Rust does pull-iteration, like Python, though there are experiments with Ruby-style push-iteration [0] [1].

[0] https://github.com/AndWass/pushgen

[1] https://epage.github.io/blog/2021/07/pushgen-experiment/

Continue my work with pushgen but also started doing some experimentation on a sender/receiver concept based on a the P2300 std::execution paper, and how that could work in Rust: txrx