This weekend I watched a talk about TypeScript at Nebraska.Code(). The presenter seemed to have a good grasp of TypeScript and was a good presenter. Sadly, that combination doesn’t always happen.
One thing I was glad about, was that he put up a picture like this:
- No type safety
- Functional language with inconvenient syntax
- Object base, not object oriented
- Few organizational constructs
He then offered the following reasons as to how TypeScript helps:
- Optional static typing
- Familiar OO constructs
- Enhanced functional experience
- Improved code organization
- Works w/ existing JS libraries
After watching this talk, I’m still not convinced that TypeScript is the way to go. I like ObjectOriented programming. The bulk of my career has been using OO principles (C++ and C#.) But I’m of the mindset that not every language has to be object oriented. After all, C is not object oriented and it definitely serves a purpose. That doesn’t make C a bad language. Just as Haskell isn’t a bad language. Just because they are not object oriented. Are they possibly harder to learn? Maybe, or maybe they’re harder to learn only because we’re so used to OOP.
I’m reminded of when I was in seminary. I took 15 hours of Greek and 15 hours of Hebrew. I started with the Greek classes, and they were way easier than Hebrew was. I had a smart friend who started with Hebrew and he really struggled with Greek. To me, it was strange, because Greek was so much easier to me. The problem was, he was coming from a different paradigm, a good grasp of Hebrew, to a new paradigm, koine Greek.
Those are just my thoughts. I’ll still keep reading & listening to stuff about TypeScript. I’m sure at some point, I’ll try to write a Hello World type of application. But it’s still further down the list of things to learn for me.