Three Years of Real-World Ruby
Recorded at:
- Share
-
- |
Read later
My Reading List
Bio
Martin Fowler is an author, speaker, consultant and general loud-mouth on software development. He's the Chief Scientist at ThoughtWorks - an international application development company, and has written five books on software development and also writes articles regularly on http://www.martinfowler.com/ .
QCon is a conference that is organized by the community, for the community.The result is a high quality conference experience where a tremendous amount of attention and investment has gone into having the best content on the most important topics presented by the leaders in our community. QCon is designed with the technical depth and enterprise focus of interest to technical team leads, architects, and project managers.
- Sections
- Process & Practices
- Architecture & Design
- Development
- Topics
- application performance management
- Agile Techniques
- DSLs
- Adaptive Leadership
- Testing
- Ruby
- Domain Specific Languages
- Project Management
- Performance & Scalability
- Mingle
- ThoughtWorks
- Dynamic Languages
- Performance Tuning
- JVM Languages
- Scalability
- Ruby on Rails
- JRuby
- Leadership
- QCon London 2009
- Agile
- Java
- Performance
- QCon
Text article available
by
Martin Fowler
Re: Text article available
by
andrew mcveigh
Has there been any sampling on whether the use of ruby is more advantageous in the creation/early stages of a project, relative to the later maintenance and upgrade phases?
Andrew
Not working
by
Michael Furtak
Re: Not working
by
melih birim
Nice talk ... but
by
Ali Motaz
that I enjoyed it greatly!
Martin presented his ideas clearly, and in case you never heard of him before
he is a UML and Agility hotshot, in a good way!
41 Ruby project by a reputable company is something any new technology can aspire
for, definitely good PR for Ruby and Rails
But the funny thing is, and if you think like I do, the bad things about Ruby,
which Martin highlighted in the talk are really, really, really terrible.
1. Ruby have a bad implementation.
Whats news to me was that Matz according to Martin doesn't have the skill to change this!
2. Ruby is slow.
But what you can read through the lines is , ThoughtWorks is trapped with 41, its a little too late to turn back to something else.
And the excuse that it's ok for a program to perform bad if it was written quickly seem hard to swallow.
OCaml at least one choice that offer high level abstraction and good performance.
3. He says that the bottle neck is the DB, and that they don't have the skills to fix this.
In many ways, Martin really admitted this in his talk, to defend Ruby's slowness he suggest that the problem and bottle neck are normally elsewhere like in the DB, and then he goes to say that mingle is slow! Which just means they don't know how to write fast DB applications, which is weird!
4. We deliver slow application to our customers! And they don't mind.
Presumably because they are delivered fast! Well, all I can think of is, they got lucky booking customers who are not demanding!
Personally I never met a customer who like slow application!
I do notice that number 3 and 4 and not really about Ruby, but what I am thinking is that they used Ruby to deliver these bad things. And they are tolerating it because of Ruby. Which at least fro me creates a bad association
Finally, all I wonna say is, after this talk, you might feel not so enthusiastic about Ruby.
Would not it have been better if he explained how he created fast performing application, and how his customers live the speed. And how speed in doing things changes perspectives and potential.
But he didn't, because they didn't!
Re: Text article available
by
Martin Fowler
Re: Nice talk ... but
by
Martin Fowler
On most of our applications the DB is the bottle neck, so Ruby's slowness isn't important. Mingle is an exception, but in that case they feel that rapid feature delivery is worth the need for more hardware.
Re: Not working
by
Floyd Marinescu
Re: Nice talk ... but
by
Jim Riley
Ruby/Rails may not be the perfect fit for all projects and teams. I think the presentation provides provides good information for determining where, who and how to apply Ruby/Rails.
"Is Ruby Slow?"
by
Lavir the Whiolet
A few more qs.
by
Manoj Waikar
(1) Does the increasing popularity and maturing of languages like Clojure, change anything for your company's approach towards Ruby (because Ruby is slow)?
(2) Do you foresee TW using Lisp or Clojure or say, some of the functional languages in the near future?
Re: A few more qs.
by
Rodrigo Piovezan
The fact that Ruby on Rails has been indicated as a more productive environment than usual choices such as JEE or .NET in three years worth of projects, despite these issues, is certainly a great thing. It is difficult to see Ruby's slowness as an issue, since even Java was once like that, and look at how influent Java is in the enterprise market nowadays.
Regarding the learning curve, you mentioned that the teams were slow at the beginning (as expected with any new technology). Progressing through the "Improvement Ravine" had a relationship with their background on other scripting/dynamic languages and also with achieving the right attitude towards meta-programming. Perhaps I just didn't understand all the gathered data, but I could not visualize how steep this learning curve is. I think it would be really useful if you could provide some kind of feedback on this, and how it affected the teams' productivity at the early stages, this way people could have more realistic expectations on the outcome of adopting these technologies. How long until a JEE or .NET team can become productive on RoR?
Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think