Kommentare zu: 101 on Prototype CSS Selectors

Von: Joys

Joys — Thu, 05 Jan 2012 10:46:22 +0000

I wonder how you got so good. HaHa! This is really a fascinating blog, lots of stuff that I can get into. One thing I just want to say is that your design is so perfect! Freshersworld

Von: Joys

Joys — Thu, 05 Jan 2012 10:45:46 +0000

Nice article. It really helped me when I was setting up the transactional replication. bank career

Von: Joys

Joys — Thu, 05 Jan 2012 10:44:56 +0000

I am very happy to discover your post as it will become on top in my collection of favorite blogs to visit. Brilliant article my friend, but could you teach me more detail about your post.
IT jobs

Von: soap00023

soap00023 — Sun, 25 Dec 2011 07:04:13 +0000

I wanted a way to facilitate that interaction that doesn’t involve me repeating myself over and over wiring and rewiring event ovservers to a document. This was a great article, it really helped me a lot.
nexium vs prilosec

Von: Ensuring Web Site Performance – Why, What and How to Measure Automated and Accurately « Tech Notes

Mon, 10 Oct 2011 18:56:50 +0000

[...] can very often be seen when expensive CSS Selector Lookups (check out the blogs about jQuery and Prototype CSS Selector Performance) are used or when using dynamic elements like JavaScript Menus (check out the blog about dynamice [...]

Von: How Case-Sensitivity for ID and ClassName can kill your page load time Application Performance, Scalability and Architecture – The dynaTrace Blog

Wed, 14 Sep 2011 12:17:28 +0000

[...] // Many times have we been posting the recommendation to speed up your DOM Element lookups by using unique IDs or at least a tag name. So, instead of using $(“.wishlist”) you should use $(“div.wishlist”) which will speed up lookups in older browsers. If you want to lookup a single element then give it a unique ID and change your call to $(“#mywishlist”). This will speed up lookup in older browsers from 100-200ms to about 5-10ms (times vary depending on number of DOM elements on your page). More on this in our blogs 101 on jQuery Selector Performance or 101 on Prototype CSS Selectors. [...]

Von: Hands-On Guide: Verifying FIFA World Cup Web Site against Performance Best Practices Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog)

Fri, 04 Jun 2010 14:39:18 +0000

[...] about different best practices on things like correct usage of CSS Selectors with jQuery and Prototype and showed the performance impact of bad JavaScript code and incorrect jQuery usage by analyzing [...]

Von: Selected readings for my JAX London Session Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog)

Mon, 22 Feb 2010 18:53:19 +0000

[...] CSS selectors in Prototype [...]

Von: Why Web 2.0 requires End-To-End Performance Analysis and How to Do It Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog)

Wed, 10 Feb 2010 15:01:19 +0000

[...] performance. Check out the following blog entries about the performance impact of jQuery and Prototype. It shows how important it is for developers to understand the internals of frameworks in order to [...]

Von: Ensuring Web Site Performance – Why, What and How to Measure Automated and Accurately Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog)

Wed, 13 Jan 2010 14:32:21 +0000