reverentgeek

Wow, that's cool. I wasn't aware of that one!

Hi! David, the author here. I'm glad to hear you enjoyed the comic style. This post is a high-level introduction/overview of OAuth/OIDC, so definitely not intended to be complete. However, I would like to understand more what parts you think were "unreliable" or leave the "wrong impression." Thanks!

I'm so glad to hear it :)

I'm glad to hear it! Thanks for the feedback!

Hey! This is David, the author. I'm so glad to hear this post helped you to better understand OAuth and OIDC. Thank you for the feedback!

About 4 years ago, I started creating hand-drawn illustrations for all my tech presentations and blog posts. There are lots of benefits, including being unique and engaging. I've written on the subject many times. Here's the most recent post: https://reverentgeek.com/how-to-be-a-superhuman-communicator...

Ask me anything ;)

Hey! I wrote this because I've given lots of introductory talks on Node.js and written a lot of tutorials, and one of the most frequent things I'm asked is the tools I use. If you use VS Code, what are your favorite extensions? If you don't use VS Code, what are your favorite tools for writing Node.js apps?

True, it's not the same kind of leaky abstraction you find with other technologies. I'm thinking more about the newcomer to JavaScript/TypeScript, who has only focused on the latest language features, trying to get a grasp of what is going on in the ES5-compatible code that gets generated.

Same is true with relying on Babel, of course.

I agree. It's ugly. I understand it's named globalThis to avoid collision with other libraries and breaking things, but my goodness.

That is a legitimate concern. Even if the person isn't new to programming and is coming from other C-like languages such as Java or C#, there's a good deal of precedence. Just like the "Don't Make Me Think" usability argument, we ought to stick with the conventions that people already know and are familiar with.

Here's the FAQ on the private syntax: https://github.com/tc39/proposal-class-fields/blob/master/PR...

Yes. I've read some of the reasoning behind choosing the syntax. Regardless of the issues, I think going with the current proposed syntax is a terrible mistake.