From b43072f3110125e02b71d15d12b56c9b5dc1cc63 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Fri, 21 Jun 2024 01:20:45 +0100 Subject: [PATCH] Add daily email for 2024-06-17 Do you still need TypeScript? --- source/_daily_emails/2024-06-17.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 source/_daily_emails/2024-06-17.md diff --git a/source/_daily_emails/2024-06-17.md b/source/_daily_emails/2024-06-17.md new file mode 100644 index 000000000..72e08ddac --- /dev/null +++ b/source/_daily_emails/2024-06-17.md @@ -0,0 +1,28 @@ +--- +title: Do you still need TypeScript? +date: 2024-06-17 +permalink: daily/2024/06/17/do-you-still-need-typescript +tags: + - software-development + - typescript + - javascript +cta: ~ +snippet: | + Do you still need TypeScript? +--- + +There have been many discussions and videos recently asking if people still need to use TypeScript. + +There have also been large open-source projects moving from TypeScript back to plain JavaScript. + +The popular approach is using JSDoc comments - similar to PHP docblocks - to replicate some of TypeScript's features, such as autocompletion in IDEs and text editors. + +The suggested benefits are cleaner code and no build step, making it easier to work with and contribute to the code. + +I like using types in PHP and using static analysis tools such as PHPStan so, naturally, I gravitated to TypeScript. + +I wrote a custom form with TypeScript and Vue.js that was an entrypoint to a Drupal Commerce application - populating data from Drupal using an API endpoint and determining and creating a cart with the correct items based on the customer's selections. + +Whilst doing so, I found TypeScript very beneficial and I'll probably continue to use it in the future. + +But, leveraging JSDoc more in situations where I can't use TypeScript, such as writing Tailwind plugins and Stimulus applications, is great to know and to get the best of both.