The Story of TypeScript

[@bawad]

I love typescript

[@jsjoeio]

always bet on typescript

[@wcandillon]

Maybe that April fools joke would go down better in 2022 😉

[@uidotdev]

Say it slower Daddy

[@rawallon]

@@uidotdev slower

[@sbrugby1]

I look forward to the near future where TS is the norm. Already seeing it happening in Next.js official example repos, rewriting their basic with-tailwind in TS. React remix tutorials also just come at you with TS out of the gate.

[@ELStalky]

One of the biggest advantages is change management. You adjust one function signature and the entire codebase lights up like a Christmas tree, showing all the places that need adjustments. Or just basic things like renaming a symbol across all files can be done (mostly) automatically.

[@uidotdev]

Agree that's a good one.

[@MilanDrazic]

Wow, and you just watching and waiting to TS tell you what to do Typescript does not solve JavaScript problems. OOP e..g

[@blank4157]

@@MilanDrazic what OOP problems does JS have tho?

[@041e71]

I always thought TS is great for large applications, but it's actually also really helpful in prototyping. What you describe really helps in environments where things change a lot and it gives some peace of mind that stuff will probably work after adjusting

[@Eichro]

as opposed to vanilla javascript which is cringe management

[@seanhuggins5382]

Please keep making these history videos! I feel as a younger dev coming into the space, I've missed out on learning a lot of the tech that brought us to where we are today. These videos help unfurl the layers of the SWE onion.

[@uidotdev]

Thank you! I've always believed understanding the historical context was underrated in education. Glad you found it useful as well.

[@Miketar2424]

If you think like that you're going to be great as a developer. If you look into assembly language, even as an academic exercise, even better.

[@uidotdev]

@@victorcheeney3633 Just started working on "Why React Won" today :)

[@xylvnking]

for real these types and fireship have helped me so much in getting 'context' for these technologies

[@ozzyfromspace]

I gave typescript a shot in early 2021 and never went back. MS did a great job.

[@uidotdev]

Agree!

[@MrC0MPUT3R]

I've been using typescript since 2014 and I STILL do *not* understand why some people are reluctant to use it. Every project I write that requires javascript is instantly translated in my brain as "obviously this'll be typescript" I only use javascript for quick test apps and I find myself beating my head against the wall without my comforting type constraints 😭

[@aca48]

My company wanted to move away from Angular, because some loud colleagues found it way too strict (as it always comes with TS), and the half year release schedule made our projects after 1.5 year obsolete, because we did not keep up with the versions. As we don't write test, most of them don't use TS features (use any most of the time) the management did not see the benefits, they wanted all the new projects to be in React.js. Like plain React no TS. It took us some time with my leader, to change the management's mind about it. In short we came up with these points: Most of our colleagues write low standard code. They don't know enough JS and can't accept the helping hands from TS. Changing to an unknown lib in the company without TS will lead to even more bugs and bad code. Lowering these bare minimum standards won't help us in the long run. We should encourage TS and tests, and that will help us keep up with the versions. They understood and made me do lectures for my colleagues. I will present them this video next time!

[@uidotdev]

Hopefully it'll help!

[@joopie46614]

Typescript is quite buggy at times and prevents you doing a lot of convenient things the language was designed for. If you're not gonna use those features you might as well choose another language such as java

[@vanjazed7021]

@@joopie46614 which features? You always can opt out of type system with any/unknown if you don't want to bother defining some tricky very dynamic type or want to do it later.

[@mr.rabbit5642]

Juustt remember to make a note that if you're talking about TS - JS relationship, it's actually a transpiler than a compiler. The difference seems linguistic-only, tho it's an important thing to not forget about when writing code. For start, Compiler will warn you if your code does not make much sense andc(modern one) won't compile code with unreachable code. Transpiler will mostly only tell you about type errors and things it can't transpile to target language..

[@joopie46614]

@@mr.rabbit5642 typescript compiles to assembly...

[@wota_pov]

Meanwhile ts developer: whatever i’ll just use any

[@uidotdev]

😅

[@wcandillon]

