Pauan

@dns2utf8 Where did you hear that?

@dns2utf8 Yes, that is correct, you must specify at least one of those options, like so: ```sh wasm-pack test --headless --chrome wasm-pack test --headless --firefox wasm-pack test --headless --safari ```...

> @fitzgen Maybe even blurring the lines and transparently running futures on etiher the server or client? Just FYI, thanks to help from @CryZe and @Diggsey (and myself), stdweb [now...

I have started work on implementing zero-cost virtual DOM and zero-cost signals / observables for Rust. It's not ready to publish yet, but you can find the code in the...

@OddCoincidence WebIDL would be nice, but it doesn't really exist (there's just the [non-standard spec](https://browserext.github.io/browserext/), which differs a bit from what the actual browsers do). There's no need to add...

@pablosichert Normally libraries don't have a `Cargo.lock`, since they're intended as... well, libraries. This is a bit of an odd case because it isn't a Rust library, instead it's an...

A couple more things which I think would be useful: * For performance reasons, it's probably faster to use a single `rAF` and then use a Rust `VecDeque` to support...

> I fear I'll have to use a `Rc` in the loop. Yes, if you want looping in Rust, that is necessary. If the looping is done in JS it...

> `pub fn new(millis: u32, callback: F) -> Alarm` This needs to accept `f64`, since `Date` cannot fit into a `u32` (even the current date is far beyond `u32`). >...

> after a certain amount of time, using setTimeout That's already handled by the gloo-timers crate. In fact, I think all of these would fit in pretty well in gloo-timers....