As I wrote earlier an Autoptimize user proposed to switch from regular expression based script & style extraction to using native PHP DOM functions (optionally with xpath). I created a small test-script to compare performance and the DOM methods are on average 500% slower than the preg_match based solution. Here are some details;
So while parsing HTML with regular expressions might be frowned upon in developer communities (and rightly so, as a lot can go wrong with PCRE in PHP) it is vastly superior with regards to performance. In the very limited scope of Autoptimize, where the regex-based approach is tried & tested on thousands of blogs, using DOM would simply create too much overhead.
Doing Web Performance can be so easy, really! I was asked to do a performance analysis of a new website and one of the things I didn’t like was the fact that the footer contained social media sharing buttons using the ShareThis widget. I’m not a fan of sharing widgets in general, as they tend to slow webpage loading and rendering down and as they almost invariably come with “3rd party tracking” for behavioral marketing purposes.
Conclusion: if performance is of any importance for your website (and it should be), you really have to avoid using 3rd party widgetery!
As every boy could tell you, it’s our toys that keep us kind of young. Because of that and as I work for a telco, I can’t but regularly buy a new phone. Over the years I’ve had a.o. a Nokia 7110, a Sony-Ericsson T68i, a Qtek 9100 and I currently own a secondhand Nokia E61i. But time flies and my E61i is aging fast (maybe if I wouldn’t drop it that often …), so in a few months time I’m buying a new smartphone. Time to start shopping for pics, specs and reviews!
Smetty recently asked for advice on this topic as well, she was thinking about the Nokia E71 as a cheaper alternative to the iPhone 3G. But I won’t be buying Apple’s must-have gadget any time soon; although it has some superb features (OS, browser and that multi-touch interface), it lacks a real keyboard, has not tethering and doesn’t allow applications running in the background. And last but not least; the platform is far too closed to appeal to an open standards and open source minded wannabe-geek like me. All Windows Mobile-based devices are banned from my shortlist as well; I really don’t like the OS and its GUI, it feels too much like Windows 3.11 to me.
I’ll probably end up buying either the Nokia E71, a HTC Dream (the Google-phone) or the Palm Pré. So let’s do a pro&con-list, comparison-tables are always fun, no?
How about battery life (rumours claim 1150-1350 mAh, combined with power-hungry HVGA)?
Not available yet, no release date announced (not for USA, and certainly not for Europe)
The conclusion: although it still is vaporware, there’s some extreme chemistry going on between me and that darned Palm Pré. It’s the most exciting device by far and if it is for sale in Belgium, it’ll be hard to resist. The HTC Dream doesn’t seem to do it for me, no chemistry on one hand and not the “safe choice” either, as that award is easily claimed by Nokia E71. So Palm Pré if available in June/July, Nokia E71 otherwise?