I'm really enjoying these new series 🙌🏼

[@uidotdev]

Thank you! We're big fans of your RN content as well.

[@foreach1]

Didn’t wanted to change my mind in 2 years of JS programming. But the day I tried TS, I felt like I was idiot for not trying it before. Such a good layer on top of JS. And if like me you hate Java, it’s seems the same but your experience is a lot better

[@hundvd_7]

Java feels like a prison, you're forced to adhere to a very strict set of rules, and this also means that sometimes you will do everything do avoid doing X thing because you can't do it how you like it. JavaScript feels like you're alone in the world, with nothing to control you. You can do anything. But that also means you have no idea what to do, and even if you have a goal, you have no way to learn from anyone. TypeScript is the perfect mix between the two. It lets you do whatever you want, and it provides you the necessary crutches when you're in need of help, and can provide guidance about what you should be doing in the first place

[@fltfathin]

@@hundvd_7 the best thing about js and python's approach to typing is you use types by choice not by force

[@natashamane6502]

Excellent…

[@meceffeukada3767]

You hate Java bcuz you don't even code with Java.. otherwise it's the same thing with typescript

[@hundvd_7]

@@meceffeukada3767 Nah man, a lot of people (including me) tried Java and that's exactly why they hate it. Though I'll give 2 exceptions: - I worked with older versions (mainly 8, also 5 and 11), but that's all that's ever used. There's just no jobs with newer java projects - IntelliJ is the best piece of software ever written, and it works the best with Java. It's still the best option for every other language, but it's only like 80-90% as effective for TS or C#

[@er63438]

Thanks for the video. Appreciate it's conciseness, and not taking 15-30 minutes as most videos do nowadays.

[@uidotdev]

You're welcome. Glad you enjoyed it!

[@serhiicho]

Thanks for the video, I love it. Side note: 00:05:23 TypeScript is not a compiler, it's a transpiler, since it doesn't compile code to machine code, it compiles it to JavaScript

[@uidotdev]

I've found that that distinction usually just confuses more people than it helps, though you're technically correct. Thanks for watching!

[@jungervin8765]

Typescript is worth even for the code completion, and structuring your project, you always know what are the types or what members an object has. If your app big than these are huge benefits, not to mention the other many benefits TS has.

[@uidotdev]

Well said.

[@buttofthejoke]

i remember the times I used to get undefined for an object property and lose my mind, trying to track where it's getting overridden. This was during jQuery times when anything can update anything on any event. after a whole day or two, I'd realise it wasn't isSpellingCorrcet but isSpellingCorrect. Thanks to typescript, now none of that BS happens. I get suggestions from intellisense and I simply press tab. ❤️

[@ward7576]

What my beef with Typescript is the types that some vendors create that make no sense when reading the name and no sense when you take a look at the type declaration itself. Just made me wanna go back to loosely typed JS. Feeling much better now.

[@finnwestergren8670]

I go back and fourth on this. I trust MY types but not really everyone else's. I kinda think that as TS becomes the standard for public packages though this will happen less and less. Or people will at least make more open source efforts to correct any discrepancies between how the api truly works on the js level and what its types represent

[@riddixdan5572]

this and previous video remind me a lot of fireship. if this level of content keeps coming, I will keep on watching.

[@uidotdev]

Fireship is 🐐

[@aaronkoller8811]

Wow. This video combined with Imperative vs declarative are simply amazing. you explain things so concisely and simultaneously digestible that my brain can totally follow. That combined with the imagery and the well-timed glint of Oprah left me in stitches. More, more, MOAR!! These videos are great!

[@uidotdev]

Thank you!

[@YeOldeKamikaze]

