linux user wrote:
> Lets face it, no corporate would want to spend many many man hours debugging
> concurrency related problem and won't adopt anything that is not thread
Really? And why do you think that? While I do agree that thread safety
would be a nice addition to rails, it's far from being the most
important, or the single barring issue to corporate adoption.
Right now rails is simple to code -- the user doesn't have to worry
about concurrency issues, since there's no concurrency at all. And
contrary to what people usually think, that doesn't hinder scaling,
unless we're talking about an application with a -really- high
concurrency level -- the likes we don't see every day.
As closing words, I'm with David on this subject. We don't need