4 ms·

Saw the demo - and love the simplicity of backend calls. It makes a lot of sense for full-stack devs to increase development velocity, but how do you see this f

Saw the demo - and love the simplicity of backend calls. It makes a lot of sense for full-stack devs to increase development velocity, but how do you see this fit in with teams that already have a backend stack? What’s the value prop for backend devs to adopt this? It also seems like Blitz.js[0] has a similar approach to yours (batteries-included, integrated FE & BE). Is there anything in particular that separates out thin.dev from Blitz? Edit: Learning more about IHP, I haven’t seen such a promising Haskell web framework since Happstack, very eager to try that out! [0] https://blitzjs.com https://blitzjs.com

_query 4y ago
Thanks for the input! Thin can quickly be integrated in an existing stack as long as you're using postgres. The value proposition with an existing backend can be: Improved UX thanks to very low latency. E.g. Thin automatically does optimistic updates when you're inserting or updating a database record. This results in a really nice user experience compared to what you'd get with a normal REST Backend. I've no experience with blitz.js. From a first look it seems it goes in the same direction. Blitz.js is not leaning on realtime as much as we're doing. Additionally it seems that it doesn't provide optimistic updates out of the box. On IHP: Yes! :) IHP has a promising future ahead! All the Thin Feature are btw also supported in IHP. The Thin JS library is just a small wrapper around the IHP DataSync SDK :)