the speed is quite frankly mind-boggling.  javascript apps scream, rendering is honored appropriately, java support is dicey (keep safari handy) and the interface is really snappy.

this week gives me enough breathing room to poke at the latest firefox 3.6 build as well.  this is the default workhorse browser for 99%+ of what i do.  frankly, i don’t know what i’d do without the “it’s all text” add-on.  given the amount of wiki editing and integration with online systems that i have to handle on a daily basis.  if i could get this for chrome, i might be sorely tempted to jump ship.  firefox 3.6 carries with it the attendant hassle of a new release in terms of add-on support.  but fortunately i’ve been able to hack or cajole all the major ones for me into submission.  there’s some decided improvement in rendering speed.  but beyond that, it looks pretty much the same to me.  which is more than ok, it’s a solid performer in the workflow.

setting aside that bit of silliness on my part, i noticed something. while i was grinding out real work and answering emails between the discovery of the breakage and repair, i discovered that my work flow had developed a dependency on having an automated “checker” come back and clean up after me.

now, i’ve had this realization in the world of MSFT Word and other packages with built-in spell checkers, but clean-up of typos was one of those things that i did in a batch manner, my fingers hadn’t actually adapted to the use of an integrated spell checking function like they had in my normal work tools. (read, emacs)

i’ve always had some level of pride in having relatively decent spelling skills. but the power of ctr-; and _knowing_ what your tool would do, has had an interesting impact on my productivity. one that i’m not entirely convinced is for the best in the long term.