First time I used TS by choice was for a sw architecture assignment back in uni. We had to implement the classic GoF design patterns using any language of our choosing. I wanted to apply the patterns in web apps. The thing is, some of the patterns make the most sense when dealing with user interactions (such as memento), so they had to be run in the browser, not server-side. I was still a newbie so it took me quite a while to realize that JS (including ES6) is not really an O.O. language, so it lacks many of the required constructs such as interfaces and abstract classes. Our professor was a pain in the ass to deal with. If your code didn't explicitly use O.O. constructs he would give you a bad grade for "not complying with requirements". I thought my project would be a lost cause, but then I read about TS and all the O.O. syntactic sugar. Once I got up to speed and figured out how to add typings to pre-existing JS libs (great code auto-completion in VSCode, btw), I could implement my project in about three days. I've been a TS fanboy ever since haha. So yeah, TS is not just "JS with types", it's so much more.

[@test-halfway]

Love it! Please keep on uploading this type of content.

[@uidotdev]

Thank you Robert!

[@satindersingh9671]

Always count on “empathetic friend” over any linter

[@chrcit]

I love your videos and the newsletter. Keep em going!

[@uidotdev]

Thank you ❤

[@sc76399]

So true, I love typescript for the extra documentation and error checking. If you define a function decloration or even parameters then decide to change them, typescript will tell you where in the code your old usage of a function doesn't match its new decloration.

[@SylvainPOLLETVILLARD]

Will TypeScript age well though ? As you explained, JS already catched up with modules and classes, but in the future, JS new features may conflict with what TS proposes, like the private class fields proposal (stage 4) vs the private modifier in TS. The promise of TS being just a layer over JS may be more and more challenging to keep with time. The two outcomes I see are either, breaking changes and deprecations on TS new versions, or a split from JS evolution trajectory at one point.

[@meanmole3212]

I suppose the compilation process from TS to JS can be adjusted to do anything in theory. There's already some inconsistencies with things like the readonly modifier which does not enforce prototype fields to be immutable on the compiled JS code despite being "readonly" on the TS side.

[@azmo_]

