Comments on: Ruby on Rails http://mfischer.com/wordpress/2008/08/07/ruby-on-rails/ the personal blog of Mike Fischer Fri, 30 Dec 2011 21:51:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Nick http://mfischer.com/wordpress/2008/08/07/ruby-on-rails/comment-page-1/#comment-176 Nick Sat, 16 Aug 2008 14:02:36 +0000 http://www.mfischer.com/?p=281#comment-176 When you figure out the magic time saving feature, let me know :) So far, I've only found the frustration features in both ROR and Django When you figure out the magic time saving feature, let me know :) So far, I’ve only found the frustration features in both ROR and Django

]]> By: Scott Nolan http://mfischer.com/wordpress/2008/08/07/ruby-on-rails/comment-page-1/#comment-172 Scott Nolan Sun, 10 Aug 2008 13:47:51 +0000 http://www.mfischer.com/?p=281#comment-172 Ruby on Rails, JBoss or Tomcat using Java, ColdFusion... Blow and LISP... they all seem like nuisance buzzword laden frameworks that don't do anything C and RPC calls couldn't do 15 years ago. The only difference seems to be that the developers of bits of code on different machines no longer have to talk to each other like they used to with C and RPC calls... So is a web application framework really saving money or time or making things easier? I guess machines and memory and storage are so cheap that the extra bloat needed to facilitate the generic API is a wash, but I find that the developers end up needing to talk to each other anyway because they still need to figure out how their bit of code on server A needs to talk to the other developer's bit of code on server B within the generic "easy-to-use" API... meaning... nothing is really changed. It's not that much easier... and coders still need to work together and agree on inter-process communication. Full disclosure: I am in Operations at a small company deploying bits of code in C, JBoss, WebLogic (Legacy, going away soon), and Rails now... and somehow we in Ops keep getting called in to referee the conflicts between the Java and Ruby camps... not that we really care; as all we want are stable applications that are easy to run in production. Ruby on Rails, JBoss or Tomcat using Java, ColdFusion… Blow and LISP… they all seem like nuisance buzzword laden frameworks that don’t do anything C and RPC calls couldn’t do 15 years ago. The only difference seems to be that the developers of bits of code on different machines no longer have to talk to each other like they used to with C and RPC calls…

So is a web application framework really saving money or time or making things easier?

I guess machines and memory and storage are so cheap that the extra bloat needed to facilitate the generic API is a wash, but I find that the developers end up needing to talk to each other anyway because they still need to figure out how their bit of code on server A needs to talk to the other developer’s bit of code on server B within the generic “easy-to-use” API… meaning… nothing is really changed. It’s not that much easier… and coders still need to work together and agree on inter-process communication.

Full disclosure: I am in Operations at a small company deploying bits of code in C, JBoss, WebLogic (Legacy, going away soon), and Rails now… and somehow we in Ops keep getting called in to referee the conflicts between the Java and Ruby camps… not that we really care; as all we want are stable applications that are easy to run in production.

]]>