3 ms·
> here are many instances of content being lost in the mire of people treating what should be simple pages as if they are complex applications, but... But....
by lucideer 9y ago
> here are many instances of content being lost in the mire of people treating what should be simple pages as if they are complex applications, but...
But.... I think this is the norm, and not the exception. Sure, there are certainly a lot more "web applications* out there today than there were in 1999/2003, but I would wager there are far more "web apps that should just be pages" than legit app use-cases.
- marcosdumay 9y agoEvery web page with a menu somewhere hacked out of nav and ul elements and some css would gain by including some application-oriented markup at their top level and restricting the text-oriented markup into the text area. There's not a clear separation between "text" and "application" on the web. Nearly every site has both.
- lucideer 9y agoI disagree. You're right that there is of course no clear separation (the opposite also being true: most complex web applications will contain text content), but the differentiator is when the application side becomes large and complex enough to warrant a change in paradigm. Doing that for a little blog menu is overengineering.
- marcosdumay 9y agoEvery page starting at the application paradigm, and explicitly changing when displaying text would fit almost all the cases better than application and text markups that don't talk between themselves.
- ng12 9y agoI don't think that's true at all. It would appear that way if you're only considering the public, "user space" internet. I've done nothing but build web applications in the enterprise sector for the last several years, all of which could not be "just pages".