Valid point, hoped me experts would comment on this (I'm a newbie)

[@peterdelf]

I started with Basic, C, and then Java at university. When I first started to use JavaScript I hated it. What I realise now is that I actually hated the LEGACY of JavaScript. Modern JavaScript is infinitely better than it's origins. Typescript is just the future of JavaScript.

[@uidotdev]

Agree

[@sleepy_femboy0]

I used to not like JavaScript but after learning TypeScript, it has becomes one of my favorite programming languages.

[@cyberneticbutterfly8506]

I still don't get how to think in javascript, it's like reading the first pharagraph of a book 30 times and still not remembering a word of what I read.

[@sleepy_femboy0]

@@cyberneticbutterfly8506 I found using a debugger helps as you can see the data that's in the stack

[@kanjakan]

@@cyberneticbutterfly8506 I had found that the answer is to just use TypeScript and forget that regular JS exists.

[@antibioticaddict]

TypeScript devs really surprised by 20-year-old compiler technology

[@uidotdev]

JavaScript is a compiled language, just at a different time.

[@muhammadahmedjaved7691]

awesome man your videos are really really high quality I love your videos these are better than many paid out there thanks

[@imhassane]

I remember when typescript just came out, crazy how time flies

[@dripdrops3310]

May this channel blow up.

[@pablorepetto7804]

What I'm hearing is that if types aren't enough by themselves to make me adopt a new tool, I can ignore TypeScript.

[@ivangrey1047]

Ever since I tried typescript, I never came back to writing vanilla javascript

[@uidotdev]

That's fairly common I think.

[@jaydenmoon1165]

Wow you did an amazing job covering this topic - I would love to see more videos on the history of languages

[@uidotdev]

Thank you!

[@n00dle_king]

I work in a massive code base that's being slowly converted from .js to .ts, and every time I change a file over to typescript tons of latent bugs jump out at me from VS. I despise working in our .js files and can't wait for the day when they are all gone.

[@uidotdev]

Right. I think most of the haters in this comments haven't had that experience.

[@Sisufyable]

So, this was more of a 'what is typescript', than 'the story of'. I hoped for the actual history, and how it succeeded against Facebook's Flow.

[@meepinandmorpin]

TypeScript is my baby mama AND my wife; that's how loyal I am.

[@uidotdev]

Dedication.

[@ze_chooch]

I’m a developer who started learning, without a technical background, in March 2020. Because of this, I’ve missed out on the context surrounding tools that my team uses, like TypeScript, which has caused some problems for me. This video really helped me build a relationship with the “why” of TS, which is influencing my relationship with the “how” of TS. Thank you. Subbed. Edit: maybe GraphQL/ApolloGQL at some point?

[@uidotdev]

I built this video for people with your background. So glad you enjoyed it. Definitely lots more to come.

[@ze_chooch]

@@uidotdev thank you!

[@WesBos]

lol damn, I'm impressed you found that tweet from 2010

[@uidotdev]

No idea why, but I love finding old stuff like this. For example, here's Chris Coyier from 2007 when he was in an Irish band - kzbin.info/www/bejne/b3i4c4Spa7iaiqc

[@AndrewBabin]

Angular 2, man... Deciding to learn it was one of the best choices I've ever made. I had just learned v1 when v2 came out, completely different, rebuilt in Typescript. Totally wasted my time learning v1, but I never would've been such an early adopter of TS otherwise. Thank goodness. Funnily enough, Google wouldn't have adopted it if they hadn't thrown in decorator support. It's stuck in "experimental" purgatory to this day because the ES decorator proposals have been taking FOREVER and are still only stage 2.

[@uidotdev]

A fun experiment to think where TS would be without Angular. Definitely not where it is today.

[@IngwiePhoenix_nb]

"Type annotations remove the guesswork." C++ auto: *Bonjour*

[@MiniArts159]

Long story short: embrace extend extinguish.

[@agontprevarator5214]

I'm wary of anything microsoft

[@hassaniyouness8024]

Loved this video hope to see more videos like this

[@uidotdev]

Lots more to come!

[@patcoston]

JavaScript will eventually be written in JavaScript

[@uidotdev]

Galaxy Brain.

[@schoolmonkey13]

TypeScript seems kind of like what's happening with Python's type hints, except in that case it's happening in the main language. Gradual addition of typing to retain the benefits of dynamic languages while getting most of the security of typed languages.

[@NateLevin]

Reminds me of Fireship in all the right ways. Do note that the thumbnail has the word "won" cut off due to youtube showing the time in the bottom right!

[@uidotdev]

Fireship is the 🐐

[@lukehatcher98]

Great video. Glad this was recommend to me. Subscribed!

[@uidotdev]

Thanks so much. Welcome!

[@MrBowmanXD]

Pretty good video. Might be working with typescript in a future job so it's good to know some history

[@uidotdev]

Glad you enjoyed it!

[@Javatician]

You dont need typescript.

[@uidotdev]

You don't NEED 10 fingers either.

[@vegiimite]

The video missed the feature of TS that adds improve your confidence in the code the most. Null / undefined checks

[@GmailNexus]

Awesome Video. Like the style.

[@uidotdev]

Glad you enjoyed it!

[@TeluguFactsTV]

I loved this series 🤩

[@uidotdev]

Thank you!

[@thepetesmith]

Dojo was awesome. Learned everything from it

[@shfunky]

Really enjoyed that! Awesome content! :)

[@uidotdev]

Thank you Adam!

[@finnwestergren8670]

Great video! I was kinda hoping for a historical explanation of why other frameworks like flow and react's PropTypes eventually fell out of fashion

[@aloufin]

yeah same here, I watched this video a few days ago then was trying to remember why TS won... i went back to the video and realised it never actually said anything about beating out its competition of Flow etc...

[@huxnwebdev]

From now on ill call Kent C Dodds as Developer Tool lols 🖖 BTW Really Awesome Video 💖

[@uidotdev]

🐐

[@hobbyxplorer]

i use to hate typescript but im getting the hang of it. it is relaxing to use once u know the types and the syntax. its like free code.

[@mightycatniss]

I love typescript, almost know it for about 80% now, it’s vast as fuck alone (types, guards, interfaces, bindings, conditional types, overloading, decorators, tsconfig and all its options, using get/set in objects, readonly, static, expanding, inheritance …) and even more when you add utilities libraries such as rxjs, events, etc… but next step is clearly rust for server side and maybe even browser side thanks to webassembly.

