3 May 2008 - 9:02am, Luigi Montanez (not verified) said:
As a developer, I would never, in a million years, write a blog post supposing that I know how to build an application better rather than the actual developers who have worked on it for the past two years.
What if I told you how to do your job? What if I went into that post about your Drupal commenting being buggy and told you, "Yeah, it's really not that hard to get Drupal commenting to work. Just follow these three one-sentence steps and it'll work right quick."
You never know what goes into any project or application unless you actually work on it. Or, at the very least, do at least some research about it. If you did, you would have found out that Twitter's core does in fact run on a message queue system that's not Rails at all, but pure Ruby:
Unbelievably disrespectful
As a developer, I would never, in a million years, write a blog post supposing that I know how to build an application better rather than the actual developers who have worked on it for the past two years.
What if I told you how to do your job? What if I went into that post about your Drupal commenting being buggy and told you, "Yeah, it's really not that hard to get Drupal commenting to work. Just follow these three one-sentence steps and it'll work right quick."
You never know what goes into any project or application unless you actually work on it. Or, at the very least, do at least some research about it. If you did, you would have found out that Twitter's core does in fact run on a message queue system that's not Rails at all, but pure Ruby:
http://dev.twitter.com/2008/01/announcing-starling.html
Daemons, asynchronous messaging, memcached. Sounds like your first three bullet points right there. Pardon them if they don't follow your fourth.