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

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

Yes, some of this is from the misuse of jQuery. But I fix that misuse a lot, so I felt it needed explicitly pointed out.

But many of these complaints have nothing to do with misuse and everything to do with either a lack of awareness about selector consequences, or a decade of built up code debt in the jQuery plugin ecosystem.

All of these examples are true for all JS frameworks, even non-SPA frameworks. Dynamic DOM is a problem for code that wasn't designed to clean up.

There is a real reason to avoid jQuery, that reason is that you want your app to work well. Blindly reaching for a tool from the static age will bite you.

> But unless you made a meaningful discovery that can add to the conversation, you don't need to make another blog post about it. Ugh.

Guessing this is yours ;)

[ Parent | on HN ]

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

My reply was a little rough. I just get frustrated because I remember when I was 'new' and would've taken articles such as this as sacrosanct.

I just think we have to be careful whenever we say "this is bad, do this instead" because people will often inherently believe you and pass it on.

[ Parent | on HN ]