Create templates to quickly answer FAQs or store snippets for re-use.
First off, thanks for the back-and-forth :) I really appreciate it!
That's a great point - I think I've already started running into that fuzzy boundary when I've tried using frameworks. Most of my TypeScript experiments have been pretty vanilla, just learning how the canvas works and things like that, but a few things I tried to do with a TS/React project proved trickier than expected.
It seems like, once again, the fabled missing ingredient is Other People! Funny how that works. Another goal of mine for the near future is a first PR, maybe I should focus on some plain JS codebases to explore.
Give yourself some credit -- the canvas can get pretty vicious once animation frames are involved!
Oy - I more meant vanilla as in free of external dependencies but you are not wrong!
Cool, thanks! I do feel I have a good grasp of type systems from Rust and Haskell, but I will say that TS's structural typing is pretty foreign to me. It's cool seeing different ways of solving that problem.
I always try to learn all I need to know to get a job done, then I try to learn the details when I need them.
Do you have a job that needs TypeScript? Learn it.
If you don't have a job that needs TypeScript, then dont learn it.
If nobody tells you if you need it or not, try to figure out the expected complexity of the project and if you comfortable with it, use JS, if you aren't comfortable with the expected complexity, then use TS.
That's the thing - I can't tell what does or doesn't need it, and all of my programming experience has been statically and strongly typed. So it sort of feels like every project needs it to me, but that's obviously not the case.
If you wanna easy going with coding, you will probably have more luck with TypeScript.
Easy going sounds good, but not at the expense of actually understanding my code. That does sound like a nightmare, but if that nightmare is the state of the art I'm just prejudiced.
Really appreciate your thoughts! Agreed about the tooling - seems like a six of one sorta deal
That makes a lot of sense! It's definitely the most unique type system I've used because of how gradual it is - I can definitely understand the benefit of understanding the underlying systems first before tacking something extra on top.
Interesting. Would it still be co considered a subset? I believe (though I'm no math guy) that the set of possible JS programs is larger than the set of possible TS programs.
You underestimate the developer community 🤣 there is a reason that reinvented of wheels is a common theme. But you have to ask, is the wheel the most optimal shape? So many questions, so much to write about!
Note that: I'm a JS hater.
Thanks for the insight! I'm already familiar with ClojureScript, ReaonML, and OCaml, and have looked at Elixir -- why do you not recommend typescript if you say it's more successful than Flow?
Cool! Thanks for the feedback - that was my assumption, at least! Betsy brought up a great point in that there's more valid styles of JS than there are of TS but I still want to learn best practices first
You do NOT waste your time learning TypeScript.
Kindred spirits, we are!
In more ways than one, though my low brass days are long gone now.
Thanks for sharing your write-up! Thats good to know... I've really been wanting to learn more about Angular but there's only so many hours in a week. I think I only went for react first because I'd used the CLJS analogue - Angular seems a bit more up my alley!
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.