Re:How to avoid common SPA pitfalls when using third-party p...
by frandroid on Tuesday January 26, 2016 @05:37PM
(#10976777)
I think the title is a bit short. It should have been "The real reason to avoid jQuery with SPA frameworks".
[ Parent
| on HN ]
Re:How to avoid common SPA pitfalls when using third-party p...
by dang on Tuesday January 26, 2016 @05:44PM
(#10976834)
It's a bit baity, so we changed it to the subtitle.
Re:How to avoid common SPA pitfalls when using third-party p...
by runspired on Tuesday January 26, 2016 @06:18PM
(#10977017)
I wasn't expecting this to be a "thing", I wrote it for people I help out in the Ember community that struggle because of their jQuery background. I may update the title now that this is more widespread.
Re:How to avoid common SPA pitfalls when using third-party p...
by dang on Wednesday January 27, 2016 @03:26AM
(#10978926)
It's common for something that works well in its original context to turn into something unintended under the pressure of the HN firehose. Sort of a tragedy-of-the-commons variation.