Dave Ferguson's Blog

TweetBacks

Comments

• #1 by Emmit on 11/5/10 - 3:41 PM

  

  Railo is buggy. There are significant outstanding bugs in the bug tracker that have not been resolved for over a year. You have no idea when you are going to run into a show stopper bug and have no guarantee that it will ever be fixed.

• #2 by David Boyer on 11/5/10 - 5:09 PM

  

  @Emmit,
  
  Railo is open source though, so you have the choice of paying for Railo support and getting it fixed that way, fix it yourself or prove that the bug is important enough to be prioritised (see the railo uservoice site). Remember that they have to make a living and focus on what their paying customers want (just like Adobe) fixed, then they'll see what issues are affecting most of the community.
  
  Adobe aren't perfect either. Sometimes they'll seem to sit on bug reports for a while, even waiting until the next major version before looking into them. The main difference is Adobe doesn't have to be as open as Railo about it.
  
  I like both of them. I use Adobe ColdFusion is my work place and love using Railo outside of work. All I wish is is that Adobe would be a bit more responsive to informing people what's happening with bugs they've logged and that Railo catch up on certain functionality (which I think 3.2 will).

• #3 by spills on 11/5/10 - 5:56 PM

  

  @Emmit
  It's obvious you don't keep up with the current state of Railo development, as currently Railo 3.2 even in preview release is rock stable. What example do you have of Railo being buggy? The bugtracker imho is a little outdated on some issues, as quite of few them have been resolved but, not marked resolved. I have gone ACF free and have not looked back. ACF still relies on Jrun which for all intensive purposes is dead and needs to disappear. I can't remember how many times my CF server would mysteriously stop working because of memory management issues -- I don't have that with Railo.

• #4 by Jeff Gladnick on 11/6/10 - 12:56 AM

  

  We've been using Railo in production for years now on http://www.GreatDentalWebsites.com I've yet to have any show-stopper bugs that suddenly appeared in production.
  
  Sure there were occasional inconsistencies, especially when porting over open source projects written for CF (sometimes with sloppy code that CF allowed to pass), but that sort of thing was caught and dealt with during development.
  
  I think I have found one or two bugs over the 4 years I've been using Railo now, but its always been in production, and bug patches have come QUICKLY from the railo guys

• #5 by Steve on 11/8/10 - 5:03 AM

  

  to be fair, the article is not on the blog, it is a pages on the site with comments enabled for the purpose of providing productive feedback. Any site owner has a responsibility to moderate comments and remove anything offensive this is normal, and it is pretty obviously that a lot of the initial feedback to that article was offensive and not productive as it spilled over on to twitter. When I come across articles full of people arguing and flaming each other, I don't bother reading them, so they serve no purpose other than to spoil it for anyone who did post anything productive as their comments probably wont get read.