On Tue, 17 Mar 2015 14:10:10 -0700 Brendan brendan@tucows.com wrote:
i'm pretty sure thomas didn't mean that and instead meant a stateless JSON protocol with most of the logic in the client application and the server doing less work overall.
IMHO the decision narrows down to deside whether to have a thick or thin client.
If a thick client architecture is chosen you could stay with PHP. On the other hand if a thin client architecture is chosen then PHP is ruled out as PHP is not geared towards an 'always on' architecture. A thin client implies a think backend which requires an independently runtime environment better suited for a stand-alone runtime. By stand-alone runtime I mean a runtime which is capable of being self sufficient.