3 ms·
An unanswered question in this debate is: what is a web app and what is a web site? Sometimes the boundaries are blurry and sometimes they are clear. For examp
by open-source-ux 11y ago
An unanswered question in this debate is: what is a web app and what is a web site? Sometimes the boundaries are blurry and sometimes they are clear.
For example, should a blog rendered in the browser be treated as a web app? Or rendered principally as HTML and CSS before it's sent to the browser (rather than rendered in the browser using Javascript). Here's an example: over 300K of Javascript to render a plain text page: http://elm-lang.org/blog/new-adventures-for-elm http://elm-lang.org/blog/new-adventures-for-elm
My impression is that some developers are beginning to treat anything rendered in the browser as a web app - even plain web pages with no dynamic elements.
Why do developers do this? Is it because it makes their life easier using a single tool or language for both dynamic and static content? Or is it because they want to learn a new framework that's popular or interesting? Whatever the reason, one has to ask if giving users a good and fast site experience comes anywhere into the equation.
- paulddraper 11y ago"Is it because it makes their life easier using a single tool or language for both dynamic and static content?" Mostly this. As soon as you add a bit of dynamicism, it becomes easier to do everything in one language/workflow.