Earlier quoted context omitted.
About 5 years ago I attended a local code meetup and someone gave a presentation about this new TypeScript thing. He basically just explained the basic syntax, concepts. etc. A bit boring, but not the worst I've seen. Then in the Q&A someone asked a "In our experience, we've had problems with X, what's your take?" (I've forgotten what X was specifically), and the guy replied with "well, actually, we haven't really us…
>The entire talk seemed pretty useless to me. To you. On the flip side, it provided an introductory level overview of a concept many watching/attending may not have looked into themselves, or were thinking of looking into. It also provided a different form of introduction, which could be valuable for attendees with a learning style preference different to that of look-at-a-how-to or check-out-the-docs. >the guy repli…
For example I currently mostly work with Go, and if I would give a high-level presentation about Go I'd start with the "tour of Go" tutorial, but I'd also add some context to some things, explain where you need to be careful to avoid problems, and emphasize the usefulness of other things that may not be obvious at a glance. That kind of stuff. I think the presentation format is a great way for doing that.
A beginning JavaScript programmer might explain the "with" keyword, which would be a mistake. I have no idea if the presentation contained any mistakes like that.
I don't work much with JS, and I haven't looked much as TypeScript since, but I didn't really learn all that much more than what I already knew: "TypeScript is JavaScript with optional typing".
Was it useful for others? Maybe; I hope so. But for me personally I consider it a wasted hour in my life.