4 ms·
> As companies move to single page applications backed by javascript and REST API, PHP CGI style classic execution model provides no advantage, when it comes to
by i_like_to_post 6y ago
> As companies move to single page applications backed by javascript and REST API, PHP CGI style classic execution model provides no advantage, when it comes to generating or serving web content
I lol'd.
SPAs are a fad. Apps that rely heavily on REST API and browser rendering rank terribly on Google.
Create a SPA and help your customers discover your competitor on the first page of Google.
- edoceo 6y agoThis assumes Google can't figure out crawling SPA.
- i_like_to_post 6y agoThat's correct. Generally, when I'm building a business, I prefer not to assume that Google will eventually, at some point in the future, solve the crawling a SPA site problem and finally discover my site. I'd rather get my 70%-80% organic search traffic today, with any boring server-side rendered tech stack.
- mgkimsal 6y agoI don't think I want any crawler ever hitting my API endpoints for customer lookups, scheduling, inventory management, etc - all that stuff that is the 'Application' part of 'SPA'. Why people use js/spa/etc stuff as the basis for a content/marketing site... I don't know. I mean... yeah, I know why - mostly to expand their skill set. But there's usually no functional benefit, and usually some drawbacks, as you're pointing out.
- admax88q 6y agoI lol'd. SPAs are great if your customers actually want an application. Figma, AirTable, Google Sheets. These don't make sense as server rendered pages. If you're in the publishing business and need your articles to rank high on Google, then yeah its probably not a good idea. EDIT: Or Slack for that matter