Hi! On 2008/05/12, at 21:16, Mike Schrag wrote:
For the vast majority of apps, I don't believe people will notice the brokenness, but I do agree that it is broken. The fix, unfortunately may be worse than the brokenness.
<voice of that irritating guy in Southpark>Concurrency issues are bad, uhhkeey? They must be fixed, uhhkeey? Don't say the fix is worse or they won't fix them, uhhkeey?</voice> :)
EOF and WO have some really great features. Awesome EOF performance characteristics is, unfortunately, not really one of them. Again, though, for most apps, it doesn't really matter. But when you want to push it, it's something you have to be considering. This is why I don't laugh at Twitter having problems with Rails. You go make an app that handles 11,000 requests per second and come back and talk to me about how awesome your framework is. Scaling is hard, and I don't care what framework you develop in, you're going to sell your beautifully-designed-api-soul to make it scale.
I'm not even sure if the core of twitter is Rails or not. But as you say, it doesn't matter. Scaling is a nightmare. Makes me nervous (as almost everything, including concurrency issues, that must be fixed!).
Yours Miguel Arroz Miguel Arroz http://www.terminalapp.net http://www.ipragma.com
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
