3/10/2024 0 Comments Dosbox debugger stuck g flag![]() As u/duvoh said, it's just something else to slow down the overall development cycle.That's largely moot though, our browsers support classes, async/await, and even ES modules natively. At one point I really appreciated the polyfills (probably not the right name in this context, but you'll get the idea) where it rewrote JavaScript code like async/await which was not yet widely available into a form that could run on older browsers.However! For my own personal projects, I don't touch it for a few reasons: The majority of the developers wanted to use it and I agreed. I use it at work for software we've worked on for many years now. I generally only talk with friends and close collegues about TypeScript as it's a bit of a death trap to discuss the downsides of TS on the internet. ![]() UNLESS specs, techstack or architecture changes midway through a project. Stay civil.ġ) TS is slightly more difficult to read (more LOC, more indirection, complexity of code structure statements can outrun the complexity of actual code)Ģ) Pre-Mature Optimization is a bigger issue with TS than it is with JS.ģ) Third Party Code integration without Types can lead to a lot of unproductive work.Ĥ) Integration in Node is still a few extra stepsĥ) Generally speaking: The 5% of use-cases where TS just failed to figure out Third-Party Code or React Components rendering loop could lead to hours spend re-arranging code without any actual use.Ħ) Tech Debt with TS is generally heavier although it incurs at a slower rate. This is just the downsides and not the upsides as the OP wanted. I am a bit hesitant to go with TS on every project and with every team. TypeScript allows devs to be busy on coding in a way that might not actually progress into a shippable product with all the busywork applied. It's certainly not adding the value that the Holy Zealots of TypeScript Church is promising. TS brings a lot of merit while incuring some complexity cost. We use TypeScript on roughly 70% of our projects. So, for you, your teams, your side projects, or what ever it is, I'm interested in your experiences with both JS and TS, and why you choose one over the other. The quicker feedback loop is very much appreciated. ![]() I use typescript because I like to be told what I'm doing wrong - before I tab over to my browser and wait for an update (no matter how quick (HMR has come a long way!).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |