I don't know if I'd call a book with 61 chapters "concise".

What I miss in this book is the reasoning.

https://gibbok.github.io/typescript-book/book/differences-be...

So we know there are types and interfaces. One support declaration merging, one does not. Both can extend others, but in different ways. But why? Why there are two of them? When should I use them? Is one better than the other?

I was wondering what is the community's opinion on the official TypeScript Handbook

https://www.typescriptlang.org/docs/handbook/intro.html

Popular in 2023 (215 points, 91 comments) https://news.ycombinator.com/item?id=36641634

Please provide a PDF as well. I cannot read books in HTML format because I need to keep track of where i left. That means I either have to leave the browser tab open (but this is prone to accidentally closing it) or I need to bookmark every progress, which creates noise in my bookmarks. With a PDF I simply leave it, the reader remembers my last page. I also have a sense of progress with pdf.

And I have this roadmap if anyone interested in

https://nemorize.com/roadmaps/typescript

I know why typescript "succeeded", but always wonder what kind of web we would have if infact Haxe had become more popular for web in the early days. My guesstimate is we would have had bundlers in native code much, much earlier, and generally much faster and more robust tooling. Its only now we see projects like esbuild, and even TS being written in a compiled language (go), and other efforts in rust.

Also it would have been interesting sto ser what influence Haxe would have had on javascript itself

Thanks for sharing, this is useful.

To the author, congrats and thank you. I have one piece of feedback:

When you are typing Typescript on your keyboard you are typing types using a strongly typed language.

Some definitions would be useful to novices: 'type' as a noun or verb, in the mathematical context + the notion of 'strong'.

Unfortunately most of the content hasn't been updated for two years straight, which is quite a lot considering how much ECMAScript and TypeScript have been changing in recent years. I guess it's still a good reference, though.

Would also recommend https://types.kitlangton.com/ as a companion — sometimes many examples can illustrate the point more succinctly than text.

[dead]

> Some of the benefits of TypeScript:

> Access to ES6 and ES7 features

> Cross-Platform and Cross-browser Compatibility

Damn, I wasn't aware that since I avoid TS, I cannot use ES6 and ES7, and my vanilla JavaScript doesn't run in all browsers :(

I guess over-hyping the technology that the book is about is to be expected, but it still leaves a slightly sour taste in my mouth when people oversell what they're talking about it.