![]() I personally think that for most JavaScript developers, the lift from JS to TS is much more significant than the lift from TS to C# to the extent that a team choosing to start a greenfield backend project in TS should evaluate C# as well. Others have expressed a concern that the lift from JavaScript to C# is too high and not feasible with the existing developers on the team yet push heavily for TypeScript after suffering the challenges of working with JavaScript on the server at scale. When discussing the possibility of considering C# instead of TypeScript on one project with another developer, he stated that he always thought C# was more like C and C++ and was surprised by how closely it resembled TypeScript upon looking at C# more closely. However, many of those platform misunderstandings persist and engineers and teams without exposure to C# simply do not realize how trivial the lift is between TypeScript and C#. NET that are simply no longer true as the. ![]() Of course, there are several “myths” about C# and. NET even just 5 or 6 years ago - have a complete misunderstanding of where C# and. The biggest challenge is that many recently minted engineers - and frankly even engineers who may have looked at C# and. ![]() When proposed to various teams, the responses I’ve gotten have been interesting. As I’ve worked with JavaScript, TypeScript, and Node backends over the last year, there was always a point in the project when I wonder “This would be way better in C# and.
0 Comments
Leave a Reply. |