<% form_for(@foo) do |f| %>
  <%= f.text_field_with_auto_complete :bar %>
<% end %>

This fork also supports nested fields_for calls:

<% form_for(@foo) do |f| %>
  <% f.fields_for(@foo.baz) do |baz_f| %>
    <%= baz_f.text_field_with_auto_complete :quux %>
  <% end %>
<% end %>

You can find my fork on Github, here.

I thought we’d gotten past this back in 2000 when .Net came out… but 3 Years of Ruby on Rails experience you say?

Mathematically impossible for the average (read: non-core) rails developer, considering Ruby on Rails was only released publicly in July of 2004.

They’re obviously very picky and so are willing to pay up to a whopping US$35-US$55/hr for all those Rails rockstars who were using it before it was released to the public! I’m sure they’ll drop everything and come running to apply!

“We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil.”
Donald Knuth

Earlier today, I suggested that we should hold language and platform selection to the same standard we do with our code when avoiding premature optimisation.

The thrust of my argument was that, in relation to scalability, 99% of sites will never become so popular as to require scalability beyond that which is possible with Rails, so worrying about scalability feels like the start of big design up front.

We should aim to not be dogmatic about our selection of language or platform, instead choosing the tools to get the job done, so we can get something out there.

After all, I think it was Fred Brooks who told us to build a first version and throw it away; the inherent wisdom in this approach is that you learn far more by building something and failing fast, than doggedly sticking to a flawed design that dies a slow, painful death.

If I can return to the example of Twitter, I don’t have any references, but I think their development time was quoted at something like 4 months? That’s not a lot of time really, and therefore, it’s not a lot of time to write off in the case that Twitter doesn’t get adopted and turned out to be an idea that was DOA.

Happily for the guys at Obvious, this wasn’t the case, and now they have a scaling issue, but I bet you they know a hell of a lot more about their users and usage patterns than what they ever could have predicted if they had set out to design it up front.

Could they have not followed the same path with J2EE or ASP.Net? Sure, if you ignore the fact that they’re Rails developers and therefore are more productive with… Rails. They chose the platform that was right for them, that got out of their way and let them implement the service to see if it would even work.

Another example, Reddit. The first version was written in Lisp before being rewritten in Python – rewriting a proof-of-concept application (the cool kids call it beta software these days) into something that is “commercially ready” is not a bad thing.

I’m sure there are plenty of counter-examples where such an approach has failed, but I’m not getting into reductio ad absurdum arguments like “if your premise is true, then I could write #{compute_intensive_app} in #{slow_high_level_language}!”

And suddenly, that gorilla shrinks; or at least it seems to.

Until someone goes and pushes the boundary way beyond those who’ve come before. Suddenly, the gorilla has grabbed your girl, climbed to the top of the Empire State and is angrily swatting light aircraft left, right and centre.

Scaling suddenly gets interesting again.

Nay-sayers and trolls cloud the issue
Those who for whatever reason want to see Rails fail, have grabbed ahold of the issue and are casting it as a reason to abandon Rails: “Behold, the savage beast that cannot be tamed!” Often, they’ve got their own agenda, whether it’s a desire to see their pet platform succeed, or to see DHH kicked to the dirt, these folks don’t really care about the scaling issue at all. They latch onto these issues not to help improve the platform, in the worst case they want to destroy it.

So forget them.

We’re here because we want to solve this without changing platforms.

It doesn’t matter to most of us anyway
The truth is, 99% of Rails projects will *never* hit a performance wall that cannot be solved using existing wisdom. So the issue is a non-issue and certainly not a reason to ditch Rails.

If perchance, you’re part of the other 1%, you should be thrilled to have this problem, it means your software has been successful! Fact is, you don’t accidentally create a site/service which generates 11,000+ requests/sec. You explicitly set out to do so. And presumably, you chose Rails for a reason. Why shouldn’t we extend the concept of “no premature optimisation” to language and platform selection? If Twitter had chosen an “enterprise” class platform and tried to architect for 11k reqs/sec, chances are they would still be building…

Obvious had a reason to choose Rails; they aren’t naive, they’ve been around the block with Rails before.

Generally, it’s much better to throw something out there NOW, and let the real problems come out in the wash, rather than sit in a dark room, worrying about what might happen and giving yourself a case of analysis paralysis.

