Don't forget that internal combustions engines lose power and efficiency over their lifetimes. Bearings, piston rings and other components wear, injectors and valves get dirty, surfaces develop varnish, etc. My last ICE car started needing a quart of oil every few months and that was with very good maintenance and not being driven hard.
I've been curious about how the degradation compares to EVs. I'm aware it's different kind of wear and that there's different ways to mitigate and repair EVs vs ICE, but they both have their own lifetimes and loss of performance.
I believe the difference between ICE degradation and EV degradation is that the EV one actually affects the car's range.
While it is true that your car might consume more oil, and some other component might need replacing, its range, assuming it has been serviced properly, should be similar to what you could get out of it new.
I do wonder if the sum of the costs of getting the ICE car back to mint condition will be the same as getting some cells replaced so you get full range again.
Keycloak ended up being quite extensible and powerful, but the UI and data model both sometimes made things more difficult than they had to be... this could be an interesting project to look at.
One bonus (for us) for Keycloak was that it was JVM-based, meaning it was easier to integrate our existing JVM libraries. Though its use of Hibernate was frustrating at times, heh
The sheer complexity of Keycloak's configuration and deployment vs. something like ORY's Hydra was night and day.
And the fact that I could intercept the auth flow through a callback and use their RESTful API to drive it was amazing. No more "package this JAR" and hope that it works. Hydra would run on its own and I don't have to touch it, except when I have to upgrade it.