Book Image

TypeScript High Performance

By : Ajinkya Kher
Book Image

TypeScript High Performance

By: Ajinkya Kher

Overview of this book

<p>In a world where a tiny decrease in frames per second impacts customer engagement greatly, writing highly scalable code is more of a necessity than a luxury. Using TypeScript you get type checking during development. This gives you the power to write optimized code quickly. This book is also a solid tool to those who’re curious to understand the impact of performance in production, and it is of the greatest aid to the proactive developers who like to be cognizant of and avoid the classic pitfalls while coding.</p> <p>The book will starts with explaining the efficient implementation of basic data Structures, data types, and flow control. You will then learn efficient use of advanced language constructs and asynchronous programming. Further, you'll learn different configurations available with TSLint to improve code quality and performance. Next, we'll introduce you to the concepts of profiling and then we deep dive into profiling JS with several tools such as firebug, chrome, fiddler. Finally, you'll learn techniques to build and deploy real world large scale TypeScript applications.</p>
Table of Contents (17 chapters)
Title Page
Credits
Foreword
About the Author
Acknowlegement
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
7
Profile Deployed JS with Developer Tools and Fiddler

Async and await


If you noticed carefully, with both callbacks and promises, there is an overhead involved. With callbacks, the overhead is in the form of writing and maintaining callback functions that need to be passed in each time we call an asynchronous function. Within the callback function, we need to handle both the success and error case. With promises, one good thing is, we no longer need to pass around callbacks, but similar to callbacks, there is an overhead in terms of handling the resolution in then and the error in catch.

Furthermore, one of the worst pain points is exposed when dealing with chained callbacks/promises. Calling subsequent asynchronous functions after the previous asynchronous function calls have completed leads to very messy looking code.

Wouldn't it be nice to be able to call asynchronous functions in a linear fashion irrespective of the calling order? Wouldn't it be nice to write asynchronous code just like you would write synchronous code, without worrying about...