Escalation Sucks
This issue has been blown up by a combination of strong opinions, incomplete information and folks from other camps pouring fuel on the fire. It’s time this “conflict” was de-escalated and the combative nature of the discussion toned down.

The situation itself can be summed up pretty easily

• We’re in uncharted waters in terms of this sort of throughput, although others have suggestions and maybe even solutions.
• The problem didn’t just suddenly spring up on the Twitter guys, clearly they’ve been working on it for a while – implying they’re now crying to core because Rails is broken for them is disingenuous. (In fact, the whole “they’ve forsaken that opportunity for an arms-crossed alternative.” thing smells like something of a strawman argument – I didn’t get that from the interview, so unless that’s come out of some backchannel, it seems a peculiar accusation to make.)
• Solutions that work for Twitter may not work for other Rails apps. Once you exhaust all of the conventional scaling wisdom, you start to move into application-specific optimisations. Are we there yet? I guess we’ll wait and see.

When the storm is over
This is a learning opportunity for everyone, but those who stand to learn the most are the core team and the Twitter guys. I hope each can continue to be open to the other’s position. We need to remember at the end of the day, Twitter are under no obligation to release patches, and the core team are under no obligation to accept them – I hope that doesn’t happen though, as the community would be the worse for it.

Now I was happy with my design, on the recommendation of a friend, I shot a PDF off to Click Business Cards via their website, and within 24 hours my cards had been printed and express posted to my door (they arrived yesterday). Their website may not be much chop, but their service sure is.

With a little hesitation, I cracked open the box, hoping that I’d gotten the resolution, colours and bleeds right. I had, they look excellent, if I do say so myself!

I’m the first to admit I’m no designer, and I’ll cop to the fact that the design was largely inspired by Dave Seah’s cards, whilst the loco image and ruby red was chosen to tie into the fact that I’m moving towards specialising in Ruby on Rails.

So, with new cards, I realised that the Wordpress template I’ve been using was pretty tired.

Time for some branding re-alignment!

A quick CSS change and a new header image later, here we are. I’ve kept the layout the same for the time being, I don’t want to sink a lot of time into a new Wordpress template as I’m thinking of packing this whole site up and moving to a Slicehost slice. If I do that, it will be goodbye Wordpress, hello to either Typo or Mephisto.

For the time being however, it’s steady as she goes!

Tasmania is a small place, which is why I’m surprised that very few people in the IT industry here have heard of Morfik, a Hobart based development company. Reading this morning’s Read/Write Web however, things may be about change there. As reported by Richard, slashdot are running a post about the Morfik patent which appears to be aimed squarely at Google’s GWT.

I’m in two minds about this, as I always am about software patents. On the one hand, Morfik was clearly first to the party in terms of public release of a JavaScript compiler, according to the patent they had a provisional granted prior to the release of the GWT. On the other, I have to wonder how this is any different to the multitude of language translation techniques already out there, or at least whether it’s significantly inventive enough to pass the “not obvious to a practitioner in the field” test.

But hey, this wouldn’t be the first patent to be granted despite the obviousness of it to someone with half a brain. I mean, thank goodness the patent doesn’t mention Ruby, I guess that means RJS is safe!

class Numeric

  def grams
    self
  end

  alias :gram :grams
  alias :g    :grams

  def kilograms
    self * 1000.grams
  end

  alias :kilogram :kilograms
  alias :kg       :kilograms

  def tonne
    self * 1000.kilograms
  end

  alias :tonnes :tonne

  def pounds
    self * 453.59237.grams
  end

  alias :pound  :pounds
  alias :lb     :pounds
  alias :lbs    :pounds

  def stone
    self * 14.pounds
  end

  def ton
    self * 2240.pounds
  end
  alias :tons :ton

  def method_missing(method_id, *arguments)
    if match = /^to_([a-zA-Z]w*)$/.match(method_id.to_s)
      self / (1.0 * 1.send(match[1]))
    else
      super
    end
  end
end

Being that we use the metric system in AU, I reduce all units to their respective value in grams.

10.kilograms
# => 10000
1.lb
# => 453.59237

And here’s the payoff: the method_missing override lets you do neat conversion tricks like:

1.kg.to_lbs
# => 2.20462262184878
0.3.tonne.to_kg
# => 300.0

(There is one caveat, I currently don’t check for the existence of the method given in match[1], so it’s not exactly prime time code just yet…)