A Front End Does Not Have to Be Rich

Re:A Front End Does Not Have to Be Rich by sbhn on Monday March 11, 2019 @02:59PM (#19361782)

Yay, the world is waking up, google search is not spa, Ebay is not spa, Wkipedia is not spa, Youtube is not spa, Stack exchange is not spa, Duck Duck Go is not spa, HomeIdea3D.com is spa though

[ Parent | on HN ]

Re:A Front End Does Not Have to Be Rich by snazz on Monday March 11, 2019 @03:24PM (#19361975)

Google, eBay, Wikipedia, YouTube, Stack Exchange, and DuckDuckGo fit nicely with the concept of “type search in form, get list of links, video, article, QA page, etc.” HomeIdea3D tries to emulate/replace a desktop application. This is the type of tool that I would allow a SPA for, even though I normally browse with JS disabled.

[ Parent | on HN ]

Re:A Front End Does Not Have to Be Rich by maxxxxx on Monday March 11, 2019 @03:12PM (#19361866)

HomeIdea3D.com is a real app with complex state and stuff so an SPA makes sense here.

[ Parent | on HN ]

Re:A Front End Does Not Have to Be Rich by Conlectus on Monday March 11, 2019 @03:32PM (#19362029)

YouTube is indeed a SPA.

[ Parent | on HN ]

Re:A Front End Does Not Have to Be Rich by ngrilly on Monday March 11, 2019 @04:06PM (#19362287)

YouTube is not really a SPA as in React or Vue. It looks like they use something similar to TurboLinks or Intercooler: https://youtube.github.io/spfjs/

Edit for downvoters: Ok, technically, YouTube is a SPA. What I meant, in the context of this discussion, is that YouTube uses a technique similar to what GitHub does, where the server returns fragments of HTML.

[ Parent | on HN ]