aeric Expert Licensed User Longtime User Jan 4, 2023 #1 17 Compelling Reasons To Start Ditching TypeScript Now. If you're anything like me, you're probably using Typescript because you were forced to. Your company... dev.to
17 Compelling Reasons To Start Ditching TypeScript Now. If you're anything like me, you're probably using Typescript because you were forced to. Your company... dev.to
Mashiane Expert Licensed User Longtime User Jan 5, 2023 #2 Compliments I have been curious about it... i will read and see what the fuss is now about.
aeric Expert Licensed User Longtime User Jan 5, 2023 #3 I like the Conclusion. TLDR; In my honest opinion, going from JavaScript to Typescript is like transitioning from PHP to C#. The core concepts remain the same. However, you are adding a layer of type safety and an additional compilation step. Click to expand...
I like the Conclusion. TLDR; In my honest opinion, going from JavaScript to Typescript is like transitioning from PHP to C#. The core concepts remain the same. However, you are adding a layer of type safety and an additional compilation step. Click to expand...
Mashiane Expert Licensed User Longtime User Jan 5, 2023 #4 I dont have enough knowledge about it. But there seems to be a big disjuncture here. 7K positives compared to the 550 negatives if we say...
I dont have enough knowledge about it. But there seems to be a big disjuncture here. 7K positives compared to the 550 negatives if we say...
alwaysbusy Expert Licensed User Longtime User Jan 5, 2023 #6 Compleet overkill in my opinion. The article writer makes some good points. Not a fan at all of it. I've seen languages (like Xojo) who implemented it instead of JavaScript. (No idea why as they had 100% control over the code they wrote). Result is a slow framework where it takes ages to implement even basic stuff. But yeah, it isn't the first blunder that company has made over the years and making very bad design decisions. Last edited: Jan 5, 2023
Compleet overkill in my opinion. The article writer makes some good points. Not a fan at all of it. I've seen languages (like Xojo) who implemented it instead of JavaScript. (No idea why as they had 100% control over the code they wrote). Result is a slow framework where it takes ages to implement even basic stuff. But yeah, it isn't the first blunder that company has made over the years and making very bad design decisions.
