bodhi
Joined 19 years ago
Joined 19 years ago
I’d be interested in seeing this hooked up to Xstate.
But controlling or understanding the control flow in Crank generator components, ie. when does ‘yield‘ return, looks like a bit of a nightmare!
https://www.sciencedirect.com/science/article/pii/0167642391...
Given we're talking about APIs, we avoid many of the UX problems, but it feels like taking on a different set of problems than just using a bearer token. It does provide baked in solutions for things like revocation and expiry though.
I've started describing it to people as: British shows are designed to entertain first, and perhaps kids can learn something, whereas the US approach is THOU SHALT MAKE SURE CHILDREN UNDERSTAND RIGHT AND WRONG!.
I can't stand this kind of "2-d" presentation...
(I don't have first hand experience with either, so I'm just musing too..)
You have, I assume, a licensed copy of Harry Potter. That license restricts you from doing certain activities, like making (distributing? Lets go with distributing) derived works. Your models are derived works. Thus when you distribute your models, you’re violating the licence terms you “agreed” to when you acquired your copy of Harry Potter.
This is no judgement by me about whether that’s reasonable or not, just my understanding of the mechanics.