[@uidotdev]

Agree

[@ko-Daegu]

coming from Java I feel like this is just the norm thank you typescript cuz JS really sucks

[@uidotdev]

@@ko-Daegu 😂

[@raconvid6521]

I didnt know that ts isnt just types. Thank you so much,

[@lasindunuwanga5292]

I love this video. I love TS from the beginning. I just love the way you explain the importance of type safety. Because some people are so lazy and hate to work with types. They write some code and quite. If people want to write correct piece of code, I believe that having a type in front of your variables is compulsory. Because that means, you know what you are doing...

[@uidotdev]

Great points! Glad you enjoyed the video.

[@MeonisRP]

You explain things EXCELLENT! I really wait for GraphQL video as I don't really understand what it stands for

[@uidotdev]

Thank you!

[@taquocviet]

Let's not forget Angular for popularizing TS.

[@uidotdev]

Very true!

[@lorenzodossi]

Those videos are awesome

[@uidotdev]

Thank you Lorenzo!

[@hanro50]

The reason I like JS, and to an extension TS, is that dynamic component. Being able to define data structures on the fly in runtime. Since tbh...I want to be able to define a function as "it returns x, but with y added into it" and... trying to do that in Java broke me...

[@uidotdev]

I agree it is convenient.

[@herrbasan]

There must be something about JS that is just better suited for the current needs, otherwise it wouldn't be that successful. But maybe it's just the fact that it comes with this super flexible but fast rendering engine, and it has actually nothing to do with JS.

[@hanro50]

@@herrbasan Isn't native code...like idk...GTK, Windows forms and QT a lot faster and less resource intensive then Blink, Gecko, Trident or Webcore? Almost like the rendering engine plays a minimal part in all this considering the diversity of implementations available...even the underlying JavaScript engines have changed drastically over the last several decades with V8 only really coming into the limelight in the last decade or so.

[@gabiold]

@@hanro50 I think it is exactly the rendering engine what made JS popular. Currently the web frontend is one of the simplest (if not the only) way to do cross-platform app development. No installation, works on Mac, Linux, Windows, Android, iOS, almost out of the box. Quite standardized, hot, up-to-date. Since JS is the only language in browser, it's learning curve is easy in the begining it's not a surprise that is so widespread. It is similar to VBA in Office. It is used widely, not because it is that pleasant to use (neither the lang nor the IDE), but because that's the only choice.

[@hanro50]

@@gabiold Ye...but you have to remember that rendering engine is still different depending on the browser family a set browser belongs to. I can easily write code that'll look perfect in chrome, but will break in Firefox or WebKit. Yet 99% of the backend JS code will be more or less exactly the same between all three browsers. With the only breakage typically being attributed to a missing feature...

[@anuraghazra4772]

Nicely summed up! Great video.

[@uidotdev]

Thanks Anurag!

[@akin242002]

Typescript is the hero Javascript needed.

[@uidotdev]

Thanks for watching!

[@HKRazieL]

i loved the part where you said that "dynamic languages like JS break down IF YOU'RE NOT CAREFUL"... most people don't understand the fact that there is no problem with JS if you're not bad... the problem starts when you have many people, a lot of whom are bad, and you have to coordinate with them how things should be... then TS makes things easier

[@igorswies5913]

not careful != bad

[@uidotdev]

Well said.

[@gallergur]

I disagree. A programming language (or any other system for that matter) is well designed if it makes it easy to do the right thing (and optionally hard to do the wrong thing). Just because you *can* write good code with JS, doesn't mean it is *easier* to do that, compared to other languages. In fact, your argument support that. When enforcing stricter rules, even bad programmers tend to mess up less. I argue that good programmers, too, are better off not having to do in their heads all the checks that C#'s compiler, for example, can do for them automatically. And tbh, "if you're not careful", in this case, is most of time. Your team will probably have bad programmers. Or stressed programmers. Or lazy programmers. Or tired programmers. And they *will* take the easy way. Let's, make the easy way the correct one.

