3 ms·

I agree to some extent, but I wonder if you actually tackled a web project of more-than-trivial complexity? I did, and tried to find a number of good abstracti

I agree to some extent, but I wonder if you actually tackled a web project of more-than-trivial complexity? I did, and tried to find a number of good abstractions (for example, generating UI / ORM according to data structures), but in the end didn't come up with something satisfying. It's too easy to paint yourself into a corner. In my opinion one of the big sources of essential complexity is the layering. You have representations of your data in the DOM, in Javascript objects, in HTTP bodies / URLs, in server-side plain text representations, in the server-side language's objects, in the database... And strictly speaking you have to make sure (de)serialization works and data integrity holds at each of these boundaries. Also, many functional parts need to be present in more than one of these domains.

alexasmyths 9y ago
I've worked on big and small. Even for the 'big ones' the (there were network management apps) - the 'business logic' (networking logic in this case) - was not rocket science in the end. As you indicated, not only is the 'layering' a pain, but often there's a whole set of technologies and toolchains at each layer! Even just starting with 'identity' for a web app, i.e. Facebook and Twitter integration along with basic credentials - can be a big pain.