3 ms·

.NET and EF Core is the platform that most teams probably want but .NET and C# can't quite shake it's pre-Core image. It always strikes me as odd that teams ca

.NET and EF Core is the platform that most teams probably want but .NET and C# can't quite shake it's pre-Core image. It always strikes me as odd that teams can embrace GitHub, TypeScript, and VS Code and then react negatively to C# and .NET being Microsoft platforms. EF Core is perhaps the most powerful, most mature ORM at this point. .NET Web APIs are incredibly productive and performant with really good DX. C# isn't that far off from TypeScript syntactically and structurally. I feel like teams that are "graduating" from TypeScript on Node probably want C# on .NET but end up exploring Go or Rust instead.

spion 3y ago
MS should've dropped the .NET branding once it became cross-platform.
- CharlieDigital 3y ago
  Absolutely. Rebranding would have helped in sooo many ways, even for the devs that moved forward from .NET Framework. For starters, it would have at least made search results less confusing and more contextual. There were years of confusion between .NET Framework, .NET Standard, .NET Core, and .NET 5. From a basic SEO perspective, rebranding would have been huge. It was a huge mistake to not rebrand it entirely.
lpapez 3y ago
For me that's not the primary reason. I was discouraged from learning C# because of the sheer number of keywords and concepts in the language. Contrasting this with Go where I landed a gig after two weeks of learning by myself and felt productive right away.
- CharlieDigital 3y ago
  The thing is, if you're comfortable with TypeScript, it's really more or less just a small step to C#; the Venn diagram of the most commonly used keywords between TS and C# has a high degree of overlap. A small repo here: https://github.com/CharlieDigital/js-ts-csharp 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 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. Edit: I'm actually curious as to which keywords you personally found the most challenging to grok or what tipped the scales of "this is too complicated".

spion 3y ago

MS should've dropped the .NET branding once it became cross-platform.

CharlieDigital 3y ago
Absolutely. Rebranding would have helped in sooo many ways, even for the devs that moved forward from .NET Framework. For starters, it would have at least made search results less confusing and more contextual. There were years of confusion between .NET Framework, .NET Standard, .NET Core, and .NET 5. From a basic SEO perspective, rebranding would have been huge. It was a huge mistake to not rebrand it entirely.

lpapez 3y ago

For me that's not the primary reason. I was discouraged from learning C# because of the sheer number of keywords and concepts in the language. Contrasting this with Go where I landed a gig after two weeks of learning by myself and felt productive right away.

CharlieDigital 3y ago
The thing is, if you're comfortable with TypeScript, it's really more or less just a small step to C#; the Venn diagram of the most commonly used keywords between TS and C# has a high degree of overlap. A small repo here: https://github.com/CharlieDigital/js-ts-csharp 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 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. Edit: I'm actually curious as to which keywords you personally found the most challenging to grok or what tipped the scales of "this is too complicated".