I echo this exactly, except I went with the 15" mbp.
My work actually lets me take it to work and use it instead of the 500$ cookie cutter pc junker they hand out.
Re:Slashdot - Where Rails gets the hype.
on
Ruby For Rails
·
· Score: 1
Is Ruby and Rails worth the attention of developers?.... Yes
Is it a silver bullet?... NO
The Rails core team is actually pretty open and vocal about Rails being designed to solve a niche problem. They believe that this focus is what will allow Rails to ultimately make the uber complex, try-to-solve-everything frameworks of Javaland seem utterly cumbersome.
Anyway, Ruby does need maturity.. that's the one thing I see as Java's biggest advantage at this point, but I agree with DHH that the time to maturity for Ruby will be much shorter than it was for Java.
Re:Slashdot - Where Rails gets the hype.
on
Ruby For Rails
·
· Score: 1
*RoR is a framework for making web applications THATS IT.*
Oops, no, you're wrong. It's not. Rails includes really nice Web Services support, making it more than just a "web page framework". Labelling it so is just Java fanboy ignorance. (I was the same way 6 months ago...) ROR will fit in nicely in a service oriented architecture, which is where my company is piloting it right now. Using ROR for web application development and wherever we require legacy integration (MQ, DB2 7 Stored Procs, etc.), we can call a Java web service. Not to mention Rails has the full power of the Ruby language and it's libraries... (Ruby is the real star, here)
I like to point out where Java was a year after it's release... I'm betting that in a few years the Ruby movement will have grown quite considerably, but hey, I could be wrong and Java might reign supreme for the next 20 years.
Re:Slashdot - Where Rails gets the hype.
on
Ruby For Rails
·
· Score: 2, Insightful
Rails ain't hype, as a fulltime Java programmer who got a little too curious, I can tell you that this is the real deal.
I dislike people who discount other languages and frameworks just because it isn't their favorite framework they've been using. Attachment is an awful trait in the programming industry.
I won't discount any of the frameworks you've mentioned because I simply havn't used them, but in comparison to Java frameworks I've used for many years, Rails blew them all away. I see a bright future for Ruby, Rails, and other Ruby based frameworks.
On topic, this is a good book for those who have spent some time with Rails and want to dig into the underlying (and magnificent) Ruby language. I met David Black at a PhillyOnRails user group meeting and actually got a signed copy of his book. Good stuff!
Slashdot Mirror
I echo this exactly, except I went with the 15" mbp. My work actually lets me take it to work and use it instead of the 500$ cookie cutter pc junker they hand out.
Is Ruby and Rails worth the attention of developers?.... Yes
Is it a silver bullet?... NO
The Rails core team is actually pretty open and vocal about Rails being designed to solve a niche problem. They believe that this focus is what will allow Rails to ultimately make the uber complex, try-to-solve-everything frameworks of Javaland seem utterly cumbersome.
Anyway, Ruby does need maturity.. that's the one thing I see as Java's biggest advantage at this point, but I agree with DHH that the time to maturity for Ruby will be much shorter than it was for Java.
Oops, no, you're wrong. It's not. Rails includes really nice Web Services support, making it more than just a "web page framework". Labelling it so is just Java fanboy ignorance. (I was the same way 6 months ago...) ROR will fit in nicely in a service oriented architecture, which is where my company is piloting it right now. Using ROR for web application development and wherever we require legacy integration (MQ, DB2 7 Stored Procs, etc.), we can call a Java web service. Not to mention Rails has the full power of the Ruby language and it's libraries... (Ruby is the real star, here)
I like to point out where Java was a year after it's release... I'm betting that in a few years the Ruby movement will have grown quite considerably, but hey, I could be wrong and Java might reign supreme for the next 20 years.
Rails ain't hype, as a fulltime Java programmer who got a little too curious, I can tell you that this is the real deal. I dislike people who discount other languages and frameworks just because it isn't their favorite framework they've been using. Attachment is an awful trait in the programming industry. I won't discount any of the frameworks you've mentioned because I simply havn't used them, but in comparison to Java frameworks I've used for many years, Rails blew them all away. I see a bright future for Ruby, Rails, and other Ruby based frameworks. On topic, this is a good book for those who have spent some time with Rails and want to dig into the underlying (and magnificent) Ruby language. I met David Black at a PhillyOnRails user group meeting and actually got a signed copy of his book. Good stuff!