49 karma · joined April 11, 2023
Sorry, my previous comment wasn't very clear. Of course, faster languages produce faster results. But the language alone isn't enough in this case.
But for the current product I built my own server. I was tired of fighting some Keycloak specifics like - No "stay logged in forever if you use the (web) application from time to time". - Bugs around caching (especially in integration tests). - No zero downtime deployment (should be fixed soon, too late for me) - Weaknesses around configuration. I used to use keycloak-config-cli, which is good enough for most use cases.
And some missing functionality that needs to be implemented very often, like "Accept ToS before profile is created". Having said that, Keycloak is a very good product and I haven't found a better free and open source product. But sometimes it is not the right choice.
By the way, I personally don't plan to outsource user data and credentials to a 3rd party service. Although Auth0 is very sexy.
CRL is probably not going to help you. At least I have no idea. But jti's blacklist will. Don't forget - you still have to maintain and distribute it, which probably won't lead to a better implementation.
What he probably means is that JWT can't be invalidated on its own like you can with a session. But of course it can be done in a similar way, and some products support it. You just lose some of the benefits of JWT. (Let alone the ability to negotiate the logout time span).
Personally, I wouldn't link it directly to rust, but to rewriting. When you develop something, you usually can't account for all future changes that affect performance, design, LOC, robustness, and so on. But with rewrite, you take them all into account. So there is a big chance that rewrite will be superior in many areas. It will probably have the same effect as if they had rewritten it in C++ again.
I am working on a learning app/system. The reason for that is, that it is very difficult for me to remember staff. I tried some apps and systems like spaced repetition/leitner, but they didn't work well for me, especially when there are a lot of cards. Supermemo is the closest thing that has worked for me.
After that I gave up and experimented with plain paper based maps and probably found the best way for me to learn. Then I implemented an improved version of it, mainly because the computer can store more historical information. At its core, the system measures the difficulty of each card and creates appropriate learning batches.
I have a working prototype, and so far I have gotten amazing feedback on it. I have introduced a version for people who have even more difficulties to learn.
It has a long way to go, but if anyone is interested in trying it out when it goes public next year, please let me know.