More power to you. I prefer to use the best tool for the job which in this case are session IDs since they are simpler, have been battle tested, and proven to work for over the last two decades.
I too love the best tool for the job, which is why blanket statements saying session IDs should always be used for authentication are very puzzling to me.
HTTPS, HMAC and asymmetric keys are battle tested and proven to work as well, that was one major point of the article.
I didn't say that they should "always" be used for authentication but that session IDs fulfills most web app user authentication needs. Most devs that implement JWT treat them as stateful which defeats the purpose of them. JWT has it's use cases when done correctly.
Session mechanisms are all too often different across every web stack though, so if you have a variety of services and applications behind a single logon, you need to solve an O(n) problem that JWT makes O(1).
HTTPS, HMAC and asymmetric keys are battle tested and proven to work as well, that was one major point of the article.