4 ms·
I think GraphQL is useful for getting data for UIs on any platform. - build views without being blocked waiting for a new rest endpoint - get exactly what the
by odammit 9y ago
I think GraphQL is useful for getting data for UIs on any platform.
- build views without being blocked waiting for a new rest endpoint
- get exactly what the UI needs to render
[edit]
Although to negate my own first point, nb4 being blocked on waiting for new mutations and queries :P
- deleted 9y ago[deleted]
- k__ 9y agoAlso, you can use it to query local data too. This enables you to transparently move data-source around.
- y_u_no_rust 9y agotalk about going backwards ffs
- odammit 9y agoThat’s a good point! Never thought about local data sources. I’ve only mapped over SQL, REST, and redis/etc.
- ComputerGuru 9y agoNative applications don’t need that, though. Modern languages embrace async/await and don’t waste cycles or block the UI or even the backend unnecessarily waiting for network/local IO or user interaction. In that regard, rust is actually behind. Async/await is still coming.
- odammit 9y agoNative applications don’t get blocked waiting for backend engineers to implement a new REST endpoint? Native applications don’t benefit from smaller responses of just the data they need to render a view? I am confused.