Ruby faster than Python and Perl! cries the headline. This is based on a benchmark that tests “i = i + 1” in a loop, so it’s a particularly useless benchmark, even in a world of benchmarks designed to test unrealistic scenarios that make the benchmark author’s product look good.
Read the rest of this entry »
From what I’ve seen, Rails’ weakest features lie in the way it prepares the test database and test data, and Ruby’s Test::Unit isn’t much better than the awful but ubuiquitous JUnit that Java developers are accustomed to. I set out this week to impose my preferences on Rails in this area, and that took some effort. Here’s what I did.
Read the rest of this entry »
For the last few days I’ve been struggling to bend Rails to my will regarding the proper way to assure data consistency. Today I made some progress. This builds upon some research I did a few months ago, and hopefully this is a more or less complete solution to the problem of making Rails work the way I want it to regarding test databases.
Read the rest of this entry »
Last year I was doing mobile development and there was interesting Linux-as-smartphone-OS stuff going on. Now I’m doing Ruby on Rails development and there’s interesting server grid stuff going on. Here’s what I’m looking forward to finding out more about (all of these are things I’ve been watching or directly researching already):
Read the rest of this entry »
Coverage tests in Ruby (with rcov) are less strict than in Java (with EMMA), so watch out - 100% coverage is easy to attain but not as meaningful.
Read the rest of this entry »
(1)
(14)
(10)
(3)
(4)
(4)
(15)
(2)
(2)
(3)
(7)
(5)
(1)
(13)
(2)
(5)
(21)
(11)
(5)
(5)
(1)
(2)
(1)
(2)
(2)
(0)
(2)
(5)
(1)
(7)
(3)
(4)
(14)
(11)
(3)
(4)
(26)
(27)
(1)
(1)
(14)
(11)
(6)
(3)
(12)
(1)
(21)
(9)
(2)
(5)
(2)
(2)
(3)
(2)
(1)
