This is when Java programmers smugly proclaim why their ecosystem is superior

(written by Lawrence Krubner, however indented passages are often quotes)

Taryn East writes:

and when I ran my fresh new rspec spec over it -> which looks somewhat like:

it “should raise an error if we don’t pass a thing” do
lambda {
my_class = MyClass.new(:thing => nil)
}.should raise_exception(RuntimeError)
end
I kept getting something weird:

expected RuntimeError, got
#>
You may already have spotted the problem… ah, single-character bugs, doncha love em?

Here it is.

WRONG:
raise RuntimeError “must have a thing!” unless thing.present? && thing.is_a?(Thing)
RIGHT:
raise RuntimeError, “must have a thing!” unless thing.present? && thing.is_a?(Thing)

At some point a Java programmer will read this and snort smugly something about the superiority of compiled languages with stricter syntax rules.