Why TypeScript is Actually Good

I respond to my last video and explain why my points are not valid. I much prefer TypeScript to JavaScript and find it very good.

Video I'm responding to:
​
----
#benawad

[_mohyddin]

I prefer to write my JavaScript code in binary, that way I only have to think in 0s and 1s and have less distraction.

[aayush_dutt]

Plot twist: He mistakenly interchanged the two videos and uploaded them in wrong order.

[RavnitSuri]

What I figured out from reading a bunch of long typescript errors: The error that usually makes the most sense is usually in the last line of error.

[ryanngalea]

That wasn't really a bug, just a poorly named function.

[geooot]

Typescript simultaneously makes me feel like a freaking genius and complete idiot at the same time.

[mikaknuuttila]

Enough is enough, Ben. You're taking this April's fools joke way too far

[AlexEscalante]

Half of my day I spend writing C# on the back end, so I know: the visual clutter is a thing, specially because of templates (var helps a lot), but now that I moved to Typescript from ES6, I love the extra help!

[randmtv]

I like Typescript, especially because it gives me amazing autocomplete in VS Code when you use it an it's nice to catch type errors even before your code runs. Although I hate that it sometimes gets in the way for code that you know works 100% by saying that some property doesn't exist etc., so you have to either somehow find a way to type it properly or just use "any", which then defeats the point of it unfortunately.

And regarding Typescript Tax, you will definitely feel it when you start using it and until you get some experience with it. You will fight with it on multiple occasions definitel, but overall it's a nice tool.

[wcandillon]

This video made me laugh harder than the April's fool one 😀

[danieldosen]

You don't know what Bonjour means!? Sacre Bleu!

[teytag]

Upsides of TS:
* easier traversal of annotated objects
* better schema definitions for functions and classes
* type safety, early warnings on improper usage, and yes, sometimes safer code like having to check for null
* easier inline documentation for those that can read TS

Downsides of TS:
* learning curve
* more responsibility in architecting types and type systems. if these are done poorly code can be unreadable
* env dependencies and library workarounds at times of lacking support
* false sense of 'error free' and (depending on team experience) a devaluing of unit testing due to the assumption that TS prevents bugs

Not an exhaustive list, but as always, pick your poison. There is no right answer, just the right answer for you, right now, for this project

[xucongzhan]

Type annotation, if anything, improves readability. It's self-documenting and provides more information about the intention of the code.

[beardmcweird]

The best thing about typescript is not needing to sift through documentation for apis online anymore, its always one click away.. Take the google maps api as an example. Knowing how to interact with it sooo much more intuitive with ts.

[zachwhite]

the lighting in your videos is borderline Gothic. you need to start ending these with an evil Dracula laugh

[samuelschwager]

In a time of NoSQL, NoEstimates and NoCode we want NoTypes, right? ;)

[lwrcica]

It's the wild wild west with react changing so much from year to year. Best patterns emerge over time, and Typescript enables us to refactor on the front end pain free. (or less pain)

[ChrisStolba]

Typescript must've bought him off since the last video... he is compromised!!!!

[DopaChinchiillaz]

I always have to watch your videos on 1.5x speed in order for it to sound normal speed

[ThomasWSmith-wmxn]

I like typescript because I like heavier bundles, typing more than i have to, and made up errors for problems that don't actually exist in js.

[thearcticmonkey]

Once I heard this argument from a developer:
He said his front-end team didn't use TypeScript because they are an experienced team of developers and didn't feel the need to use it because with their experience they felt comfortable and confident in their skills to use Javascript.


He made TypeScript sound like a language for teams with short experience in Javascript and what he said stuck in my mind...
I have been using TypeScript for a while and I have 5 years of experience in Javascript and after trying TypeScript, I just can't go back to Javascript and it's very hard for me to understand his argument.
In my view, no matter how much experience you have, TypeScript will help with and avoid problems in the future no matter how much experience you have. Makes me think those experienced devs never really understood the power of TypeScript...

Cheers!