4 ms·
I can’t agree with most of the points, especially the ones relating to performance, at least as far as SDUI as a generic concept is concerned. If Judo is reinve
by Zanfa 5y ago
I can’t agree with most of the points, especially the ones relating to performance, at least as far as SDUI as a generic concept is concerned. If Judo is reinventing HTML, that’s one thing, but a sane approach to SDUI gives you native UI performance (including complex interactions and animations) with reduced network bandwidth requirements.
- hitekker 5y agoSpeaking from personal experience, I agree with most of the points listed in the linked comment The incompatibility of GraphQL and SDUI is obvious; the former dictates UI from the frontend, the latter from the backend. Poor performance stems from SDUI acting as a shim around as set of native component; another abstraction that introduces slowdown. As for the rest of the point, difficulty in hiring for the bespoke SDUI framework, loss of expertise on the platform of choice... those are all things I've in the tech giant I work at. To the point, that the GraphQL folks had to sit down with the SDUI folks to tell them to back off. For better or for worse, SDUI the buzzword disrespects mobile engineering. Bored developers leap at the chance to force an overengineered DSL on their coworkers, while upper management is sucked in by the illusion of a thin client offering complete control with no cost whatsoever.