3 ms·
> Progressive enhancement (beyond very small apps) is a challenge to maintain, since UI state needs to be shared between a server runtime and client runtime. I
by chrisdotcode 12y ago
> Progressive enhancement (beyond very small apps) is a challenge to maintain, since UI state needs to be shared between a server runtime and client runtime.
It does? Why? The server is handling the data to be rendered either way, and as I say in response to another comment, rendering the data is as simple as:
res.end(render(template, data))
> And your comments about shitty execution of web pages and apps could apply to any shitty app. They have nothing to do with client-side JavaScript applications. I expect a better argument than "I once saw a webpage that sucked".
The argument is "you are VC-funded, and taking a 1mil+ dollars to build the Next Big (S|P)aaS. You are spending tons of money on A/B testing, designers, mockups, UI specialists, and your page does not even load for the lowest common denominator - and easiest to manage (static HTML) users of the web?"
The web was built for content-first, not flash.
- iamstef 12y agoMy experiences may be biased, but most startups I work with have target audiences that do not include tin-foil hatted JavaScript disabling individuals. To the contrary, for them investing any energy in servicing this minority would be a mistake. I suspect their exists some subset of startups were this may be reversed. But they are absolutely in the minority.
- chrisdotcode 12y agoBut that's the thing. It's far easier to 'program' a static HTML than any other dynamic alternative. What people seem to not understand is that the exact same template that they are using on the client renders exactly the same on the server.