Why I don't enjoy using typescript or static languages much

TL;DR

The speaker prefers dynamic languages over TypeScript for personal productivity and simplicity.

Transcript

all righty y'all this is gonna be a very sensitive topic and i think a lot of people are gonna get offended by this um i've i've tried in the past to use typescript and for whatever reason i just don't like it and i want to kind of explain to you why i don't like it but honestly this always just boils down to a personal preference so if you like ty... Read More

Key Insights

• 👻 Dynamic languages favor a less structured approach, allowing for quicker coding and prototyping, which is often preferred by experienced developers.
• 👶 TypeScript is widely adopted in the industry, especially for new libraries and frameworks, suggesting a significant shift in programming practices.
• 👨‍💻 The speaker highlights the importance of readability in code, arguing that excessive typing can detract from understanding and enjoying the programming process.
• 🔇 Familiarity with a language can influence productivity; the speaker feels more freed and productive with dynamic languages due to their less stringent nature.
• 🙈 Type checking in TypeScript is seen as both a benefit for beginners and a hindrance for seasoned developers who value direct and less verbose coding.
• 👨‍💻 The experience of debugging in TypeScript is noted as a frustrating aspect, often requiring excessive attention to type compliance rather than the logic of the code itself.
• 👨‍💻 Personal preferences in programming languages are not necessarily rational but often stem from individual experiences and comfort levels with coding styles.

Questions & Answers

Q: What are the speaker’s primary reasons for preferring dynamic languages over TypeScript?

The speaker finds dynamic languages more enjoyable and productive for coding, emphasizing their speed and simplicity. They argue that the verbosity of TypeScript's static typing slows them down, making coding feel more like a chore than a creative process. Ultimately, they believe that dynamic languages facilitate quicker prototyping and development.

Q: How does the speaker view the learning curve associated with TypeScript?

The speaker acknowledges that TypeScript can be beneficial, especially for beginners who may struggle without the enforced structure of static typing. However, they express a strong preference for the freedom to code without rigid constraints, suggesting that excessive type-checking complicates the learning and coding experience for those who are more comfortable with dynamic languages.

Q: What experiences does the speaker recount regarding their time with TypeScript?

The speaker reflects on using TypeScript during their work with AngularJS and other projects, noting challenges with generics and complex type-checking. They recount instances of struggling to understand TypeScript's code structure, leading to feelings of anxiety and frustration when trying to navigate legacy codebases filled with type annotations.

Q: Does the speaker see a potential future with TypeScript?

While the speaker recognizes that the industry is shifting towards TypeScript, they are apprehensive about having to fully embrace it in future jobs. They humorously express that they feel like “an old dog” reluctant to learn new tricks, fearing that they might eventually need to adapt to TypeScript despite their preference for dynamic languages.

Summary & Key Takeaways

• The speaker discusses a personal dislike for TypeScript, stating that while it has benefits, they prefer dynamic languages for their productivity and less verbosity in code.

• They acknowledge the growing adoption of TypeScript in the industry but express concerns about the added complexity and verbosity that static typing introduces to code reading and writing.

• The speaker shares experiences with TypeScript while working on various projects, highlighting frustration over type-checking hindering rapid prototyping and simple testing.