Freeze support of stdweb at v0.18

[jstarry]

Problem

Maintaining support for two browser binding libraries requires a lot of effort, duplicate code, and ugly cfg macros which make it hard for newcomers to make contributions. If forced to choose one, we should pick the library that the Rust community uses, supports, and enjoys using more. That library is clearly web-sys, not stdweb.

The biggest problem with supporting stdweb going forward is it's lack of recent development. The repository hasn't been active in about a year despite various features being missing.

Despite the lack of development, stdweb is a really great tool and provides a higher level of abstraction, nicer APIs, and a convenient js! macro over the web-sys library. Furthermore, the sister tool, cargo-web doesn't support web-sys, only stdweb.

Many of the above advantages have been solved in the new web-sys oriented ecosystem. wasm-bindgen alleviates the need for a js! macro, trunk replaces cargo-web, and libraries like gloo provide nice APIs.

Proposal

• After the v0.18 release, remove all stdweb code from master
• Remove all outstanding stdweb related issues.
• Remove all references to stdweb in the documentation besides a disclaimer informing users of the feature freeze
• Create v0.18 branch will be created to release patch fixes as needed

[therustmonk]

I've thought about it dozen times. It would be impossible to create yew without stdweb since it was a bridge between Rust and JS worlds, today we have to give a lot of respects to great stdweb project, but remove it to make yew simpler to maintain and closer to prod usage.

[teymour-aldridge]

stdweb was (is?) a wonderful library, and it's a shame that it seems to have petered out. Just one of many examples of the lack of sustainability in FLOSS, and that the infrastructure we all rely on is incredibly fragile.

[lukechu10]

Since v0.18 has been released, I think this issue should be closed.