News for hackers. Stuff that matters.
Re:The boring front-end developer by vilmosi on Monday July 13, 2015 @02:07PM (#9879847)
Honest question, what's wrong with SPA?
Re:The boring front-end developer by alanh on Monday July 13, 2015 @02:11PM (#9879868)
The author write and linked to an article on the downsides. While I haven't read it, I do rage every time I click on a link to a Blogger.com-hosted article and watch some fucking Blogger logo animating as they load a web app to show me some static text. There’s no need for anything to load before showing me the blog page. The experience has been degraded and made more fragile, not enhanced.
Re:The boring front-end developer by woah on Tuesday July 14, 2015 @05:26AM (#9883682)
Similar to how I hate all hamburgers because of those damn dry McDonald's buns.
Re:The boring front-end developer by vilmosi on Monday July 13, 2015 @02:32PM (#9880016)
I've read many articles about SPA issues. I don't think any of them can't be overcomed.

But when I say webapp I don't mean blogs or regular mostly static websites. I mean Web applications.

Re:The boring front-end developer by snarkyturtle on Monday July 13, 2015 @03:12PM (#9880325)
If people disable JS or if it fails for whatever reason, you'll be left with an unusable site. If fonts don't load or if css doesn't load, at least you still have html and you could read what's on the screen. With JS you won't even be able to navigate to pages since it all gets handled with js.

That and it often has more to load than your traditional html/css page, which means a less pleasant experience on slower connections (mobile).

Re:The boring front-end developer by woah on Tuesday July 14, 2015 @05:28AM (#9883688)
Not true if you use a decent framework.
Re:The boring front-end developer by snarkyturtle on Wednesday July 15, 2015 @01:31PM (#9892730)
If your framework just saves up json like most SPA's, your pretty much SOL unless you do non-js fallbacks, but that's boring and tedious ;)
Re:The boring front-end developer by matt_s on Monday July 13, 2015 @02:50PM (#9880144)
Given that the vast majority of end users are not techie - what value does SPA add to an end user of a web application?
Re:The boring front-end developer by vilmosi on Monday July 13, 2015 @03:08PM (#9880298)
Interactivity mostly. Imagine if Google Maps reloaded every time you zoom in or pick a location.
Re:The boring front-end developer by alanh on Monday July 13, 2015 @04:48PM (#9880958)
Google Maps is famous as a pioneering use of AJAX, not as an SPA. Whether it is or is not an SPA at present is largely immaterial. There are many ways to create interactive experiences without full-page reloads, and going full SPA is just one route.
Re:The boring front-end developer by vilmosi on Monday July 13, 2015 @05:43PM (#9881353)
Sorry, I'm a bit confused about the difference between an Ajax powered page vs an SPA
Re:The boring front-end developer by matt_s on Tuesday July 14, 2015 @11:01AM (#9885384)
AJAX and the ability to manipulate the DOM has been around for about a decade or so, AJAX came out of Microsoft I believe.

Putting bits of AJAX into a web app doesn't make it SPA. Lets say you have a CRUD web application that is tax forms which end up being 5-10 "pages" printed. Then as a SPA you would have to load all the code to generate the 5-10 pages of forms, validation, logic, etc. onto a Single Page. This single page would be where everything is done, the URL would not change and the end user would have a seamless experience.

If the goal is interactivity and seamless operation to the end user, attempting to mimic a desktop app, there are multiple paths to achieving that goal. Limiting the design to a single page seems sort of contrived and a "do it because I can" type of approach, absent of user requirements - in my opinion.

Re:The boring front-end developer by vilmosi on Tuesday July 14, 2015 @03:07PM (#9887288)
>>> This single page would be where everything is done, the URL would not change

There's HTML5 history API, lazy loading... Seriously, you describe SPAs in very simplistic terms that are just not true. Do you have any experience building them?

Google Maps is technically an "Ajax powered web app", but it's technically an SPA too as you never encounter a full page refresh.

Re:The boring front-end developer by mod on Monday July 13, 2015 @02:49PM (#9880141)
Nothing's really wrong with SPAs (they have benefits and drawbacks).

What's wrong is making a blanket statement that "every web app" should be one. Also you're trying to draw a fine distinction between web apps and websites, which could be another discussion altogether, probably with no big agreement on where to place the line.

Re:The boring front-end developer by vilmosi on Monday July 13, 2015 @03:07PM (#9880287)
Sorry, didn't mean to sound like I was making a blanket statement. I agree there's a fine line between web app and website. No-one should take the decision of using an SPA lightly.