IE11 Support (Transpilation Policy)

[kfule]

Since Mithril v2.2.3, m.domFor() introduces generators and for-of loops, so transpilation appears to be mandatory for IE 11. A polyfill alone is not enough.

So, I would like to proceed with one of the following options:

1. Rewrite to ES5

• Rework the affected parts to ES5 equivalents so that transpilation is unnecessary.
  • Pros: Removes the need for a build step.
  • Cons: Code becomes more verbose.

2. Assume transpilation

• If relying on transpilation is acceptable, I would like to introduce the spread operator into hyperscriptVnode.
  • Pros: The code becomes simpler and performance seems to improve by a few percent.

Although I personally no longer use IE 11, I recognize the value of supporting it and believe either option is valid.
I would appreciate your feedback.

[kfule]

I think the README.md description also needs to be improved.

[dead-claudia]

I vote dropping the IE support claim instead in the README. It's essentially dead, with a very limited number of Windows distributions (all long-term support releases) still having any official Microsoft support: https://learn.microsoft.com/en-us/lifecycle/faq/internet-explorer-microsoft-edge

The few devs who still target IE are people who need several years to update to a modern browser flow.

It's worth noting that IE global market share has dipped to the 0.2-0.5% range on desktop and 0.1-0.2% range on all devices.

[kfule]

Thank you for your comment.😄
IE11's market share seems to be decreasing more than I imagined.

So, I would like to drop its support from the README and also submit a PR for performance improvements, including the spread operator as mentioned above.

[dead-claudia]

So, I would like to drop its support from the README and also submit a PR for performance improvements, including the spread operator as mentioned above.

Feel free to submit one.

Edit: also, if you find instances in https://github.com/MithrilJS/docs, feel free to file a PR there as well.