Also, having experience with typescript's static typing helps you a lot when you go to other languages, such as Go or Rust.

I've forever stayed away from typescript and not because I don't love writing type safe coding but because I just never felt the need to replace the plain old JS which works perfectly fine in most cases. However last year, I'd a chance to work on a Sveltekit project where I chose to use Typescript and boy does it help. It not only speed up the development time but also helps to debug more clearly and confidently build for production ready apps. Now I'm translating my old node js project to Typescript and seriously I see no reason to ever go back to JS.

I just started learning typescript and you released this video at the perfect time, thanks!

We need the new tutorials to come with typescript by default

What I also love about TypeScript and any stricter language, is that you are sure on what the function is receiving and returning. This is basically the best documentation you can get, without even writing a documentation. However, I wish they would add a throws keyword like in Java, where you can or have to declare all Errors thrown inside the function, making it much clearer how to handle errors for that specific function without the need of further documentation

I in particular like that you need to specify what your objects look like with types/interfaces. After doing that, you will get autocompletion which just helps. And it also makes you avoid null pointers.

Well put together video, and the only one I've seen from yourself, but it might be good to cover some downsides in an impartial way if you haven't already. Every technology has its pros and cons, Typescript included 🙂 I can think of a number of occasions where Typescript has cost many hours of time that works have been unnecessary in pure JS. Possibly that time has been compensated for due to reduced bugs, it's hard to know. Issues I've hit: - TypeScript compiler is really slow which costs hours of time waiting locally & in CI - Types being wrong 😢 - Conflicting type definitions - Transpiler bugs - Nested generics & error messages (common with libraries) can get really complex vs just reading docs - Some libraries omit docs thinking types are enough (often not the case)

Great tips to start exploring typescript.

Thanks Kyle! 👍

You can also get autocompletion with jsdoc, if you have a small project and don't want to use typescript but want to profit from the typescript engine you can use jsdocs instead. you can even generate type files (.d.ts) from a js file that has jsdoc with typescript

Nullish coalescing is the double ?? The ?. Is optional chaining.

I love that I can rename a property, and it automatically updates everywhere that's referenced.. ❤ thanks to typescript.

Kyle you just convinced me to reconsider TypeScript as beneficial. I had no idea there was that level of flexibility, I thought it had to be more rigid and universally applied.

Thanks!

