[mukundesh]

Only available in .NET ecosystem, got excited after I read the title, but forgot Microsoft is Microsoft.

"YARP is a reverse proxy toolkit for building fast proxy servers in .NET using the infrastructure from ASP.NET and .NET."

[throwuxiytayq]

I don't get it, what do you even expect them to do? Write it in Java? It's MIT-licensed, you can rewrite it if you wish.

[square_usual]

Yeah - whatever language they chose it would be "only available for [that] ecosystem." At some point you've got to pick your home, not like you can write a 100% cross-language framework for anything.

[stanac]

Hopefully one day most devs will share one home called wasm runtime. Although not sure if it applies to this scenario (lower-level code).

[maloo]

WASI? there are already prototypes of running .net in WASI that might make it for .net 7

And WASM is already supported, app size about 1MB including runtime and GC

[pdpi]

It’s written in C#, probably because they use a bunch of C# internally for this sort of project (who’da thunk it?). That naturally restricts the project to .NET environments.

That line could easily have read “for building fast proxy servers in the JVM” or “for building fast proxy servers in node.js” or whatever else, and it would’ve still been just as restrictive.

[maloo]

Still more flexible than the "app" style proxies. And there is ongoing work to allow c export and not just imports in C#. Which means you could make it a library for any language, but of course with your own custom interface since you can't call the C# apis unless you export a function to C.