If you have a business case for JWTs, fine, take on the extra complexity and implement JWTs properly.
If you don't (and as the author points out, the majority of implementations don't need them), push back and do it properly using a simpler system, rather than implement the complexity just to then abstract it away.
I like it because it’s faster and it’s enabling more powerful integrations.
We (Clerk) abstracted away the complexity so it’s just an implementation detail, and think other tools should do the same instead of letting developers trip over the hazards.