[@HKRazieL]

@@gallergur then we have to delve very deep into the philosophy of what is considered "the right thing" for some people "the right thing" a dynamic language should let you do easy is "everything" and for some people being able to do everything is bad because it leads to more mistakes by people who don't know what they are doing... mostly by people who can't bother actually learning the language and how it works... having stricter rules MIGHT lead to less mistakes, i never claimed otherwise, but JS is not bad because someone who doesn't know how to used made a mistake with it...

[@gallergur]

@@HKRazieL So you're claiming you never make mistakes? Static typing helps you, at the very least, catch some mistakes before you even save your file (let alone deploy it to production). But it is often more than that. Type systems allow you to express designs and structure using language constructs, and that is useful for communicating the design to your colleagues, your future self, AND the type checker (that can check that *your* design is used as intended, not just the language's). "The right thing" is a very subjective phrase. However, "everything" does include a lot of things that you and I can probably agree are bad. So allowing "everything" (or to be more exact: not making it harder to do certain things) is not better. Exactly what are those things is debatable. But having the ability to express these rules as executable and verifiable code is a very useful tool.

[@RobertKing]

Angular were ahead of their time adopting TS and RXjs. Starting to pay major dividends. I switched back to angular from react recently and not going back to react.

[@ApolloSevan]

Im kinda bummed that you didn't bring up the war between Flow and TS. I always found that interesting.

[@uidotdev]

Revisionists history. Didn't feel appropriate for the video, but I could see where that could be wrong.

[@trafficface]

Trip down memory lane 😭

[@uidotdev]

Another data point that we are indeed old.

[@trafficface]

@@uidotdev hey it's okay, we could be older, that's what I tell myself but each year that gets increasingly more thin

[@josemiguelochoa5372]

man first time on your channel. Really good content. Keep it up!

[@uidotdev]

Thank you so much! ❤️

[@jsonisbored]

Enjoyed the video, I assumed it would've had way more views

[@uidotdev]

We'll get there.

[@ankk98]

The videos that you referenced indicates that you are one of the enthusiasts.

[@alfred1243]

Sadly, people forget that tools like TS, Docker, Kubernetes created to solve large scale problems and driven by hype deploy them everywhere often adding unnecessary complexity

[@rice8864]

uh huh

[@ajricherson1099]

I don't see much cost in using TS. it is more annoying to debug JS and track down type errors then just using TS

[@d.sherman8563]

The cost of typescript is trivial compared to the benefits it brings, in anything more complex than hello world is worth it imo.

[@emanuellamba5828]

So basically MS didn't want ES4 update so they can create TS which implemented what ES4 was supposed to add to JS...

[@JLarky]

BTW in 2010 we thought that every computer in the world is going to have JVM on it. In 2022 it seems like every computer has V8 which is a sense JavaScript virtual machine :)

[@uidotdev]

Very true

[@ronaldgipa8731]

and smartphones

[@Apoasdf123]

I feel like people here praising typescript never used any static typed language.

[@uidotdev]

it's OK for people to like things.

[@bakhtiyor_sulaymonov]

Thanks 👍 for this quality content

[@uidotdev]

You're welcome!

[@Joso997]

Typescript is child of Javascript and C#

[@RickyGarcia_Learning]

Tyler still pullin thru!

[@uidotdev]

I've been out of the game for too long. Still got it though (I hope). Hope you're doing well!

[@petarkolev6928]

Thank you for the wonderful video 🍻

[@uidotdev]

You're welcome. Glad you liked it.

[@srikantam4796]

Such a compact and informative video! You deserve more subs :)

[@uidotdev]

Thank you! ❤

[@FatherPhi]

Typescript has allowed me to work remote with no degree 😭

[@uidotdev]

🙏

[@JoonhwanLee]

Stroy of {my favorite KZbinrs}

[@uidotdev]

❤️

[@headwayio]

Thanks for featuring Kelsey's tutorial at the 00:06 mark! 🤗

[@uidotdev]

You're welcome! Kelsey is great.

