dotnet-webassembly VS TypeScript

there's a nuget WebAssembly package, so you can probably run assemblyscript on .net already.

It's been done

Zod is great. It has some weaknesses - you can't just reuse types from external libraries; it can be verbose.

There are some libraries that provide a cleaner experience (e.g. typescript-is/typia). But they rely either on code generation or extending the TypeScript compiler while Zod just makes do with some clever typing.

TypeScript itself will never integrate something like this as it goes against their design goals[1].

[1] https://github.com/microsoft/TypeScript/wiki/TypeScript-Desi...

I know you said don't get me started on the bugs TS caused, but I would like to hwar about them if you don't mind.

I personally only had one bug that was caused by TS itself (https://github.com/microsoft/TypeScript/issues/40726) so I'm curious to hear about the issues you encountered.

I have created an application with Go in Gin-Gonic. In my frontend (Nuxt3/TypeScript) I always get a CORS error:

Import JSON files as const (See relevant GitHub thread)

Since the OpenAPI Specification is a "machine-readable interface definition language for describing, [...] web services", and TypeScript is practically the only available type solution for Node.js, I confidently googled:

TypeScript: While not a Node.js feature, the growth of TypeScript as a strongly-typed superset of JavaScript synergized with Node.js, offering static typing and future JS features.

Let's start with the basics. TypeScript is a superset of JavaScript that adds optional static typing and class-based object-oriented programming to the language. The key word here is optional - you can use as much or as little TypeScript as you want!