TypeScript merge disaster

One of those annoying web people have just decided to drop support from the only good language to use for the web, an absolute foolish, unneeded and harmful decision, while rushing to merge the PR 2 hours after it was opened. Seems like he stubbed his toe real hard It’s about to go down. 🧨 🧯 Fully recognize that TypeScript offers some people some advantages, but to my eyes, the benefits are evident in this PR. The code not only reads much better, it's also freed of the type wrangling and gymnastics needed to please the TS compiler. We write all our client side code at 37signals now in pure JavaScript and the same too with any internal libraries. This is going to bring that in line. All the love and appreciation to contributors who would prefer TypeScript. This is one of those debates where arguments aren't likely to move anyone's fundamental position, so I won't attempt to do that.

A screenshot of a social media post criticizing a rushed pull request that removes TypeScript support and favors pure JavaScript. The embedded comment argues that JavaScript code reads better without TypeScript's type gymnastics, while the surrounding post mocks the decision as foolish and harmful. It is used as a reaction to heated programming-language debates and controversial technical changes. EN: A screenshot of a social media post criticizing a rushed pull request that removes TypeScript support and favors pure JavaScript. The embedded comment argues that JavaScript code reads better without TypeScript's type gymnastics, while the surrounding post mocks the decision as foolish and harmful. It is used as a reaction to heated programming-language debates and controversial technical changes.

• @gentoomemes / 6225 2023-09-06