5 ms·
This is definitely interesting and I will spend some more time checking this out. This tooling looks more advanced than pretty much anything else out there, but
by hermanradtke 8y ago
This is definitely interesting and I will spend some more time checking this out. This tooling looks more advanced than pretty much anything else out there, but from what I can tell it is a server-side driven approach. I have been trying to imagine what tooling that is client-side first looks like. It should not matter _how_ a server implements something, such as Siren, only that it properly follows the semantics of the Siren protocol.
- dustingetz 8y agoIt can be server driven, but it doesn't have to be. It depends where the data is and what the permissible access patterns are and which process is responsible for enforcing them. These days the data that matters is in server-side databases with tightly controlled access patterns so it is pretty weird for the client to be in charge. Hyperfiddle's data protocols are sufficiently abstract to run anywhere in the continnuum of data ownership [1], but so far we've only bothered to implement the parts of it that matter to today-era businesses. Are we thinking about this the same way or have I missed the mark? [1] http://www.dustingetz.com/:urbit-continuum-of-data-ownership/ http://www.dustingetz.com/:urbit-continuum-of-data-ownership...
- pdimitar 8y agoWow, this is really interesting. Wish I worked on it! What tech and languages do you guys use? And are you hiring?