When
· Naughties
· · 2006
· · · September
· · · · 01 (2 entries)

RAD X: Making Markup · [RAD stands for <a href='/ongoing/When/200x/2006/08/17/JRuby'>Ruby Ape Diaries</a>, of which this is part X.] If you’re writing Web apps, and even if you’re one of the few who isn’t, you’re probably going to have write code to generate markup, HTML or XML. Historically, programmers have found this difficult, and thus there are lots of libraries that try to abstract markup away behind code (for example, my own <a href='/ongoing/When/200x/2004/02/20/GenxStatus'>Genx</a>). There are tricky issues and trade-offs here, and Ruby throws them into pretty sharp focus ...
 
Spolsky Starts a Language War · In Joel Spolsky’s new <a href='http://www.joelonsoftware.com/items/2006/09/01.html'>Language Wars</a>, he argues that .NET, Java, PHP, and maybe Python are the safe choices if you’re going to build out a Web app that’s really big and really critical. He ices this cake with a shovelful of classic FUD aimed at Ruby and Rails. Not surprisingly, David Heinemeier Hansson volleys back twice with <a href='http://www.loudthinking.com/arc/000596.html'>Fear, Uncertain, and Doubt by Joel Spolsky</a> and <a href='http://www.loudthinking.com/arc/000597.html'>Was Joel’s Wasabi a joke?</a> Bruce Tate has a more thoughtful response over at InfoQ: <a href='http://www.infoq.com/articles/From-Java-to-Ruby--Risk'>From Java to Ruby: Risk</a>. You may not agree with all of Bruce’s points, but they’re well argued. It may surprise some who’ve endured the flood of Ruby-red writing around here recently, but I think Joel’s correct that Python is quite a bit better proven than Ruby; and also that Ruby has a big Unicode problem. But I can’t get around the fact that Joel sounds <em>exactly</em> like a mainframe droid talking about Personal Computers, or a VMS droid talking about Unix, or an EDI droid talking about the Web, or a C++ droid talking about Java. Yeah, the new thing is kinda unproven and kinda shaky in places and kinda slow and not very full-featured. But it’s got ease-of-use advantages and programmer-productivity advantages and developers like to use it. See the <a href='http://www.tbray.org/ongoing/When/200x/2004/01/03/TPM1'>Technology Predictor Success Matrix</a>, and particularly the last three criteria: <a href='/ongoing/When/200x/2004/01/12/TPSM-Programmers'>Happy Programmers</a>, <a href='/ongoing/When/200x/2004/01/13/TPSM-Elegance'>Technical Elegance</a>, and especially the <a href='http://www.tbray.org/ongoing/When/200x/2004/01/14/TPSM-8020'>80/20 Point</a>. Joel’s probably wrong.
 
author · Dad · software · colophon · rights
Random image, linked to its containing fragment

By

I am an employee of Amazon.com, but the opinions expressed here are my own, and no other party necessarily agrees with them.

A full disclosure of my professional interests is on the author page.