How to avoid common SPA pitfalls when using third-party plugins

Re:How to avoid common SPA pitfalls when using third-party p... by Khao on Tuesday January 26, 2016 @05:03PM (#10976497)

The real reason to avoid single page apps.

[ Parent | on HN ]

Re:How to avoid common SPA pitfalls when using third-party p... by lolc on Tuesday January 26, 2016 @05:12PM (#10976575)

"The real reason to avoid JavaScript"

Ooops, wrong decade

[ Parent | on HN ]

Re:How to avoid common SPA pitfalls when using third-party p... by Smudge on Tuesday January 26, 2016 @05:18PM (#10976630)

Honestly, more like "the real reason to avoid programming"

If you are the type of person who likes to paint ideas and approaches in black and white, pointing out only the upsides of the things you like and only the downsides of the things you don't like, then you're going to REALLY hate programming.

[ Parent | on HN ]

Re:How to avoid common SPA pitfalls when using third-party p... by runspired on Tuesday January 26, 2016 @05:15PM (#10976608)

Using static pages just so you can avoid writing good code seems smart..

[ Parent | on HN ]

Re:How to avoid common SPA pitfalls when using third-party p... by dasil003 on Wednesday January 27, 2016 @12:53AM (#10978486)

Running code is very powerful, but the real power over the long haul is running the least amount of code necessary to get the job done.

[ Parent | on HN ]