Is this project dead?

[whizsid]

I would like to add WASM support to https://github.com/google/tarpc crate by using this crate for wasm targets. But seems like this project was dead. Can anyone mention it officially?

[stan-irl]

yeah @tomaka it would be great if you could review some of the incoming PRs or hand it off to a willing maintainer.

Its a great library and the ecosystem really needs it, but in its current state its hard to justify using it

[tomaka]

I recommend against using this project. It is and has never been anything more than a quick hack while a proper solution is to be found, which is why it has no proper readme and I have never even talked about this crate publicly or on any solution media or anywhere in fact.

There exists two clean solutions that are better than this crate:

• Using wasm32-wasi
• Making your code entirely no_std and let the user manually plug the time input

I am not willing to spend time on, sorry to call it like that, "administrative bullshit". Getting a source of time in a cross-platform way shouldn't require any maintenance. If it does, it indicates something fundamentally wrong somewhere. All the people complaining about the lack of maintenance of this project are free to waste their energy and can fork this crate (it is under the MIT license, one of the most permissive) and publish their alternative.

[stan-irl]

thats totally fair. thankyou for clarifying

[stan-irl]

for others who find their way here. i'd suggest time-rs. It works nicely on wasm.

[whizsid]

@stan-irl time-rs is using for a different purpose such as formatting, parsing and manipulating dates. But the wasm-timer supporting intervals, delays and all the tokio related time functions. I could not find any alternative at the time. So I started to manage a hard-fork of this project (wasmtimer). Also I improved it to support Web Workers, Node JS, serde.

[tomaka]

For anyone reading this issue, also be aware using setTimeout is extremely hacky, for reasons explained here: https://developer.mozilla.org/en-US/docs/Web/API/setTimeout#timeouts_in_inactive_tabs

I can't stress enough: do not just assume that WebAssembly in browsers can do timers. You will have issues. For all purposes, assume that timers simply do not exist in browser wasm.

[stan-irl]

yeah sorry you're right @whizsid. also time-rs is just a wrapper around std::time and panics at runtime anyway I just realised.

Your wasmtimer package is working great! thanks for taking ownership of the project!! 😄

[youngjoon-lee]

@stan-irl time-rs is using for a different purpose such as formatting, parsing and manipulating dates. But the wasm-timer supporting intervals, delays and all the tokio related time functions. I could not find any alternative at the time. So I started to manage a hard-fork of this project (wasmtimer). Also I improved it to support Web Workers, Node JS, serde.

I also forked this repo with a super simple change: youngjoon-lee@15e8835.
I just used instant::Instant, which is WASM-compatible, instead of std::time::Instant and crate::wasm::Instant And, I removed the entire crate::wasm module. So, the wasm_timer::Interval now uses instant::Instant. This works with both non-wasm and wasm32.

You can see detailed explanation in my blog: https://oudwud.dev/posts/2305102345-made-rust-libp2p-gossipsub-work-in-wasm/