3 ms·
Just to add to the chorus of disapproval. I got a white screen on my phone. Had to switch to my laptop. Here's the thing. You're building a mainly content-dri
by andybak 13y ago
Just to add to the chorus of disapproval.
I got a white screen on my phone. Had to switch to my laptop.
Here's the thing. You're building a mainly content-driven site (still the bulk of websites).
If you go down the route of some javascript-based 'app' that squirts all the content in dynamically then you might get everything right and end up with a beautiful, fast website that works across a range of devices, is accessibly, doesn't break bookmarking or the back-button and doesn't kill your SEO.
But you've got to get everything right so the odds are that you'll get a part of this wrong. Debugging and testing are also suddenly a much bigger part of the equation.
So what have you gained over plain old HTML and CSS with progressive enhancement? If you want the possible speed advantages of not re-rendering whole pages then techniques such as Pjax can be used to get the best of both worlds.
In short - with an app-based approach over a html-based approach - there are lots of ways to get it wrong and only a few ways to get it right. You're probably not clever enough to get everything right. Gawker weren't.