Re:Mobile CPUs and the Performance Inequality Gap
by scarface74 on Sunday March 29, 2020 @01:32PM
(#22720801)
Validation does need to be done on both sides. But validations on the client side means no round trips and you can do validations even when you’re not online. Also even if the content is “static”, if you don’t have access to the network, how do you do simple things like display totals from service charges, a receipt of all the items delivered - propane as deliveries and tank repairs, alarm installation or at home nurse care where they had a checklist?
Even with CRUD apps you need to display dynamic content based on user interaction.
I used to be big in native apps, until having seen too many examples of what used to be done in VB/Acess back in the day.
So you haven’t seen the poor performance of ASP.Net Web Forms with the huge hidden field to maintain state and redrawing the screen for every interaction and a network round trip?
Re:Mobile CPUs and the Performance Inequality Gap
by pjmlp on Sunday March 29, 2020 @02:14PM
(#22721214)
Not to the point that it actually matters, in a world were plenty of people are deploying node, django and rails applications.
Re:Mobile CPUs and the Performance Inequality Gap
by scarface74 on Sunday March 29, 2020 @02:28PM
(#22721312)
if you haven’t noticed, the world is moving away from server side rendering - even Microsoft is pushing toward client side rendering.
Validations always need to be done on both sides, unless one does not value security.
All of this is possible with vanilaJS, using builtin browser features, no need to kill the poor CPU with an additional bloated framework.
I used to be big in native apps, until having seen too many examples of what used to be done in VB/Acess back in the day.
So unless it is a game using OpenGL ES 3.0, Vulkan, Metal, something that requires AR/VR, real time audio, GPGPU for machine learning, or direct access to hardware sensors, it might be quite doable as PWA.