News for hackers. Stuff that matters.
Re:Mending the Bitter Absence of Reasoned Technical Discussion by ankhmoop on Saturday April 04, 2009 @07:17PM (#546782)
"One comment that seemed particularly uncontroversial to me was at the core of this nerd firestorm: Ruby is slow. For the next several days, I could think of only one thing: why is something you can measure controversial?"

This is exactly what needed to be said, and repeated until it is fully and widely understood. Cognitive dissonance should not be assuaged at the cost of the rational and empirical.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by gleb on Saturday April 04, 2009 @08:19PM (#546844)
PR, marketing and politics are facts of life. The reasons that Ruby/Rails community ridiculed (obviously accurate) "ruby is slow" are exact same reasons the community was such a success in the first place. Consider what would have happened if "ruby is slow" meme took off. Forget the RoR itself, but it would have actually been a disservice to users who don't understand the details and wouldn't have been able to make the right choices.

If you actually want to affect a change with communication it's useful to think through what, where and how you say it. But mostly, don't just complain, include a patch. E.g. our Ruby and RoR patches were accepted the same day with gratitude: http://blog.pluron.com/2008/01/ruby-on-rails-i.html

We (Pluron/Acunote team) are going to be presenting @ RailsConf 2009 ( http://en.oreilly.com/rails2009/public/schedule/detail/8615 - Advanced Performance Optimization of Rails Applications ) and it's going to take some work to frame the presentation in a useful fashion. As tempting as it is just to point out how bad every single part of the stack is, from our hosting to Firefox, it would be highly misleading; they are still the best available options.

Having said that, it's a pleasure to have HN where these sensitive topics can be discussed in a rational fashion.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by ankhmoop on Saturday April 04, 2009 @08:28PM (#546852)
I do not believe that forthright explanations of genuinely complex topics can ever be a disservice to users -- accurate and complete information is critical to "make[ing] the right choices".

The suggestion to provide patches is a simple displacement mechanism. A correct, reasoned evaluation is not predicated on also including patches, and a reasoned evaluator may have significant cause to not invest further effort in providing improvements to the evaluated software.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by ewjordan on Saturday April 04, 2009 @09:32PM (#546914)
I agree with you, but I think the gp has a point: look at Java as an example. Here we are, at a point where Java code runs extremely fast, but because of the "Java is slow" meme that took off at the turn of the century, any time Java comes up you _still_ see uninformed people on (for instance) Slashdot insisting that Java is unusable for important code because it's so slow.

That said, I don't think the right solution to avoiding problems like this is a "head in the sand" approach. If there are real performance issues, they should be acknowledged and addressed. I definitely get the sense that a lot of Ruby zealots are trying to pretend that there is no problem, which is something that Java zealots tried to do years ago (and something that the people in control of feature requests still do quite a bit, using the "Nobody can microbenchmark the JVM, it's too smart!" excuse).

I don't know why this stuff gets people so emotional, though. You don't see carpenters have heated arguments about whether a screwdriver is better than a hammer; why do programmers get so emotionally attached to their tools, refusing to acknowledge the limitations and strengths of each particular one?

Re:Mending the Bitter Absence of Reasoned Technical Discussion by eonwe on Sunday April 05, 2009 @03:16PM (#547624)
I can think of two reasons getting emotionally attached to the tools: learning the tool, be it Java or Ruby, requires considerably more thought than learning to use a screwdriver and using the tool shapes the way problems and solutions look to a programmer.

Required effort causes programmers to know less languages and to value the languages they already know higher as they've had to come up with a rationalization for learning the language. This rationalization hinders acknowledging the downsides of the languages they've learned.

Additionally, languages give us our vocabulary and solutions seen beautiful by a programmer of one language can seem incomprehensible or at least ugly to programmer of another language. This is at least something that I've personally observed in a Java-shop I work in.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by trapper on Sunday April 05, 2009 @08:06PM (#547950)
People still get emotional over primitive tools. Having an emotional stake in the tool must have conveyed some evolutionary advantage as we all display it.
Re:Mending the Bitter Absence of Reasoned Technical Discussion by berntb on Sunday April 05, 2009 @07:32AM (#547291)
Obviously, some language/OS/etc cultures are more fanboyish than others. I tend to not get active in those; it'd be embarrassing.

Edit: I am specifically thinking about Ruby here. It seems quite neat and worth trying, but... Maybe I'm spoiled with polite communities.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by Eliezer on Sunday April 05, 2009 @10:03AM (#547385)
The reasons that Ruby/Rails community ridiculed (obviously accurate) "ruby is slow" are exact same reasons the community was such a success in the first place. Consider what would have happened if "ruby is slow" meme took off.

Sadly, there's no standard and acknowlegedly forceful way to say: "Your statement is technically veridical but I disagree with the connotations you intend to sneak in."

http://lesswrong.com/lw/4h/when_truth_isnt_enough/

Re:Mending the Bitter Absence of Reasoned Technical Discussion by 10ren on Sunday April 05, 2009 @02:31PM (#547580)
Nice exposition of the idea, thanks. In the vernacular, isn't it just "attitude" and "tone"? It's also possible to not intend the connotations, at least not consciously.

My language is powerful; yours has dynamic binding; his is slow.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by dkarl on Sunday April 05, 2009 @03:00PM (#547606)
Sadly, there's no standard and acknowlegedly forceful way to say: "Your statement is technically veridical but I disagree with the connotations you intend to sneak in."

Yeah, there is. You yell. That's why cable TV news shows (and politics in general) suck so much -- you get two sides who refuse to actually contradict each other competing on volume to have their message triumph over the other.

That's because most of the people watching are going to come away with one idea, and you want those people. If you want to "win" in the minds of those simple-minded people, and your opponent isn't saying something that can be easily falsified, you have to compete on volume, arrogance, and ferocity.

On the other hand, if you only care about the viewers or readers who are capable of having a nuanced view, you can simply say what you have to say, as clearly and cogently as you know how. They'll understand and remember. But will you really be satisfied with those people? Probably not, if you're fighting for votes or market share. In other words, unless all you want is a fair shake from intelligent people, what you want can't be had in a civil way.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by carbon8 on Saturday April 04, 2009 @08:38PM (#546862)
until it is fully and widely understood. Cognitive dissonance

By accusing people of "cognitive dissonance" and apparently believing that's the primary issue here, you are contributing to the drama.

See the comments on the original:

http://www.radicalbehavior.com/5-question-interview-with-twi...

The aggressive and insulting remarks directed at Ruby, Rails and people associated with them are exactly the source of the problem here.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by trapper on Sunday April 05, 2009 @10:57AM (#547417)
Ruby is slow. Fast, good, easy - pick 2.
Re:Mending the Bitter Absence of Reasoned Technical Discussion by ankhmoop on Sunday April 05, 2009 @05:32PM (#547775)
A false dilemma.
Re:Mending the Bitter Absence of Reasoned Technical Discussion by trapper on Sunday April 05, 2009 @07:44PM (#547921)
Explain with examples?
Re:Mending the Bitter Absence of Reasoned Technical Discussion by ankhmoop on Sunday April 05, 2009 @09:23PM (#548045)
What technical limitation prevents a language from being fast, easy to use, and well designed? Alex seems to argue that Scala is 'fast, good, and easy', and I would tend to concur.

What I've seen of C# 3.0 and F# also implies that those languages could meet this criteria, but my experience with them is limited.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by trapper on Monday April 06, 2009 @07:37AM (#548688)
Software engineering is about tradeoffs. I'll take that a step further: everything is about tradeoffs. You can always optimise for one use case to the exclusion of the others.

Are you saying that fortran isn't faster than scala/jvm based languages? That APL isn't better for matrice's? That lisp macros aren't more powerful? Or that php isn't simpler than scala?

Being good at all three may be possible, but being optimal at all three is probably impossible.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by ankhmoop on Monday April 06, 2009 @02:35PM (#549329)
"Being good at all three may be possible, but being optimal at all three is probably impossible."

Why?

Re:Mending the Bitter Absence of Reasoned Technical Discussion by trapper on Monday April 06, 2009 @09:04PM (#550034)
Re:Mending the Bitter Absence of Reasoned Technical Discussion by ankhmoop on Friday April 10, 2009 @03:29AM (#555831)
"Multi-objective optimization (or programming),[1][2] also known as multi-criteria or multi-attribute optimization, is the process of simultaneously optimizing two or more conflicting objectives subject to certain constraints."

Note "conflicting objectives". Why do you believe the objectives are conflicting?

Re:Mending the Bitter Absence of Reasoned Technical Discussion by lsb on Saturday April 04, 2009 @07:42PM (#546805)
The regexp engine isn't slow. The bignum support isn't slow. The development time isn't slow.

If you wonder why there's a firestorm, it might be because of sweeping generalizations.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by shrughes on Saturday April 04, 2009 @07:50PM (#546815)
No, you're completely dodging the issue by saying some library functions, not written in Ruby, are not slow, and then talking about development time, which has nothing to do with the slowness people are talking about. The last time I checked, we're talking about the speed of code written in Ruby, and in particular, the speed of code as it's typically written.
Re:Mending the Bitter Absence of Reasoned Technical Discussion by ankhmoop on Saturday April 04, 2009 @08:02PM (#546826)
The regular expression engine and large number support are simply not broadly representative of Ruby performance, and do little to refute empirical observations of properly representative benchmarks and the many educated critiques of Ruby's implementation.

Your final example of development time is wholly unrelated to runtime implementation performance, and its use as a justification to assuage cognitive dissonance is predicated on a false dilemma -- that a language can not both support rapid development and a well performing runtime.

It is not necessary to introduce a false dilemma to justify an individual preference for Ruby development, in spite of its measured performance.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by tptacek on Saturday April 04, 2009 @08:31PM (#546856)
Isn't that a lot like saying that despite the VM system, OpenBSD 2.1 wasn't slow because it had a pretty good "gzip"?
Re:Mending the Bitter Absence of Reasoned Technical Discussion by kragen on Saturday April 04, 2009 @09:36PM (#546923)
Python is slow. For loops containing arithmetic, array indexing, function calls, and similar primitive operations that also exist in C, it's maybe 100× slower than C. But programs written in Python are usually not 100× slower than C programs with similar functionality. They may be 10× slower or 3× slower or, very rarely, faster; that's because their inner loops tend to be in operations like regexp matching, array arithmetic, data compression, string hashing, and the like, and Python's implementations of those things aren't themselves written in Python — they're the things you're likening to "gzip" here.

There's a selection bias here. If you write your compiler or interpreter or pathfinding algorithm in Python, it's going to be a lot more than 10× slower than if you wrote it in C (or Java or OCaml or whatever). So people don't write those programs in Python, so we don't get to compare them.

I've been writing about Python because I know more about it than I do about Ruby, but I think most of the same things are true of Ruby, as well.

Re:Mending the Bitter Absence of Reasoned Technical Discussion by swolchok on Sunday April 05, 2009 @02:58PM (#547604)
Sure -- minimizing the number of Python statements is a decent optimization heuristic in Python (and, as a bonus, that can help you optimize for human readers as well when not taken to extremes).