I started programming with C++ on the Half-Life SDK back in high school (yes, I'm old). I know very well the benefits of a strongly typed language, or just static typing in general. TypeScript is obvious to me, and I would go so far as to suggest ECMAScript become a statically typed language in further iterations. I'm learning to use TypeScript right now, and it's very intuitive. Of all companies, Microsoft pushed for this, and I have to give the devil his due.

Congrats on your new home!

Can you make a video on how to manage concurrent requests and limit number of requests and wait until the previous request is complete then start the next request.

I been avoiding TypeScript then seen that made this video when I decide to take it srsly, amazing timing lol!

You should make a video about how to use d.ts in TypeScript

I think it TS helps a lot when u are new to the project, or it's been awhile since u code on that project, seriously how would I know what properties does this object has after few months of not coding, I have to dig through all the code to find out, that's slowing me down, TS also helps with refactoring code, especially renaming property names, it just give u the confidence that the app will run

👋 Hey Kyle, Do you know how to make some props optional in TypeScript? For Example, if I have an error prop, and I want to enable or make it required when I have another prop, it should give an error I haven't passed it else, not an error? I strongly need this mechanism... P.S. I am a newbie in Typescript, but very strong in ReactJS..

thanks brother

hmmmm, i was wondering if i should give it a try, i've been on my journey to become a web dev for 1 year now, and i'm using react / next / tailwind css with firebase pretty efficiently, i think i will try typescript for my next project and make a ticket management to add to my portfolio :D

3:48 optional chaining not nullish coalescing. A good way to remember the difference is chaining always refers to objects and the dot syntax. Just like .then() chaining.

Would you do a full stack app with Nextjs, Prisma and Trpc. Thanks

Very usefull tipps for TS

It looks awesome.

may i migrate for typescript so?

Hey really cool Video! im currently learning angular and typescript(im a beginner coder just finished learning js) and i question myself for what case i should use the "?" like in your button?.addEventlistener codeline. Like if i want to reference to a button i know that it exist right? In which case it should not exist? Why should i ever say that something can be null if i never want to code something that can be null? This concept is a bit confusing to me. Also why should u use queryselector instead of using id + document.getElementById since a page/application will most likely have more then 1 button( i think queryselector just pick the first element, dont know if im right)

Huge TS fan here... You should try co-pilot, it's crazy good (often).

Can i use javascript to connect to a localhost database using Wampserver?

at 3:49 is that nullish coalescing or optional chaining ?

My experience with typescript slowing me down has been in dealing with libraries and cumbersome verbose typescript stack traces, but i guess those simple cases bother people too. That’s not been my issues though.

Exactly I use TS even in the most miniscule of projects

This is a very good video, actually I use typescript almost only in scenarios you covered. My biggest problem with TS is that people tend to abuse it, i.e. they think TS is a good thing and thus try to use it everywhere, and that just causes more problems than good. Most of the times you should rely on TS’ inference feature instead of hand coding the types on every line of the code. Adding types is only helpful in scenarios like passing args to a function as there is a context switching and thus is usually more prone to type errors. In other scenarios the types should be self-evident, and thus adding types notations is just unnecessary work and creating visual noise. So in these cases if you have to rely on types it means you probably have bad code and you should try to fix the code itself.

typescript is an invaluable tool when it comes to major refactors, I just had to delete half of a code base and as soon as typescript was happy everything just worked out the box

The problem with TypeScript is the amount of errors i'm getting that i'm not understanding. With JavaScript it's fairly easy to debug an error. With TypeScript i don't have a clue what is wrong. I feel like the learning curve with TypeScript is higher than anything i've done before.

Can you put the code where you are showing this repo i wanna read this whole code

Great video. Why you dont use Nextjs. Thanks

watching his folders, while i barely have public and src folders in projects. im crying

Totally agree, always prefer to use TS over JS when possible

I see a lot of Typescript developers do Type Driven Development I do Test Driven Development It is about to think first about the input and output. You can do it with tests but also with the types. Writing first code and then tests or types will result in bad code. It is a mindset, not specific Typescript. (Type Driven Development can also with JSDoc with type check with Eslint)

this would deserve a heroic viking song meme for the typescript galaxy

i also think that blinking only your left eye makes you save time, hahahah, love you

I’m using JavaScript in a .js file. I haven’t used typescript, .ts, or .jsx file. At first I was getting null values all the time. I did read about the “?” and it worked in some possibly null places. It bothered me, and I wasn’t even seeing this problem in tutorials teaching JavaScript. I did find a setting that I turned off that fixed it for me. My question though is, why was I reviving this error if I wasn’t using typescript?

The main reason to learn TypeScript is that you wont get a job if you don't learn it. The more you tell everyone how much you love it the more likely you are to make money.

That anonymous function to check input types is so related, I do it all the time coz I can't remember their name. And you shouldn't have to when using typescript, just copy and get everything from the editor, be more specific about your code.

Hey, Kyle. Is there any course made by you on Angular...?

Excellent video. Please create more React in-depth videos for beginner to intermediate devs.

Sorry but I'm going crazy with typescript at the moment. Trough some es lint to the mix and use the basic recommended things and suddenly you are fighting with so many errors that are coming from libs because all using different es lint implementations for their types. Some do undefined or null. What grinds my gears the most is that I now i have a value in an object but still getting errors event with checking for type safty.

hey kyle any thoughts on posting a TS in 30 mins course? would be great, greetings crack

Is there any way to contact you for a question? :)

Define what must be defined, infer what can be inferred, and prune bugs which could have been type-checked. 🐸

I’ve been holding out learning TS because I’ve only been studying software development for 2 years and it’s never seemed like a priority. I’ve focused on HTML CSS JavaScript Python Flask React SQL etc and I feel like I should really lock those down before I move on to something that can almost be considered “redundant”…I’ll get to it, though…someday

It's time to the join the TypeScript side of the force. Declare those numbers and your journey towards the TypeScript side will be complete

Complaining that you have to create your types is like complaining that you have to plan bevore coding. If you have planned your app, you already have written somewhere which variables you have, what data structures you send febe, so there is very little overhead.

Please come with Angular

things get slower when you are newish to typescript and you have type error... I am on my first typescript project and when on react I try to place onCLick on a div, just for example... I just gave up on that and use ignore :). But in general typescript is way better even only for autocomplete.

Bro can u please post a mini portfolio project in MERN 😊

Every night I pray to the Gods that I will never have to work without TS again.

hmmm, let me add a new language that needs to be compiled into JS (adds time), to overcome VS Code short comings. Type safety is over rated for something like JS. All you need to do is expect certain types. If it's an HTML attribute, you expect a string. If it's your own variable, you expect undefined or null. It's not that hard. I often use null or 0 to have the same meaning, so it can be useful to know when something is not as you expected. Real type safe languages provide an "actual performance boost" for using them. Take Assembly Script, which is similar to TypeScript, but designed to make WASM files. If you go this route, you get a 30%+ performance boost for using static types. Want more speed, there are other type safe languages like Rust. Plain old TypeScript is only semantic.

The reasons I still don't use typescript are: 1. Sometimes libraries has no support for typescript (nodejs) and i can't find a clear guide where they explain how to create on my own for that library. I mean, there are... But they just explain how to place "any" everywhere or they just say "write this to make it works" ...i want to understand what i do! 2. Can't find a resource where i can learn typescript with RTK, RTKQuery, React hooks forms and redux saga. Every guide has just plain functional component with basic types ... As soon as i will learn how to do that, i will switch to typescript for sure

