dotnet6-openapi VS js-ts-csharp

.NET Web API has great tooling for generating OpenAPI on build. Once you have this, you can easily generate TypeScript bindings for your front-end. See also: https://github.com/CharlieDigital/dotnet6-openapi

This will scaffold a project which is more or less the exact same as Flask, Express, or any other "easy" framework.

OpenAPI output is built-in, but tooling for development does require a bit of knowledge (agree that Microsoft would benefit from making this work out of the box).

A small repo here showing how to connect OpenAPI and front-end TypeScript client generation: https://github.com/CharlieDigital/dotnet6-openapi

I have one example that shows how to do this with Vue and Svelte: https://github.com/CharlieDigital/dotnet6-openapi

A lot of the work I've done is closed source, but I do have a simple template here that is a typical starting point: https://github.com/CharlieDigital/dotnet6-openapi

The thing is, if you're comfortable with TypeScript, it's really more or less just a small step to C#.

A small repo here: https://github.com/CharlieDigital/js-ts-csharp

And a practical example of a Playwright web scraper in C# and TypeScript: https://github.com/CharlieDigital/playwright-scrape-api

"Too many keywords" is the weirdest objection to a programming language versus actually using the language to build something practical.

[1] https://github.com/CharlieDigital/js-ts-csharp

Modern C# isn't that big of a lift from TypeScript. If you can write TypeScript, you can write C#. Much easier transition than say Go or Rust. See also: https://github.com/CharlieDigital/js-ts-csharp

> ...this project is a nice showcase how versatile C# and .NET is

C# and .NET are highly underrated/underappreciated because of some early flops and the Microsoft branding.

It's converging with TypeScript in the best way possible[0] and has some really great language features that even TS is lacking (really powerful switch expressions, for example).

It seems like the natural option for teams that want to move from TypeScript to a compiled, multi-threaded, statically typed language but it seems that there's a lot of teams that would rather use Go or Rust; neither of which are as easy to step up to from TypeScript, IMO.

[0] https://github.com/CharlieDigital/js-ts-csharp

Should it be C#? I think the transition to C# is the easiest because of how similar TypeScript and C# are at some levels (small repo here showing the similarities: https://github.com/CharlieDigital/js-ts-csharp)

I have a small repo here that shows just how similar the JS, TS, and C# are: https://github.com/CharlieDigital/js-ts-csharp

For me, I use TypeScript and C# almost interchangeably now. Most of the patterns I would implement in C# I can also implement in TypeScript. It's very easy to move between them (exhibit A and exhibit B).

Bonus: TypeScript is soooo similar to C#; completely worth your time to learn it.