throttle

I'm gonna go against the grain on this one and call it karma whoring. Here's the formula:

1) Pick a company that has been the source of recent controversy.

2) Find a silly security flaw in one of their products that you can make sound serious with a bit of sensationalism. This should be easy to do, because most web apps have a few silly security holes.

3) Inform the company, and when they inevitably assign the silly flaw a low priority, write an inflammatory blog post and submit it to major news aggregators (e.g. news.yc)

Not hacker news.

...which further proves my point that Ruby is a bad, bad platform choice for production applications right now. You just can't have this level of insecurity, sloppiness, and unresponsiveness among the developers in a platform you would use for serious applications. Maybe one day Ruby, Rails, et al. will be ready for prime time, but it's just not now, IMO.

update: by Ruby I mean the standard Matz codebase.

Not hacker news.

The mistakes are so amateurish that it should raise questions about the rest of the codebase (i.e. the defects which are yet to be found)...

Haven't you heard about the egregious buffer overflow vulnerabilities found recently in Ruby? Not a good idea to use it for anything serious in light of those, IMO.

yea, he should definitely demand his money back...