Skip to main content
Code Review

Return to Answer

Commonmark migration
Source Link

##I heard you like wrappers

I heard you like wrappers

So I wrapped your wrapper (jQuery) in a wrapper (your thing) so you can do ajax.

Why do you do this again??

Instead of wrapping over (slow) jQuery you could just wrap the native ajax functionality. In general I expect that to be faster. Additionally this frees your API to be changed independently of jQuery and it removes that nasty jQuery dependency at all.

Don't wrap wrappers in wrappers, unless you add significant functionality

What significant improvement does your API provide over jQuery's?

##I heard you like wrappers

So I wrapped your wrapper (jQuery) in a wrapper (your thing) so you can do ajax.

Why do you do this again??

Instead of wrapping over (slow) jQuery you could just wrap the native ajax functionality. In general I expect that to be faster. Additionally this frees your API to be changed independently of jQuery and it removes that nasty jQuery dependency at all.

Don't wrap wrappers in wrappers, unless you add significant functionality

What significant improvement does your API provide over jQuery's?

I heard you like wrappers

So I wrapped your wrapper (jQuery) in a wrapper (your thing) so you can do ajax.

Why do you do this again??

Instead of wrapping over (slow) jQuery you could just wrap the native ajax functionality. In general I expect that to be faster. Additionally this frees your API to be changed independently of jQuery and it removes that nasty jQuery dependency at all.

Don't wrap wrappers in wrappers, unless you add significant functionality

What significant improvement does your API provide over jQuery's?

replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

##I heard you like wrappers

So I wrapped your wrapper (jQuery) in a wrapper (your thing) so you can do ajax.

Why do you do this again??

Instead of wrapping over (slow) jQuery you could just wrap the native ajax functionality native ajax functionality. In general I expect that to be faster. Additionally this frees your API to be changed independently of jQuery and it removes that nasty jQuery dependency at all.

Don't wrap wrappers in wrappers, unless you add significant functionality

What significant improvement does your API provide over jQuery's?

##I heard you like wrappers

So I wrapped your wrapper (jQuery) in a wrapper (your thing) so you can do ajax.

Why do you do this again??

Instead of wrapping over (slow) jQuery you could just wrap the native ajax functionality. In general I expect that to be faster. Additionally this frees your API to be changed independently of jQuery and it removes that nasty jQuery dependency at all.

Don't wrap wrappers in wrappers, unless you add significant functionality

What significant improvement does your API provide over jQuery's?

##I heard you like wrappers

So I wrapped your wrapper (jQuery) in a wrapper (your thing) so you can do ajax.

Why do you do this again??

Instead of wrapping over (slow) jQuery you could just wrap the native ajax functionality. In general I expect that to be faster. Additionally this frees your API to be changed independently of jQuery and it removes that nasty jQuery dependency at all.

Don't wrap wrappers in wrappers, unless you add significant functionality

What significant improvement does your API provide over jQuery's?

Source Link
Vogel612
  • 25.5k
  • 7
  • 59
  • 141

##I heard you like wrappers

So I wrapped your wrapper (jQuery) in a wrapper (your thing) so you can do ajax.

Why do you do this again??

Instead of wrapping over (slow) jQuery you could just wrap the native ajax functionality. In general I expect that to be faster. Additionally this frees your API to be changed independently of jQuery and it removes that nasty jQuery dependency at all.

Don't wrap wrappers in wrappers, unless you add significant functionality

What significant improvement does your API provide over jQuery's?

default

AltStyle によって変換されたページ (->オリジナル) /