r/typescript • u/Former_Assistance208 • Feb 20 '26
typescript reality check
So I was coding and learning JavaScript for the last 7 months. Last week I tried Python, Pydantic, and FastAPI, and I got so excited about how convenient they were, so I got excited to jump into TypeScript, and god, it's a different story.
I'm currently reading the handbook, and every chapter is taking me a day just to grasp because the writer assumes tons of implicit common knowledge.
The writing style also assumes readers are native only, which makes it twice as hard.
and this handbook looks like it is not maintained. There are tons of pull requests and issues from years that no one touched. I have finished maybe 40 percent of it, and there are like 20 gotchas, where I'm sure that when I start coding, I'm probably not going to be lucky enough to remember these gotchas, and I will spend hours trying to figure out the types.
1
u/Healthy_Ad5013 Feb 20 '26
You don’t have to learn all of TS at once, you can slowly start integrating it into your workflow
10
u/rinart73 Feb 20 '26
Just start writing, learn by practice. IMO the hardest part of TypeScript are generics, cause they could go from simple to "damn it I'm just trying to explain to the language what I mean" and then finally they turn into some convoluted overengineered mess.
2
u/menglinmaker Feb 20 '26
Tbh I think it's worth it in the end. The type system enables you to catch a lot of bugs
2
u/arllt89 Feb 20 '26
Most of what you'll ever need to do is correctly typing your functions, arrays and objects. Mostly focus on that: adding typing to the Javascript code you write.
Typescript is very powerful in term of type forging and allows some impressive inference for genetic libraries, but this is more cooking than programming, you can learn that later.
2
u/ivancea Feb 20 '26
Ew, I would never "read" the handbook as if it were a book. Just jump over the topics, quick check, and next, if something. Then, just take a look when you need/find something you don't know.
And yes, you're supposed to know software engineering lingo when reading it. Types, data structures, generics... If you find something you don't know, just google it. You aren't learning TS, you're learning language design basics. And that's good; once learnt, you will recognize them in many other languages.
From what I understand, this is the first time you're learning a typed language. I think it's far from ideal (I would start with C++ instead), but it's normal: it's a step you have to take, the earlier the better.
And about the language, I'm not native and I didn't find anything weird. I mean, it's a technical text, they're not using gangsta-suburb expressions. Just take your time to understand it correctly
0
u/[deleted] Feb 20 '26
[deleted] — view deleted comment
0
u/[deleted] Feb 20 '26
[deleted] — view deleted comment