I wrote an app in JavaScript, released it, then for the second release ported it to TypeScript. My experience was that I preferred TypeScript. The better intelli-sense made coding faster when using objects and it definitely prevented mistakes. One simple mistake anybody who has written JavaScript has made is an accidental casing typo. For example, if an object variable name is mySharona, and you accidentally typed mySHarona. JavaScript allows this and treats the two as separate variables on the object since it is case-sensitive. This leads to defects as most places expect the correct spelling except for the place you made the mistake. This kind of stuff is even hard to catch in code-reviews. For this reason alone, TypeScript is superior. It catches stupid mistakes. This was glossed over in the video as the error category of static type checking.
The entire classical languages just want to discredit Js but it's not possible... because Java could not succeed over Js, they introduced typescript and call it superset of Js.... when complexity is introduced in design at the detriment of flexibility, it destroys the whole essence... FLEXIBILITY is FREEDOM, it is the SELF WILL on which Designers thrive....
typescript try to control free style coding of developers. Typescript owned by microsoft that's why they are promoting it more. Always prefer Javascript for freedom of coding.
Readable is debatable. Your codes readability isn't going to falter cause of TS, it'll depend on how you write code in general. As for being lazy, well... That's a poor excuse.
typescript seems a bit better to me. I personally like the ability to assign parameters and variables types so that i can easily keep track of what they are, and in the one or two cases where i need an arbitrary variable, i still have the freedom to do so. It's so much easier to read code when it tells you what things are instead of making you guess.
What is Typescript? Typescript is Microsoft's last resort in controlling and setting the standard for the internet since their epic failure with IE. TypeScript will restrict your freedom in determining the model of your program. Because, some people think it's a good idea to prefer strict rules over freedom in programming the web. And, duh...why do it the easy way when you can do it in a more complicated and sophisticated way with style? But, because these things become a thing ... and it can pay the bill quite nicely, I guess I’ll jump into the bandwagon too. Yippie!
Restrict functions in only accepting the argument types they are intended to take?... What a wild concept. Easy way is the lazy way, and likely the way that will end up just having holes in the code that shouldn't have even been in the commit in the first place. Yeesh.
"some people think it's a good idea to prefer strict rules over freedom in programming the web" Because freedom often leads to more bugs and poor structure. 5 million line projects can be written in Python because of it's strong typing. I can't imagine a 5 million line project written in Javascript.
its because developer nerds ALWAYS go crazy for new software/language/tools, they foam at the mouth. But honestly.... we need to just keep it simple! Everyone wants their own tools/language to be mainstream. And us nerds get high off new stuff. In the End..... its ONLY about the final product. I myself don't care about fancy backend stuff, I just want the final product good.
Most likely the newer Typescript compiler is less optimized at this point in time. ( and having the compiler check data types may catch errors not caught in Javascript )
Speeding up development time is always more about catching and identifying bugs and correcting mistakes; ergo, the quicker you can catch them, the better. Typing is the least time-consuming part of development. 90% of software development is a mix of brainstorming the optimal attack approach to a problem and detective work to search for what is broken.
@@olumideolaleye1834 This reminds me of the old battle between C vs C++, where a large project in C could have far more bugs than C++. ( there's reason why most graphical engines are written in C++ )
idk but for ts me it looks better or I have no idea what im talking about because im only programming in C# and C++. I would be very grateful for some advice and guidance.
@@laughtale1181 try to learn html, css and javascript as a fundamental base and then move to some frontend framework, e.g. React. Maybe try to do some research in job positions in Your country to see, what is the most common FE framework required in job position and go with that.
TypeScript or JavaScript - choose what’s better for your purposes! What are the key differences that make your choice? 🤔
This video sold me on Javascript.
Yeah I’m here to choose as well
Lmfao same. I'll stick with JS
Hahaha
I wrote an app in JavaScript, released it, then for the second release ported it to TypeScript. My experience was that I preferred TypeScript. The better intelli-sense made coding faster when using objects and it definitely prevented mistakes. One simple mistake anybody who has written JavaScript has made is an accidental casing typo. For example, if an object variable name is mySharona, and you accidentally typed mySHarona. JavaScript allows this and treats the two as separate variables on the object since it is case-sensitive. This leads to defects as most places expect the correct spelling except for the place you made the mistake. This kind of stuff is even hard to catch in code-reviews.
For this reason alone, TypeScript is superior. It catches stupid mistakes.
This was glossed over in the video as the error category of static type checking.
what about a spell checker plug-in
‘use strict’
just use eslint dude. you can do the same thing without adding an unnecessary dependency.
Video says in short:
JS is less compilation time with less project size and you should use TS.
HAHAHHAAHHAAHHAHAHAH
😆
The entire classical languages just want to discredit Js but it's not possible... because Java could not succeed over Js, they introduced typescript and call it superset of Js.... when complexity is introduced in design at the detriment of flexibility, it destroys the whole essence... FLEXIBILITY is FREEDOM, it is the SELF WILL on which Designers thrive....
Typescript = JavaScript + Java
typescript try to control free style coding of developers. Typescript owned by microsoft that's why they are promoting it more. Always prefer Javascript for freedom of coding.
Typescript reminds me of Java. So much boilerplate and unreadable code just for benefits which esLint can provide to Javascript.
javascript is more readable than typescript and you have to write more code in some cases to consume a js response from an api.
Readable is debatable. Your codes readability isn't going to falter cause of TS, it'll depend on how you write code in general.
As for being lazy, well... That's a poor excuse.
typescript seems a bit better to me.
I personally like the ability to assign parameters and variables types so that i can easily keep track of what they are, and in the one or two cases where i need an arbitrary variable, i still have the freedom to do so.
It's so much easier to read code when it tells you what things are instead of making you guess.
I was totally intrigued until he mentioned Product Owners
Do I still need to learn JavasCript? before go to TypeScript?
They both use the same words and you don’t have to relearn any thing?
What is Typescript?
Typescript is Microsoft's last resort in controlling and setting the standard for the internet since their epic failure with IE. TypeScript will restrict your freedom in determining the model of your program. Because, some people think it's a good idea to prefer strict rules over freedom in programming the web. And, duh...why do it the easy way when you can do it in a more complicated and sophisticated way with style?
But, because these things become a thing ... and it can pay the bill quite nicely, I guess I’ll jump into the bandwagon too.
Yippie!
Well said!
🤝
Restrict functions in only accepting the argument types they are intended to take?... What a wild concept.
Easy way is the lazy way, and likely the way that will end up just having holes in the code that shouldn't have even been in the commit in the first place.
Yeesh.
"some people think it's a good idea to prefer strict rules over freedom in programming the web" Because freedom often leads to more bugs and poor structure. 5 million line projects can be written in Python because of it's strong typing. I can't imagine a 5 million line project written in Javascript.
Thank you for such a smart explanation.
4:17 so typescript is slower in creation and compilation? Why are you advertising this as a good thing.
True
its because developer nerds ALWAYS go crazy for new software/language/tools, they foam at the mouth. But honestly.... we need to just keep it simple! Everyone wants their own tools/language to be mainstream. And us nerds get high off new stuff.
In the End..... its ONLY about the final product. I myself don't care about fancy backend stuff, I just want the final product good.
This is never a good thing. People just loves to jump into whatever bandwagon they lay their eyes on.
Most likely the newer Typescript compiler is less optimized at this point in time. ( and having the compiler check data types may catch errors not caught in Javascript )
JAVASCRIPT IS THE HATED AND MOST USEFUL.... HATERS SHOULD HATE
I really don't see how TS is faster than JS when you gotta type more.
Speeding up development time is always more about catching and identifying bugs and correcting mistakes; ergo, the quicker you can catch them, the better. Typing is the least time-consuming part of development.
90% of software development is a mix of brainstorming the optimal attack approach to a problem and detective work to search for what is broken.
@@parasharkchari This is the more reason one must learn and master JS very well. JS can be written well enough not to battle with bugs
@@olumideolaleye1834 This reminds me of the old battle between C vs C++, where a large project in C could have far more bugs than C++. ( there's reason why most graphical engines are written in C++ )
Typescript sucks makes unnecessary work … its like your computer has OCD …
Actually OCD causes you to make it the shortest and simplest.
actually its the opposite
the ambiguity of javascript would make even more work
Why would anyone in their right mind use JS unless they're behind held hostage by legacy frameworks is beyond me.
idk but for ts me it looks better or I have no idea what im talking about because im only programming in C# and C++.
I would be very grateful for some advice and guidance.
Did not catch the work "unespected"
@@RajVardhanReddylol😂
dart vs typescript
Dart is better lang than typescript
I hate the transitions
i hate it also...
TS is ugly, and the dynamic types system has some pros and you killed it.
I really like this video
nice
js
???
hmmmm
Hmmmm 🤔🤔🤔
3:28 in 2018
and still growing! ;)
what should i learn ? for web development
@@laughtale1181 try to learn html, css and javascript as a fundamental base and then move to some frontend framework, e.g. React. Maybe try to do some research in job positions in Your country to see, what is the most common FE framework required in job position and go with that.
@@jakubtomas9154 thanks man