My biggest problem with JWT is that it's way overhyped, leading less experienced devs to believe JWT is the only way to implement auth, unless you use a 3rd party provider. JWT is a solution to a problem 95% of us don't have: https://apibakery.com/blog/tech/no-jwt/
1) not having to worry about authentication in their app (and not about security issues, exploits, account recovery, fake accounts, bots, ...)
3) the ability to use it in any framework they want (e.g. the Go standard library "framework")
4) the ability to "upgrade" to full microservice authorization
And yes, these are sort-of kind-of not-quite-but-almost provided in Django, Spring and Ruby On Rails, but if you want to use whatever framework you want ... JWT is definitely the closest thing available, or at least it seems so.