3 ms·
Data comes from the server as JSON. Data comes from the user as DOM events and changes. There's always going to be an impedance mismatch. The DOM API sucks, so
by stickfigure 3y ago
Data comes from the server as JSON. Data comes from the user as DOM events and changes. There's always going to be an impedance mismatch.
The DOM API sucks, so React et al went all in with state-as-objects. IMO it was the right call.
- hinkley 3y agoI just don't think DOM->JSON->server->microservice->DB->microservice->server->JSON->DOM is sustainable long term. It's had a good run, but it's a big part of the reason I'm looking at Phoenix for a personal project. React is predicated upon solving the wrong problem. Talk about impedance mismatches.
- robertoandred 3y agoI'm not sure switching to DOM->JSON->server->microservice->DB->microservice->server->DOM will make much of a difference.
- hinkley 3y agoComplexity is usually quadratic or factorial. Only a tiny number of systems are logarithmic. 20% reduction in parts can often be a 40-70% reduction in cognitive load. But the funny thing with fractions is that if go above a threshold and come back from the brink, the path back is a smaller number than the path out. So if you go from 8 to 10 steps that's 25% worse and if you undo that bad decision you are getting 20% better. So you want to be careful to compare sustainable to unsustainable and not the other way around, if you follow me.