[@mskleftwich]

Thanks so much, y'all! 💗

[@Mohit-gb9dv]

Typescript is only on KZbin not on production 😂😂

[@JACOBTL23]

Awesome video

[@uidotdev]

Thank you!

[@KyleHarrisonRedacted]

Excellent video, thank you for this

[@uidotdev]

You're very welcome. Glad you enjoyed it!

[@introspecticon]

Super disappointed that the book cover shown at 2:52 isn't real

[@uidotdev]

Be the change you want to see!

I have tried both JS and TS and there is no absolut truth. Each case is a case and their usage should be evaluated first. Sad to read some comments saying: "I switched to TS because it is easy to spot typos and blah blah". It just shows you are doing something wrong or have never heard about linters.

[@uidotdev]

I'd argue linting is a very small part of what TS is good for.

@@uidotdev Indeed. That's my point.

[@IgnoreSolutions]

As a C# dev, i love typescript

[@uidotdev]

And hate JavaScript, I assume lol

[@IgnoreSolutions]

@@uidotdev Absolutely. But it does still have a place and is useful *when used in the correct context*!

[@uidotdev]

@@IgnoreSolutions That comment is way too rational for KZbin.

[@Official_R_deep]

Good work

[@uidotdev]

Thank you!

[@josh-rb7he]

thanks for this video!

[@uidotdev]

You're very welcome!

[@nathanfranck5822]

I found typescript helped me write less stupid, more readable javascript - you don't need to adopt special libraries for data protection like immutablejs, just use readonly arrays/members. You don't need giant 10 argument function signatures, just accept an object with certain fields. Even the most vanilla es3 javascript looking code is made better when your confidant users of your code can't mess it up.

[@toyotayaris9038]

so basically gives u everything u get in c# and visual studio but in javascript?

[@fatihersoy7559]

you are great

[@uidotdev]

Thank you!

[@sle6423]

I'm surprised no one ever talks about tradeoffs with TS (e.g. governance). I'm a fan on many fronts, but the lack of balanced opinions on it troubles me.

[@jemesmemes9026]

Would you be able to form your own counter argument for it? I’m also a fan of it and haven’t seen any big issues with governance (as far as I’m aware)

[@a.c.vermillion]

what's the problem with governance?

[@sle6423]

AFAIK it's only certain people at Microsoft who ultimately control the direction of TS, unlike the evolution of web standards for example. This in and of itself isn't a strictly bad thing, it's just something to be aware of IMO (I'm reminded of it every time I come across an issue thread with hundreds or thousands of comments only to be closed at the end by someone like Ryan Cavanaugh, just for an example) And I doubt I personally could make a case for any project almost guaranteed to scale in size and contributors where the tradeoffs are too great on the whole in favor of TS afaik, I'm just surprised I never see anyone else doing so at all.

[@SelfMadeSystem]

I think TS has one of the best type systems of any language. Its "interface"s and string types (?) are actually the best.

[@LexRudera]

It's easy to say you won when you are sitting in your own reaffirming bubble

[@chrisgraham2123]

Amazing video!!!

[@uidotdev]

Glad you enjoyed it!

[@andreas_tech]

yo man, do you have anything to do with slightly sociable? your expression/speed is great, and makes your vid very interesting to watch.

[@uidotdev]

Haven't heard of them until now. After watching a few videos, very similar energy.

[@indycinema]

This video is fucking awesome

[@uidotdev]

🌹 Thank you!

[@emiliobarrera8229]

The day browsers natively understand typescript will be glorious

[@uidotdev]

I think the anti types crowd would rebel if types ever got added to Ecmascript. We'll see though!

[@emiliobarrera8229]

@@uidotdev I mean any valid js code is valid ts code, isn't it? They could keep doing their normal businesses as we move forward onto a more secure way of writing

[@diegobraga3745]

I can't get back to Javascript

[@nixoncode]

oh how the times have changed

[@adeceptikon]

Million of years ago nobody would have guessed that apes would dominate earth. So is the case for programming languages apparently.

[@uidotdev]

🤔