Not sure if you’ve heard, but Google released a new web browser today they are calling “Chrome.” We’re big fans of Google at EasyBib - we use the Google Apps suite of tools for all of our internal business needs, we use Google search (obviously), and so on - so Chrome was something we were excited to check out.
On that basis alone, I’d encourage anyone who is interested to at least check it out. I’m a FireFox user, but I’m likely going to switch to this. Internet Explorer users, Chrome is worlds ahead of what you’re used to.
So why am I writing this post? Well, new browsers always have implications for Web developers, especially new browsers launched by a company with Google’s reach.
The biggest concern is interface stability: Web browsers can interpret a site’s code differently, which could have far reaching implications for how a Web site looks. For instance - we spent a lot of time making sure our site looked the same in IE and Firefox, but there are minor issues that are still not perfect. Adding another browser in the mix could complicate matters.
Fortunately, Chrome uses Webkit, which Apple’s Safari is also based on, and our pages render well. So that’s one concern neutralized.
The thing that I was most interested in, however, was something new Chrome is bringing to the table. This is the Chrome Task Manager, which is basically a way for users to tell with Web sites are hogging all their memory. We’ve all been in situations where our browsers freeze and crash, and we don’t know why. Well, Task Manager is a way of figuring out which Web sites are naughty and which are nice.
So how does EasyBib perform?
Here’s the screenshot - When I first load the EasyBib site, it loads about 11MB of memory, but then goes down to about 7MB. As I use the site, it hovers around 10MB. I’ve included some other sites for comparison.
Overall, I think 7-10MB is pretty decent. Fellow web developers, what do you think? For your own sites, were you happy with your memory performance? Any suggestions to lower the usage number? Post your thoughts in the comments.