* It doesn't support expiry as a claim; you have to check it against the current time manually, and factor in leeway if you want that. Because no one ever screwed up a timestamp check.
* It doesn't support any other verifiable claims, for that matter, so if you want to add e.g. issuer and issued-at, you'll have to do so manually.
* If you're not writing a Rails app, you have to pull in ActiveSupport... or copy code, as you suggest, which seems bad for other reasons. Surely maintaining your own crypto fork is almost as bad as writing your own crypto in the first place?
* To the best of my knowledge, ruby-jwt has not suffered either of the two JWT vulnerabilities discussed in this thread.
Finally, why is this "simple":
@verifier = ActiveSupport::MessageVerifier.new('s3Krit', digest: 'SHA256')
cookies[:remember_me] = @verifier.generate([@user.id, 2.weeks.from_now])
But this is "bad": payload = { sub: @user.id, exp: Time.now.to_i + 1_209_600 }
cookies[:remember_me] = JWT.encode(payload, 's3Krit', 'HS256')
They seem fairly equivalent to me?