Comments on: jQuery and Performance: What is ‘this’? http://www.erichynds.com/jquery/jquery-and-performance-what-is-this/ Web Developer's Ramblings on JavaScript, jQuery, ColdFusion, MySQL, and other technologies. Wed, 04 Jan 2012 16:01:00 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Tim Branyen http://www.erichynds.com/jquery/jquery-and-performance-what-is-this/#comment-1946 Tim Branyen Tue, 02 Feb 2010 16:03:49 +0000 http://www.erichynds.com/?p=173#comment-1946 Regarding premature optimization, I don't think anyone is claiming to refactor code to use this approach. I do, however, feel its prudent as a client side coder to know where performance can be improved, without taking away from the readability. While many of us are on quad core machines that show minute differences with events. Its very likely a user could be on an older machine that stands to gain. I agree with premature optimization being an unnecessary step in the development cycle, but with this new knowledge, it instead becomes good practice. I also noticed through some testing of my own that getElementsByTagName performed faster than access forms and images through dot-notation. Regarding premature optimization, I don’t think anyone is claiming to refactor code to use this approach. I do, however, feel its prudent as a client side coder to know where performance can be improved, without taking away from the readability. While many of us are on quad core machines that show minute differences with events. Its very likely a user could be on an older machine that stands to gain.

I agree with premature optimization being an unnecessary step in the development cycle, but with this new knowledge, it instead becomes good practice.

I also noticed through some testing of my own that getElementsByTagName performed faster than access forms and images through dot-notation.

]]> By: Tim Branyen http://www.erichynds.com/jquery/jquery-and-performance-what-is-this/#comment-3897 Tim Branyen Tue, 02 Feb 2010 16:03:00 +0000 http://www.erichynds.com/?p=173#comment-3897 Regarding premature optimization, I don't think anyone is claiming to refactor code to use this approach. I do, however, feel its prudent as a client side coder to know where performance can be improved, without taking away from the readability. While many of us are on quad core machines that show minute differences with events. Its very likely a user could be on an older machine that stands to gain. I agree with premature optimization being an unnecessary step in the development cycle, but with this new knowledge, it instead becomes good practice. I also noticed through some testing of my own that getElementsByTagName performed faster than access forms and images through dot-notation. Regarding premature optimization, I don’t think anyone is claiming to refactor code to use this approach. I do, however, feel its prudent as a client side coder to know where performance can be improved, without taking away from the readability. While many of us are on quad core machines that show minute differences with events. Its very likely a user could be on an older machine that stands to gain.

I agree with premature optimization being an unnecessary step in the development cycle, but with this new knowledge, it instead becomes good practice.

