Sorry to "Gravedig" but it is a sticky. (I don't see the problem with gravedigging anyways on a forum).
Originally posted by Rad:
Believe it or not I tried to get people to check out Ruby on Rails about two years ago.
You crack me up. You realize that 2 years ago it was basically unstable and just starting out? I've never encouraged anyone to use software that early in development for production purposes. Hence everyone thinking you're nuts for telling them to use it in a production enviroment.
As of 1.0 however, it is much more stable and versatile. I don't think I would of cared for Rails much if I started on it around the 0.2 stages.
So yeah Rad, just because you like using software not fit for production purposes at the time, doesn't mean others do. I think that would of been Scott's point back then.
Originally posted by Rad:
What's interesting is that the people are not thinking for themselves all of the sudden, it's just that the general opinion of Rails has switched from a "it's not in PHP it must be evil" framework to "this is actually something interesting and useful." I guess it's my fault for expecting an open mind.
You'd fall in the same bandwagon in a sense. You just had the advantage of using Ruby before 'Rails' was around. So I clearly think you're misjudging the general perception of the entire ordeal. IMO, Rails wasn't 'fit' for production work and was looked at as alpha/beta software (it was, get over it). Why go from a production suitable enviroment (PHP as an example at this time) to a bleeding edge development enviroment?
It's a question of stability and no stability. You even complained about how TextDrive was with all of the bleeding edge technology they had running and how slow or 'unstable' it was. Same principle applies to asking someone who is learning or currently applying PHP to a production enviroment and you're spouting off to learn an alpha/beta framework in an entirely different language (not easy to just 'do').
Now that Rails is actually in the 1.0 phase (once again), people are trying it out for shits (that's how I started) and are actually coming to terms with it's benefits and disadvantages. You're always going to have the select few who go by the 'hype' or the 'coning'. It's easy to go with someone elses opinion for some people apparently, but that doesn't mean 'everyone' is like that.
A lot of the comments come from the stupid screencasts (yes, they're dumb). About how you can make a blog in what, 57 lines? Whoopde doo, that's all marketing hype of the easyness and 'power' of Rails. So you're always going to have different types of people, but I believe the general consensus two years ago would of been to use PHP4 over Rails 0.1-3, I can't recall what it was entirely 2 years ago, I just know it was 'very' new.
An open mind would be understanding this, not expecting others to follow your opinion.
Originally posted by Rad:
Maybe it's just me being cynical.
Maybe you should fix that.
___________________
The Audoptic Weblog. It's where the magic happens.
Last edited by Locke, May 4th, 2006 09:34 PM (Edited 2 times)
April 11th, 2006 
I've done PHP, Perl, RoR and Java/J2EE with the right tools remains my favorite. My last job was J2EE but this one is PHP. Honestly, I'd say try PHP or Ruby first, then move on up to Java if you're looking to take it a bit further (and make more money). 
