With Deepak’s instigation finally I moved one of my greasemonkey scrips to Chrome as an extension. This will be the trial period for chrome through the new year eve as earlier experience was not very great on memory footprint.
Pros of chrome extension
1. Setup – The extension setup is a breeze, create a directory, add manifest and supporting html/js/image files. Point Chrome to it and you are done. Firefox and other browsers require an explicit restart. Chrome also integrates all the “configuration” information of extension in one place, making it simpler for developer to “get it” compared to multiple file approach of Firefox.
2. Control over “interaction” – Chrome uses HTML 5 localstorage for storage. Very explicit declarative interaction with browser sandbox is defined. Communication between frames in Chrome is using a new feature of HTML5 called postMessage. One thing I needed was “way to look into localstorage contents”-I ended up using cmdline – but a debugging box on right would be neat.
3. Sandbox restrictions are explicit but little rough and would prefer more declarative approach of what is possible and not a good practice.
4. Automatic configurable updates vs update on restart for FF is neat but imho way too hacky.
Cons of Chrome Extension –
1. Deeper interaction apart from adding buttons to toolbar(browser interaction), greasemonkey’ish stuff(page actions) and themes is really “terse”.
2. My “expand-text-when-rolled-over” jquery code refused to work in popup.html.Images of png format refused to animate in popup.html
Conclusion – good 2 hours spent. Mozilla’s Jetpack is on horizon so keep options open🙂. Speed Tracer is a good thing to have on chrome. FF’s AdblockPlus and FireGestures are way ahead at present for chrome counterparts. Way to backup/restore associated extension is again something which Chrome needs to get right(I have not had time to look into associated google group postings to verify).
Update – (29/12/2009) – Chrome extension store is less organized than FF and also less “open” like Apple ‘s infamous app store’s challenges for developers.
Update-(30-12-2009)-Chrome browser throws up errors while parsing rss from http://news.ycombinator.com/rss
I bypassed the simple code(string.find(“something).each..) and had to go “find”+”addToArray”+”retrieve it later” way.
Reddit on other hand is providing valid rss.
02/01/2010-Once posted this query to chrome-extensions group – one gentleman – phistuck helped me verify that it is the problem of feed from ycombinator, which is resulting in the problem I am seeing. (head tag getting modified). He also shared a tip to look @ headers and raw response – A look at chrome://net-internals/view-cache/http://news.ycombinator.com/rss after visiting http://news.ycombinator.com/rss proved the fact that ycombinator is providing bad response.