Skip to content

Implement WebAssembly (WASM) Support for Improved Frontend Performance #52934

@sdawson85

Description

@sdawson85

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

Yes, my feature request is related to optimizing frontend performance in ASP.NET Core applications. Currently, ASP.NET Core heavily relies on JavaScript for client-side operations, which can sometimes lead to performance bottlenecks, especially in complex web applications with intensive client-side processing. This reliance on JavaScript can limit the performance potential, particularly in scenarios requiring heavy computation or real-time data processing on the client side.

Describe the solution you'd like

I propose the integration of WebAssembly (WASM) support within ASP.NET Core. This solution would involve:

Enabling developers to write C# code that compiles to WebAssembly, allowing intensive computations to be run in the browser at near-native speeds.
Providing seamless interoperability between WASM modules and existing JavaScript frameworks/libraries used in ASP.NET Core applications.
Offering tools and documentation to assist developers in migrating performance-critical JavaScript code to C# (or another .NET language), which would then compile to WASM.
Ensuring the WASM integration is aligned with the current development workflow in ASP.NET Core, allowing developers to adopt it incrementally in their existing projects.
The addition of WebAssembly support would significantly enhance the capabilities of ASP.NET Core for building high-performance, client-side web applications. It would also open up new possibilities for complex front-end development using the .NET stack, aligning ASP.NET Core with modern web development standards and performance expectations.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs: Author FeedbackThe author of this issue needs to respond in order for us to continue investigating this issue.area-blazorIncludes: Blazor, Razor Components

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions