Recovering the journal after a less than graceful shutdown is normal behavior for xfs. That isn't an error. It also happens automatically after a set number of boots, similar to ext3. Yes, you'd see that fairly regularly in a verbose boot. It's not instability.
Any filesystem will complain about a timestamp in the future. That is repairable and recoverable as well in xfs.
I don't think anything you've described would be seen as "instability". Vector Linux offers two world-class journaling filesystems, jfs by IBM and xfs by SGI. Both are used on big iron, the very high end of commercial UNIX systems. Both are incredibly robust and stable. Ad you've pointed out yourself there is nothing faster than xfs.
The main argument against jfs and xfs is that Linux lacks some tools to manage these partitions (i.e.: resize them while leaving data intact) which do exist for ext3. That is an entirely valid reason for choosing ext3 particularly in a development enviornment like yours. I'm running ext3 on my netbook now except for the recover partition (which has Clonezilla Live installed), which is fat32 from the factory. I want to leave Ubuntu Netbook Remix (factory installed by updated/patched by me) in place. I reduced the partition size but I don't want to reformat. I want flexibility and ext3 offers the most flexibility in a Linux environment.
On my Toshiba I use xfs exclusively.