I ran a store last year selling shirts (http://rubythreads.com/) and I managed inventory and shipped out of my garage. Any profit made on the shirts was spent on logistics. Its a rough business and I'm trying to appeal to a very specific audience. I was planning on building a new storefront and moving to a kickstarter-model for future designs, but Teespring has been totally turnkey for me so far.
Nothing is wrong with Test::Unit or Rspec or any other testing framework. I happen to like Minitest and want to use it in my Rails app. Also, the testing infrastructure in Rails 4 is built on Minitest and so minitest-rails enables its use in Rails 3.
I dislike where Rails places the tests by default, so I wanted something to support a more discoverable structure.
Its a testament to how Rails is architected that its to easy to plug in an entirely new testing framework. Yay Rails.
Confreaks is recording the conference, as well as helping us stream it. I'm working hard to ensure that we get the videos posted as soon as we can. Should be a couple weeks and not a couple months.
Why was a seven year old post resurrected for discussion here? Does anyone still believe that Ruby, even with its unbridled dynamicity, is just for tinkerers and won't work for large teams or production quality applications?
Agreed. I gave two week's notice earlier this week. This is the first time I haven't lasted two years at a company, so I am feeling a bit like a job hopper. But the reasons I'm leaving are very much about accountability without authority.