Static Web Apps

AndrewDucker wrote: post #3

ofrzeta wrote: post #2

why call it "static", when it's obviously dynamic?

Because the server isn't dynamically producing web pages? (I actually moved to this model myself recently - server producing data, client using Angular to display it.)

It's still misleading. There's already a term for it. It's "single page web apps". Also they are quite dynamic, as they change the browser state through Javascript and HTTP requests to the server. Nevermind.

Re: Static Web Apps

#5

Post by mbleigh » Tue, Jul 29, 2014, 9:08 AM UTC

ofrzeta wrote: post #4

AndrewDucker wrote: post #3

Earlier quoted context omitted.

Because the server isn't dynamically producing web pages? (I actually moved to this model myself recently - server producing data, client using Angular to display it.)

It's still misleading. There's already a term for it. It's "single page web apps". Also they are quite dynamic, as they change the browser state through Javascript and HTTP requests to the server. Nevermind.

Static Apps also encompass statically compiled web apps (e.g. Jekyll sites), so it's not just SPA. I've also always hated the term Single-Page App, it's like "horseless carriage." I prefer the term "Web Client."

That being said, there is lots of confusion out there because of the term static. While the term is accurate in terms of using static file servers to run web applications, I'm beginning to think a new term might be necessary.