3 ms·
Interesting! I’ve recently made a switch from C# to TypeScript and I’ve found prisma to be such a relief from working with entity framework. Not that entity is
by EnKopVand 5y ago
Interesting! I’ve recently made a switch from C# to TypeScript and I’ve found prisma to be such a relief from working with entity framework.
Not that entity is bad in any way, it’s just not as productive. Which is sort of how I have it with most of the journey into TypeScript. It’s just a really great environment especially in Azure Function apps, and a massive cadeau to Microsoft for making the node in docker such a first class citizen in their Azure environment!
In many ways I feel like TypeScript is a mix of the best of Python and C# and that’s just wonderful, for me.
But writing things like Odata APIs in .Net sure has some benefits from the massive work Microsoft has done with the .net and C# environment since moving core into the main .net or however you describe it.
So now I’m not sure where I am going with this, I’m probably just very appreciative of the work Microsoft has done for us enterprise developers in non-tech enterprise in the past few years.
- CharlieDigital 5y agoPrisma's query syntax feels quite verbose to construct and reminds me of CAML from my SharePoint days (except JSON vs XML). It's also lacking support for a lot of data types on PG. It's crazy that EF Core has providers for everything from SQL Server to CosmosDB to Google Spanner to in memory DBs. LINQ and expression trees are probably one of the best features of .NET.