I also noticed through some testing of my own that getElementsByTagName performed faster than access forms and images through dot-notation.

]]> By: JAlpino http://www.erichynds.com/jquery/jquery-and-performance-what-is-this/#comment-1799 JAlpino Mon, 11 Jan 2010 23:35:28 +0000 http://www.erichynds.com/?p=173#comment-1799 Like any type of app development, it's best not to get caught up in pre-mature optimization. So @Adam, if your app is not heavy on the client side, then taking optimization steps such as using the dom properties directly vs. jQuery calls, then it might not make sense to switch. However, if that's not the case then applying these performance measures will help, even if the calls span over time rather than all at once. Like any type of app development, it’s best not to get caught up in pre-mature optimization. So @Adam, if your app is not heavy on the client side, then taking optimization steps such as using the dom properties directly vs. jQuery calls, then it might not make sense to switch. However, if that’s not the case then applying these performance measures will help, even if the calls span over time rather than all at once.

]]> By: JAlpino http://www.erichynds.com/jquery/jquery-and-performance-what-is-this/#comment-3896 JAlpino Mon, 11 Jan 2010 23:35:00 +0000 http://www.erichynds.com/?p=173#comment-3896 Like any type of app development, it's best not to get caught up in pre-mature optimization. So @Adam, if your app is not heavy on the client side, then taking optimization steps such as using the dom properties directly vs. jQuery calls, then it might not make sense to switch. However, if that's not the case then applying these performance measures will help, even if the calls span over time rather than all at once. Like any type of app development, it’s best not to get caught up in pre-mature optimization. So @Adam, if your app is not heavy on the client side, then taking optimization steps such as using the dom properties directly vs. jQuery calls, then it might not make sense to switch. However, if that’s not the case then applying these performance measures will help, even if the calls span over time rather than all at once.

]]> By: Adam Koch http://www.erichynds.com/jquery/jquery-and-performance-what-is-this/#comment-1796 Adam Koch Mon, 11 Jan 2010 14:20:24 +0000 http://www.erichynds.com/?p=173#comment-1796 Sure, but this is for 20-50k times. I don't have any functions that are called that many times. Sure, but this is for 20-50k times. I don’t have any functions that are called that many times.

]]> By: Adam Koch http://www.erichynds.com/jquery/jquery-and-performance-what-is-this/#comment-3895 Adam Koch Mon, 11 Jan 2010 14:20:00 +0000 http://www.erichynds.com/?p=173#comment-3895 Sure, but this is for 20-50k times. I don't have any functions that are called that many times. Sure, but this is for 20-50k times. I don’t have any functions that are called that many times.

]]> By: Jonas De Smet http://www.erichynds.com/jquery/jquery-and-performance-what-is-this/#comment-1788 Jonas De Smet Sat, 09 Jan 2010 11:08:59 +0000 http://www.erichynds.com/?p=173#comment-1788 Wow, thanks for the great tip, there were a couple of things I didn't know! Wow, thanks for the great tip, there were a couple of things I didn’t know!

]]> By: Jonas De Smet http://www.erichynds.com/jquery/jquery-and-performance-what-is-this/#comment-3894 Jonas De Smet Sat, 09 Jan 2010 11:08:00 +0000 http://www.erichynds.com/?p=173#comment-3894 Wow, thanks for the great tip, there were a couple of things I didn't know! Wow, thanks for the great tip, there were a couple of things I didn’t know!

]]> By: Dean Hall http://www.erichynds.com/jquery/jquery-and-performance-what-is-this/#comment-1787 Dean Hall Sat, 09 Jan 2010 04:43:16 +0000 http://www.erichynds.com/?p=173#comment-1787 Seeing all the qualifiers, this seems to prove the point that jQuery (and other, similar libraries) is invaluable to developers writing cross-browser JS. Thanks for the reminder, though, that libraries also invisibly add cycles. It won't affect us much when developing sites with minimal JS that's executed once or even on occasional user interaction, but when writing complex web apps, knowing how to optimize the code that gets executed repeatedly will save your users lots of headaches. Seeing all the qualifiers, this seems to prove the point that jQuery (and other, similar libraries) is invaluable to developers writing cross-browser JS. Thanks for the reminder, though, that libraries also invisibly add cycles. It won’t affect us much when developing sites with minimal JS that’s executed once or even on occasional user interaction, but when writing complex web apps, knowing how to optimize the code that gets executed repeatedly will save your users lots of headaches.

]]> By: Dean Hall http://www.erichynds.com/jquery/jquery-and-performance-what-is-this/#comment-3893 Dean Hall Sat, 09 Jan 2010 04:43:00 +0000 http://www.erichynds.com/?p=173#comment-3893 Seeing all the qualifiers, this seems to prove the point that jQuery (and other, similar libraries) is invaluable to developers writing cross-browser JS. Thanks for the reminder, though, that libraries also invisibly add cycles. It won't affect us much when developing sites with minimal JS that's executed once or even on occasional user interaction, but when writing complex web apps, knowing how to optimize the code that gets executed repeatedly will save your users lots of headaches. Seeing all the qualifiers, this seems to prove the point that jQuery (and other, similar libraries) is invaluable to developers writing cross-browser JS. Thanks for the reminder, though, that libraries also invisibly add cycles. It won’t affect us much when developing sites with minimal JS that’s executed once or even on occasional user interaction, but when writing complex web apps, knowing how to optimize the code that gets executed repeatedly will save your users lots of headaches.

]]>