Curiouser and Curiouser! on greasemonkey http://matt.blogs.it/ RSS feed for topic greasemonkey Copyright 2006 Matt Mower Squib/0.1 self@mattmower.com self@mattmower.com en-gb A squirt of grease is good for Rails Sat, 30 Jul 2005 12:03:22 +0100 <p>I've just installed <a href="http://blog.monstuff.com/">Julien Couvreur's</a> <a href="http://blog.monstuff.com/archives/images/XMLHttpRequestDebugging.v1.0.user.js">XmlHttpRequestDebugging</a> script for <a href="http://greasemonkey.mozdev.org/">GreaseMonkey</a>. I've been using Safari since I <a href="http://matt.blogs.it/2005/06/24.html#a1873">switched</a> because it looks so much nicer than Firefox but as I starting trying to debug some Ajax stuff in a Rails app I'm working on I found myself reaching for FireFox and it's more capable developer tools. Then, by chance, I remembered that someone had worked on an Ajax debugger and that lead me to Julien's script.</p> <p>What can I say? Thank you Julien, great work . This is a tip top tool.</p> http://matt.blogs.it/entries/00002804.html Hands up Safari!! Tue, 04 Oct 2005 17:36:50 +0100 <p>I keep hearing people talking about how <a href="http://webkit.opendarwin.org/">Safari</a> is dreadful, crap, what have you. I guess that, since I installed <a href="http://haoli.dnsalias.com/Saft/index.html">Saft</a>, i've not felt that. It looks nice, it seems fast and, if the history and bookmarks leave something to be desired, well there's always version 3. And <a href="http://greasemonkey.mozdev.org/">GreaseMonkey</a>? Who needs it when I have <a href="http://redhanded.hobix.com/inspect/theMouseholeProxy.html">MouseHole</a>? (Check it out, it's very cool).</p> <p>However, lately, I've been starting to feel that Safari is indeed cursed. One thing it seems prone to do <strong>a lot</strong> (for a MacOSX app) is crash.</p> <p>It seems that all my crashes happen at around the same point: between Safari starting and finishing loading a page. If I try and stop it, if I click a link before it's finished, or try to go back before it's finished. Well there seems to be a good chance it will crash.</p> <p>Again, Saft limits the damage by recovering the lost page addresses (if not any dynamic or form content). But you have to wonder why that feature got implemented. Was it, by any chance, because Safari crashes regularly?</p> <p>To keep things in proportion this doesn't happen that often, largely because I am learning to be patient and let Safari finish loading a page before doing anything. Also a crash on MacOSX always seems so much less serious than Windows. The app crashes, I report it, then I run it again and all is well. I've not yet seen one crash lead to anything worse.</p> <p>If I had one wish for MacOSX 1.4.3 it would be a more stable Safari.</p> http://matt.blogs.it/entries/00002974.html