JavaScript or TypeScript: which one to really dig into?
-
So, I've spent most of my professional career working on system administration, databases, and desktop applications. Now I find myself being thrust into ASP.Net Web Api 2 to build REST interfaces so that an internet portal can access internal data via IIS. I've got the server side down pretty good so my question is do I spend more time focusing on learning the ins and outs of JavaScript or TypeScript or both for the client side? As a C# dev, the type safety and classes of TypeScript are appealing but it doesn't seem to support the breadth of ECMAScript capabilities like JavaScript does. I want to focus on what will work best but I don't want to bind my hands either. Since this is really my first serious foray into browser scripting, I wanted to get the opinion of the CPians that more experienced in such matters.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
-
So, I've spent most of my professional career working on system administration, databases, and desktop applications. Now I find myself being thrust into ASP.Net Web Api 2 to build REST interfaces so that an internet portal can access internal data via IIS. I've got the server side down pretty good so my question is do I spend more time focusing on learning the ins and outs of JavaScript or TypeScript or both for the client side? As a C# dev, the type safety and classes of TypeScript are appealing but it doesn't seem to support the breadth of ECMAScript capabilities like JavaScript does. I want to focus on what will work best but I don't want to bind my hands either. Since this is really my first serious foray into browser scripting, I wanted to get the opinion of the CPians that more experienced in such matters.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
-
TypeScript is the way to go. It would be more sensible coming from the C# dev background to have the structured code even in JavaScript world which is highly loose scripting language but with huge power.
Thanks. I thought that TypeScript would give me a little more piece of mind. Before getting started on that I'm reviewing this: ECMAScript Specifications[^]. I think that I need to build a strong foundation before attempting to build a house.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
-
So, I've spent most of my professional career working on system administration, databases, and desktop applications. Now I find myself being thrust into ASP.Net Web Api 2 to build REST interfaces so that an internet portal can access internal data via IIS. I've got the server side down pretty good so my question is do I spend more time focusing on learning the ins and outs of JavaScript or TypeScript or both for the client side? As a C# dev, the type safety and classes of TypeScript are appealing but it doesn't seem to support the breadth of ECMAScript capabilities like JavaScript does. I want to focus on what will work best but I don't want to bind my hands either. Since this is really my first serious foray into browser scripting, I wanted to get the opinion of the CPians that more experienced in such matters.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
I've never used TypeScript so I can't speak to that. I use jQuery a ton. It makes using JavaScript much easier.
There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.
-
So, I've spent most of my professional career working on system administration, databases, and desktop applications. Now I find myself being thrust into ASP.Net Web Api 2 to build REST interfaces so that an internet portal can access internal data via IIS. I've got the server side down pretty good so my question is do I spend more time focusing on learning the ins and outs of JavaScript or TypeScript or both for the client side? As a C# dev, the type safety and classes of TypeScript are appealing but it doesn't seem to support the breadth of ECMAScript capabilities like JavaScript does. I want to focus on what will work best but I don't want to bind my hands either. Since this is really my first serious foray into browser scripting, I wanted to get the opinion of the CPians that more experienced in such matters.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
My viewpoint is that these super-sets (TS, CS, DART, etc) compile to JavaScript. If JS itself were so tedious or difficult to work in I would understand that, but largely it doesn't make sense to me to add a link in a chain that already uses a high-level language. It's great for someone who doesn't have the interest or capacity to learn how the underlying technology works, but doesn't really benefit someone that's willing to dig in. That said, the ECMA approach to OOP is pretty damn counter-intuitive to the C# mindset and there is a bit of a curve. I like that personally, because the switching of gears makes defining client-vs-server concerns fairly obvious, but I may be alone in that regard.
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
-
My viewpoint is that these super-sets (TS, CS, DART, etc) compile to JavaScript. If JS itself were so tedious or difficult to work in I would understand that, but largely it doesn't make sense to me to add a link in a chain that already uses a high-level language. It's great for someone who doesn't have the interest or capacity to learn how the underlying technology works, but doesn't really benefit someone that's willing to dig in. That said, the ECMA approach to OOP is pretty damn counter-intuitive to the C# mindset and there is a bit of a curve. I like that personally, because the switching of gears makes defining client-vs-server concerns fairly obvious, but I may be alone in that regard.
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
These are good points. The ECMA Standard and JavaScript is still the foundation of all the web scripting libraries so I see how working toward a professional level familiarity with it would be beneficial. It's similar to how Assembler is still the foundation of all of the programing languages. Does C# make programing a lot easier? Yes. Does is still end up as assembly instructions passed to the interpreter? Of course. C# and the rest of the high-level languages just make it easier to program, abstracting all the tedious bits. I may not be able to write a full program in x86 or x64 assembly (yet) but I know it works and that knowledge helps me write better code at the higher levels.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
-
So, I've spent most of my professional career working on system administration, databases, and desktop applications. Now I find myself being thrust into ASP.Net Web Api 2 to build REST interfaces so that an internet portal can access internal data via IIS. I've got the server side down pretty good so my question is do I spend more time focusing on learning the ins and outs of JavaScript or TypeScript or both for the client side? As a C# dev, the type safety and classes of TypeScript are appealing but it doesn't seem to support the breadth of ECMAScript capabilities like JavaScript does. I want to focus on what will work best but I don't want to bind my hands either. Since this is really my first serious foray into browser scripting, I wanted to get the opinion of the CPians that more experienced in such matters.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
Type script is a JavaScript inspired object oriented language that compiles to JavaScript. At the end - in the browser - it is always JavaScript for now, so I would say: learn JavaScript inside-out... After that, you may find it easier to use some intermediate - like TypeScript - to create the actual JavaScript code, but that's secondary... If you are coming from the intermediate part only, you will find yourself helpless against a on-client-machine-only bug, that will force you to debug the JavaScript result (and generated code is always hard to read)...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
Type script is a JavaScript inspired object oriented language that compiles to JavaScript. At the end - in the browser - it is always JavaScript for now, so I would say: learn JavaScript inside-out... After that, you may find it easier to use some intermediate - like TypeScript - to create the actual JavaScript code, but that's secondary... If you are coming from the intermediate part only, you will find yourself helpless against a on-client-machine-only bug, that will force you to debug the JavaScript result (and generated code is always hard to read)...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
I am beginning to believe that I will be better off just biting the bullet and learning more JavaScript. Any good resources to learn some of the intermidiate to advanced topics? I've got the internet (ecma-international.org, w3.org, w3schools.com) that have gotten me a good start as well as a book on JavaScript and JQuery. What I am looking for is a resource that tells me all the things I can do with JavaScript and a few pointers to get me started. So far, I'm learning how to manipulate the DOM and using XMLHttpRequest to do a little async processing from an MVC/WebApi test site that I built. Obviously, there's a lot you can do with it but nothing I can find paints a good road map on what subjects to focus on and in what order.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
-
I am beginning to believe that I will be better off just biting the bullet and learning more JavaScript. Any good resources to learn some of the intermidiate to advanced topics? I've got the internet (ecma-international.org, w3.org, w3schools.com) that have gotten me a good start as well as a book on JavaScript and JQuery. What I am looking for is a resource that tells me all the things I can do with JavaScript and a few pointers to get me started. So far, I'm learning how to manipulate the DOM and using XMLHttpRequest to do a little async processing from an MVC/WebApi test site that I built. Obviously, there's a lot you can do with it but nothing I can find paints a good road map on what subjects to focus on and in what order.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
First read you should go for is JavaScript: The Good Parts[^] Than these too: Douglas Crockford's Javascript[^] This is good also: Build A JavaScript Framework[^] And this too: Prototype in JavaScript | Sander's bits[^] And not to be afraid to pick and use a library - of you choice - intensively to easy you work...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
First read you should go for is JavaScript: The Good Parts[^] Than these too: Douglas Crockford's Javascript[^] This is good also: Build A JavaScript Framework[^] And this too: Prototype in JavaScript | Sander's bits[^] And not to be afraid to pick and use a library - of you choice - intensively to easy you work...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
So, I've spent most of my professional career working on system administration, databases, and desktop applications. Now I find myself being thrust into ASP.Net Web Api 2 to build REST interfaces so that an internet portal can access internal data via IIS. I've got the server side down pretty good so my question is do I spend more time focusing on learning the ins and outs of JavaScript or TypeScript or both for the client side? As a C# dev, the type safety and classes of TypeScript are appealing but it doesn't seem to support the breadth of ECMAScript capabilities like JavaScript does. I want to focus on what will work best but I don't want to bind my hands either. Since this is really my first serious foray into browser scripting, I wanted to get the opinion of the CPians that more experienced in such matters.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
The question is how deep a rabbit hole you are planning to follow. If your intention is to learn enough to do a project and will not become full time web developer, then TypeScript is probably easier. If you want to switch from being SysAdmin into a developer then I would suggest biting the bullet and get to know JS. I personally know JS then learn TS, then gone back to stick with JS. TS to JS is like C/C++ to Assembler.
-
So, I've spent most of my professional career working on system administration, databases, and desktop applications. Now I find myself being thrust into ASP.Net Web Api 2 to build REST interfaces so that an internet portal can access internal data via IIS. I've got the server side down pretty good so my question is do I spend more time focusing on learning the ins and outs of JavaScript or TypeScript or both for the client side? As a C# dev, the type safety and classes of TypeScript are appealing but it doesn't seem to support the breadth of ECMAScript capabilities like JavaScript does. I want to focus on what will work best but I don't want to bind my hands either. Since this is really my first serious foray into browser scripting, I wanted to get the opinion of the CPians that more experienced in such matters.
if (Object.DividedByZero == true) { Universe.Implode(); } Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
