Well, I hardly think they’d be pulling numbers out of the air, and their figures tally pretty well with a number of other sources. Do you have some alternative source of data to back up your claims? Presumably you’re basing your opinion that IE6 and IE7 are still popular on something? As for, “what does it really show?”, it shows exactly what I said in my previous post, which you ignored. It shows that, contrary to your original claim, significant numbers of IE7 users switched to IE8 even before they were required to do so by an OS upgrade. It shows that, when you said, “IE9’s adoption will be tied directly Windows8’s adoption”, you were wrong. It shows that IE7′s market share has 20% in the last year alone, and will likely be gone within a year, way before IE9 is released. Will we have to keep supporting older browsers? Yes, that’s just part of being a web developer. If you don’t like it, stop whining and go program desktop apps. But these figures show there is reason to be optimistic that within a year or so the browser landscape will look a lot different.

By the way, the graph on that page would have looked much better if they drew it with SVG. Can you think of three reasons why didn’t?

About an example of usage, we are releasing soon the beta of our product. Everything (except the google apps obviously) are generated through PURE: http://beebole.com/en/blog/beebole/google-chart-tools-timesheet-report/

Notice the speed. There is a as well a mobile version that has impressive rendering speed too. We’ll release a vid too.

If you use it, feel free to drop a message on the forum: http://groups.google.com/group/Pure-Unobtrusive-Rendering-Engine

Similar performance? Chrome 5 and Opera 10.5 look to be 2x faster than IE9

Not true, according to the chart and associated figures, the platform preview MS just released is faster than Firefox 3.7 Alpha 2.

However, talking about which browser is “faster” now isn’t very valuable. All browsers have implemented JIT and have converged on a similar level of performance. The differences between the latest versions of each isn’t significant enough to make much difference at all, which is a good thing for developers.

@okonomiakyi3000

Rant much? Unfortunately your spiel isn’t backed up by the actual market share statistics. They show IE7 certainly did “make a dent”, as it was the most popular web browser in the world this time last year. Furthermore, its market share began sharply declining as soon as IE8 was released, way before Windows 7 was available, proving that significant numbers of users are upgrading their browsers independently of upgrading the OS.

@ragjunk PURE has a mode that totally separates HTML and JS, as described here: http://beebole.com/pure/documentation/unobtrusive-really/

“IE9 to be faster than FF 3.7 who would have expected that…”

Nobody, since Firefox 3.6 is currently faster than IE 9. See the IE blog for charts on this.

Also note that Firefox 3.7 alpha 3 will also have hardware acceleration (Direct2D) support.

More importantly, why do we care about any announcement regarding IE9? Because we want IE to support SVG, Canvas, HTML5, etc? IE9 will not make older versions of IE support these things and it will not make older versions of IE go away. IE8 is killing IE6 only because it ships with Windows7 and no matter how bad Windows7 is, most XP users have held out as long as they can so they’ve accepted that “better than Vista” == “good enough”. IE7 didn’t make a dent because it shipped with Vista. The fact is that the vast majority of IE users don’t know what a browser is or why they should upgrade or how to do so. IE9′s adoption will be tied directly Windows8′s adoption, it will further erode IE6 and IE7 but it will hardly touch IE8′s numbers. We can count on Mozilla and Webkit users to be pretty much up to date but we must always expect a significant number of IE users to be at least 2 generations behind. So expect to be able to make use of any fancy new IE9 features in about 6 years but also expect that you’ll still be dealing with whatever bugs and limitations IE9 suffers from for much longer. Or, you know, learn from the past.

$(“#results”).tmpl(“productTemplate”, product);

Shouldn’t it? The setting html part of it is understood.

PS: I don’t work for Beebole; I just use this engine in my work, which is the best templating engine, IMO.

And “with new features from HTML5+” just sound like: “uhm, we will implement this one, and this one, and maybe this one… oh, and this one we will say we did, but we wont… maybe in a patch in 2011… and the rest we won’t do but we will blame potential security flaws…”

Yes, I “love” IE…

As soon as you want to do anything like grown-up, however, things get a lot more convoluted, and that’s when Microsoft code fails.

Every time.

also see http://wiki.github.com/nje/jquery/jquery-templates-proposal#discussion
“Templates should be Real DOM Elements”
the example contains a template with an img tag. The against is that templating with real dom elements would cause the img tag to request an invalid url. this is all well and good but they forgot to notice the id attribute of the main template container which will be rendered N times breaking id related selectors related to the template anyway. Using the need to protect someone from an img tag is a bad argument against the dom based method when they ignore simple rules like id’s should only appear once per document.

Templating with strings is also slow compared to dom base approaches because you cannot clone and modify only the dom elements you need.
With a string based approach inner html will have to be used to expand each populated template into dom elements before it can be appended to a document or document fragment.
Rendered callbacks are a good idea because you can use the dom manipulation approach but on a str based foundation you wouldnt have any sort of optimization from this.

It would be very interesting however if they would expand/compile the template+template psuedo code into javascript where str replace templating could become competitive performance wise. But then again do we really need more psuedo code when js can handle this sort of thing really well and one of the main reasons why jQuery is so popular?