The time you're going to spend defining types and stuff like this will take more time than Normal JavaScript, but .... the time you will spend when falling into bugs and spending hours to solve them is going to be saved by TypeScript. TypeScript wins.

Love from India

yes you need to compensate for all the boilerplate you need to write, so you need to be faster... a real hell is mixed app that you need migrate to ts - that thing has special place in hell

I can have the same behavior while using JS and JSDoc. Plus, I do not need to compile the code. Collegue of me always try to convince me to use TypeScript, but I (personally) see no reason to „change“.

please use semicolons tho. Either by putting them manually or using alt-shift-f.

I can’t see any reasonable reason to use js instead of ts

even with small stuff like i m writing small browser extensions for myself typescript helps because i dont need to go check what code does what tbh at this point why would you even use js without ts in 2023

TS is a blessing

you know whats slower? creating app in JS and theeeen move to TS because you decide halfway that you lack type safety.

the fact that you didn't mention anything about the compiler

All fun and great until you try to compile a service worker written in TypeScript to be in the root after compilation.

I'm afraid to start learning typescript

Since most employers know typescript help detect faults in code . Most employers will want there employees to know it

Autcomplete isn't a good feature because it allows people to write code when they do not understand the fundamentals of what they are doing. Then when things break they won't know how to fix it.

you can either write types or spend 3 days debugging them

you could just use JSDoc types.

I don't use auto-complete or vscode so this video is lost on me :(

Write More or Fix Bugs More

Coming from Swift this is a million times more readable

I don't even use auto complete. Auto complete annoys me. And honestly I really don't care how fast I am typing. I don't think coding is about typing fast. Actually I think typing fast is a way to produce bad code. Typing is what? 10% of coding? 20% max. Most of the work is done in your head. Also, the fact TS is adding that "?" to check if that button exists or not is just not acceptable. If I need to check for something I can do it myself. And if it does not need to be check then I don't want it to be checked. So.. still not convinced. All I see is TS could save me from errors that almost never happens. Type errors? Once a month? Fixed in a few seconds. Variables names error? Makes me waste 2 minutes a week? I love types, in Kotlin for example, but I love simplicity a lot more. I will use types when JS will implement them natively.

Web Dev Simplified: TypeScript Makes You A Faster Developer Also Web Dev Simplified: Is Learning TypeScript A Waste Of Time?

when it comes to coding for work, TS faaaaar exceeds JS, do you want silly errors in prod, do you not want readable, scalable and maintainable code at work,.

Save time, write "any" everywhere. 😅😉

I've been working with C# for years, when I tried web development for the first time, JavaScript felt so weird and felt like it is a mess that leads to many bugs and mistakes that you will spend hours finding why, but anyway as experience developer it didn't cause me problems maybe because I already learned to not make mistakes with C# since it is not dynamic type language .. for people like me, TS is a good solution, but still it I would recommend it for beginners, but for advance devs for me at least I don't see the need.

i dont even write my own functions i write code first then extract the function so i get types for free.

Finally realized?

Create a video about GPT-4. I believe this bot has the potential to replace many jobs as it is claimed to be 500 times better than GPT-3. Tonight, there is a live show demonstrating the power of GPT-4. They are going to create a website on paper and send it to GPT-4, which will turn it into code. I think this is really cool😢

Ok its funny he gaves Typescript the point with the faster autocomplete, for sure typescript has a nice LS/LSP and thats makes typescript usable. But the example shows that VScode is a Code editor not an IDE. With WebStorm, Phpstorm and other full IDEs this problem doesn't exist. My way to go is normally when i need typesafty and i mean runtime typesafty then i use not typescript or JavaScript but if i want a easier workflow in my js projects i use JSdocs. JSdocs can be used out of the box with the most IDEs and you can generate a Documantion out of it. TypeScript is a nice language but i think its overhyped

Someone told me that the exclamation mark was a code smell, but there are situations where a null check is completely unnecessary. Edit: I'm wrong. It's a code smell. Do your null checks. Be safe. It takes two seconds.

You are a great developer and teacher but please stop putting controversial titles on videos

Typescript is too slow relative to javascript. also it's a misery to find out what html tag is belong to what type many times especially when you wrote react or next.js with it. I know it's fundamentals very well but i don't like it and i never write it if i don't must it for work on a job. I understand why they want to define a type from us to strings, booleans, numbers, objects etc but in html tags or other things is very annoying to find out and also typescript docs are awful to describe that things.

The first viewer 😂

When u go Ts u never go back 😂

I’m going to have to read more about adding an exclamation to remove the null because I’m sure as hell my team lead might not approve of that pattern

Or you can just define everything as any. I tigered the entire TS community. :p

The bad side of Typescript is when you know it you start to hate JavaScript 🙄

TypeScript & Testing makes you a faster developer. To ship a real product. Two months down the line you will be much faster compared to your crappy untyped and untested javascript code.

Not using typescript is like typing English with spell check, grammar check, and auto complete disabled. That's definitely slower. Learn typescript and you'll have powerful tools at your disposal to help you make programs quicker.