@ccfreak2k I obviously can't speak for them, and as an everyday .NET developer for more than an decade now - and an .NET ActivityPub implementer myself (in
#BirdsiteLive) - I'm highly biased on this mater.
But since I've shipped python's API product, and I have some JS/node background too, maybe I can give some insights on the advantages of this stack:
- ASP.NET Core is (really) efficient. .NET Core is too.
- It's FOSS. .NET Core and old .NET are a complete different beasts on this matter.
- It's highly and easily multi-threaded. The framework has a lot of tooling to do multi-threading and even a junior (been there, taught that) can create reliable and efficient multi-threaded apps.
- It's an industrial/engineering focused framework (in contrary to an academic focused framework), meaning it's highly tainted and focused on code cleanness, modulability, isolation, etc. Prototyping stacks (like Python or Node) are interesting in many cases/domains, but for the long run, industrial focused stack wins in my book.
But again, as a .NET dev, I'm highly biased, but .NET is a really vibrant ecosystem and can helps getting better software at a very low cost (which mean, in FOSS, at a lower personal non-payed/low-payed investment), the only thing against it is... being MS related.
And that's why I'm curious / happy seeing this stack growing in this space.