Document browser compatibility

[Boscop]

1. Does it support old browsers like IE8/9 via asm.js?

2. How big is the resulting app js file for TodoMVC with asm.js?

3. Would you recommend it for commercial apps in production that need to target old browsers like IE8 on WinXP and Safari on iPhone4?

I'd prefer to use this at my job (compared to Elm which is very verbose) :)

[rivertam]

1. I believe this question is better suited for https://github.com/koute/stdweb.
2. Maybe someone else has an answer, but why don't you build it and try it out for yourself?
3. Personally, I would highly not recommend using this for commercial apps in production. Typically, semantic versions < 1.0.0 (this crate has a current version of 0.3.0) are never recommended for use in production due to unstable APIs and general lack of maturity.

[Boscop]

I don't mind living on the edge, I also use rustc nightly in production (rocket needs it) etc.
But I care about the size of the app js file..
I'll see if I can get emscripten to work and test with asm.js, just thought someone had already done it maybe :)

[rivertam]

Subjectively, Yew is in a far more experimental state than Rust nightly/Rocket. I can't speak for everyone, but I have serious doubts any contributors would recommend using Yew in production in its current state.

[koute]

The support for old browsers (like IE8 and such) is limited by what Emscripten supports. I don't remember what minimum version of IE it supports, but for those old IE versions you need to disable certain Emscripten features to get it working (e.g. IE9 doesn't support typed arrays so you need to pass some magic linking flag to Emscripten [which I don't remember] to get it to load). Also, I never tested stdweb on anything else than IE11, so there is a significant chance it won't work on something older.

[Boscop]

But everything works with IE11+?

[koute]

No idea; I tested that a long time ago. It may or may not work. If it doesn't then it should be possible to make it work without much trouble, I think.

[dalen]

There are also some webasm polyfills that might help with IE11 support, I haven't tried them myself, but have seen live demos of them.

• https://github.com/lukewagner/polyfill-prototype-1
• https://github.com/rfk/wasm-polyfill

[mc1098]

Hi 👋,

I agree that having browser compatibility information would be really helpful but as Yew is still in a state of constant flux this is a moving target. I worry defining the compatibility then might lead Yew into having to worry about backwards compatibility for browsers as it moves through versions which isn't what Yew should be worried about before "1.0.0".

#1948 was a similar issue raised and was closed due to the maintenance burden of keeping track of compatibility.

Once Yew gets closer to "1.0.0" then I completely agree that this would be invaluable to have!

I am going to close this issue for now - please let me know if you don't agree with this otherwise happy coding ❤️