js-ts-csharp VS MikroORM

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.

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

https://www.npmjs.com/package/mikro-orm - 44 issues

Mikro-ORM is a TypeScript ORM that focuses on simplicity and efficiency. It supports various SQL databases and MongoDB. Mikro-ORM is known for its simplicity and developer-friendly APIs. It provides a concise syntax for defining data models and relationships, making it easy to use.

I found MikroORM [0] to be quite reasonable if you're in the TS ecosystem already. It was also easy to do custom, raw queries, and really just felt like it wasn't in the way.

[0] https://mikro-orm.io/

It also does code generation into its own module, so good luck with hoisting in a monorepo where you want multiple independent prisma schemas. MikroORM[1] is a much better alternative to Prisma in my opinion but any ORM carries some form of baggage.

[1] https://mikro-orm.io/

More about v6 development can be found here.

I recommend looking at https://mikro-orm.io/