Open SteveSandersonMS opened 1 year ago
Thanks for contacting us.
We're moving this issue to the .NET 8 Planning
milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
Thanks for contacting us.
We're moving this issue to the .NET 9 Planning
milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
I didn't make any tests but I believe that WASM application with SIMD instructions enabled should run faster. Unfortunately SIMD instructions are not available in iOS 15.x. Currently (February 2024) there are 11% of iPhones and 18% of iPads with iOS 15 or earlier (source: https://developer.apple.com/support/app-store/). I also noticed that even simplest Blazor WASM application can be unreliable on phones with 2GB of RAM (iPhone 6s, some Android phones). These are two examples where Auto
rendermode should eventually fallback to Server mode and not even load WASM files.
The initial implementation of the
Auto
rendermode will be hardcoded to make its choice based on whether the WebAssembly files are already downloaded and cached.Some developers may want to implement custom rules, e.g.:
There could be a JS-side callback to allow arbitrary JS code to make the decision.