interface-types
ASP.NET Core
Our great sponsors
interface-types | ASP.NET Core | |
---|---|---|
20 | 1,632 | |
636 | 34,312 | |
- | 1.6% | |
2.8 | 9.9 | |
almost 2 years ago | 2 days ago | |
WebAssembly | C# | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
interface-types
-
WebAssembly Playground
Some things that might greatly increase wasm usage and overall tooling:
1) Tools that run docker containers and serverless function services (like AWS lambda) to support providing a .wasm files instead
2) Garbage collection in the runtime to make GC languages easier to port to wasm
3) Dynamically typed languages (NodeJS, Python, Ruby) being able to compile to webassembly directly instead of porting the runtime to webassembly and then running the code through the runtime. This is a big ask though, basically needs to redesign the runtime completely
4) wasm-DOM bindings will enable other languages to do HTML rendering which will require new web frameworks for every language that wants to take over the space from JS. This will lead to (even more) fragmentation of the web ecosystem
5) A new wasm-first SDK (unrelated to the DOM) for building cross platform applications. I can see this taking off only if it is built-into the browsers and backed by some standards committee, so not very likely I think
6) Something like the Interface Types proposal ( https://github.com/WebAssembly/interface-types/blob/main/pro... ) becomes a thing allowing wasm programs to be consisted of modules written in several different languages and being able to call said modules with low or 0 runtime performance hit (and of course, no compilation to multiple CPU archs). So much of programming ecosystems are locked to specific languages (like data science with python) when there is little technical reason for it be like that.
-
Bring garbage collected programming languages efficiently to WebAssembly
AFAIK GC is irrelevant for "direct DOM access", you would rather want to hop into the following rabbit hole:
- reference types: https://github.com/WebAssembly/reference-types/blob/master/p...
- interface types (inactive): https://github.com/WebAssembly/interface-types/blob/main/pro...
- component model: https://github.com/WebAssembly/component-model
If this looks like a mess, that's because it is. Compared to that, the current solution to go through a Javascript shim doesn't look too bad IMHO.
-
Rust & Wasm (Safe and fast web development)
I'm not really optimistic that particular aspect will get much improvement. Many people expected interface types to come save the day, but after a looong stagnation that proposal has been archived (for now) in favour of component types, which has much less potential for performance gains.
-
Plugins in Rust: Wrapping Up
Really good questions. Unfortunately, most of the issues I found back then were fundamental ones. I've seen that Wasm has deprecated "Interface Types" and is now working on the "Component Model". But even then, as far as I understand that would only avoid the serialization and deserialization steps, and you would still need to copy complex types. It will be more performant, but I don't think it would be enough for Tremor either.
-
When moving from JS to WASM is not worth it - Zaplib post mortem
wasm doesn't know anything about the outside world on purpose. This allows it to be used in other domains. For direct access to the DOM et al, interface types are being developed. It's a non-trivial problem to interoperate with a dynamically typed GC'd language from any statically typed no-GC language that can compile to wasm.
-
WebAssembly 2.0 Working Draft
You may want to look into WASM interface types, which is defining what amounts to am IDL for WASM and different languages have common calling conventions: https://hacks.mozilla.org/2019/08/webassembly-interface-type...
I don’t know if there’s a better intro article. I believe this is the current iteration of the proposal: https://github.com/WebAssembly/interface-types/blob/main/pro...
-
Replace JS with Rust on front-end, possible? Advisable?
Yes, and if I'm not mistaken, this is the RFC
-
Google Chrome emergency update fixes zero-day used in attacks
I see no reason why not. See the interface types proposal for a proposed solution.
- Rust for UI development
-
Front-end Rust framework performance prognosis
Wanted to get thoughts from the Rust experts on this - the author of the Yew framework seems to think that Web Assembly Interface Types (https://github.com/WebAssembly/interface-types/blob/master/proposals/interface-types/Explainer.md) will allow Yew to eventually become faster than Vue, React, Angular, etc. Is there general consensus on this in the Rust community? The prospect of mixing Rust (for the performance critical pieces) with TS on the front end doesn't seem super appealing to me.
ASP.NET Core
-
Middleware in .NET 8
This approach to organizing middleware enhances code readability, maintainability, and reusability. By following this encapsulation pattern, you're adhering to best practices in ASP.NET Core development, ensuring your application remains well-organized and scalable.
-
.NET Monthly Roundup - March 2024 - .NET 9 Preview 2, Smart Components, AI fun, and more!
🌟.NET 9 Preview 2 ➡️.NET 9 Preview 2 Discussion ➡️ASP.NET Core updates in .NET 9 Preview 2 ➡️ASP.NET Core updates in .NET 9 Preview 2 Release Notes ➡️EF Core updates in .NET 9 Preview 2 ➡️.NET Aspire preview 4 - .NET Aspire
-
Chrome Feature: ZSTD Content-Encoding
https://github.com/dotnet/aspnetcore/issues/50643
-
The Mechanics of Silicon Valley Pump and Dump Schemes
Even if you look at Microsoft’s by far most popular GitHub project, they’re still only half as big as SupaBase. If you believe “the SupaBase story”, SupaBase grew and became twice as large as Microsoft in 3 years. Below is their likes over time if you’re curious, together with a couple of additional “too good to be true” Silicon Valley projects.
-
Bug Thread
https://github.com/dotnet/aspnetcore/issues/10117
-
Evolutive and robust password hashing using PBKDF2 in .NET
To achieve these objectives, we will take inspiration from ASP.NET Core Identity's PasswordHasher class. It incorporates a concept of hash versioning, allowing only the number of iterations to be modified.
- Experimenting with .NET 8 Blazor Web App w/ the Blazor Server rendering mode enabled but I can't get any my events to fire.
-
Observable or promise for http call from ASP.Net
yes I watched several courses, may be aim not getting clearly. but i worked with asp.net which uses http call and firebase cloud function also which uses socket connection, for socket connection its makes sense to use observable bcoz there streams of data we can observe once the connection establish ,but for http it need to be call every time.
- Como conseguir mi primer laburo
-
Working with Excel Interop and BGWorker
As I'm not utilizing ASP.NET, despite its resource-intensive nature and occasional unpredictability, I prefer the cost-free option. I'm hesitant to invest in EPPlus or engage in trials, and moreover, I am more proficient with Interop. Given the limited volume of records in my department, there's a preference for utilizing tools covered by our existing license. This avoids the need for navigating through layers of approval within the chain of command and ensures compliance with our contractual agreements and Microsoft's patch management, ultimately aligning with a cost-saving mindset.
What are some alternatives?
assemblyscript - A TypeScript-like language for WebAssembly.
Blazor.WebRTC
gc - Branch of the spec repo scoped to discussion of GC integration in WebAssembly
Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
deno - A modern runtime for JavaScript and TypeScript.
meetings - WebAssembly meetings (VC or in-person), agendas, and notes
inertia-laravel - The Laravel adapter for Inertia.js.
proposals - Tracking WebAssembly proposals
PuppeteerSharp - Headless Chrome .NET API
wasm-fizzbuzz - WebAssembly from Scratch: From FizzBuzz to DooM.
CefSharp - .NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework