In the future we may support additional languages and if there's particular ones please feel free to drop us a line at postgres@heroku.com and let us know which ones you'd like and why.
SQL Server allows for .NET stored procedures, so you could already use something like JScript.NET.
I fail to see what you mean by thinking out of the box.
Third party handlers exist, off the top of my head, for JavaScript (obviously; see TFA), R, Ruby, Scheme and shell. That list probably isn't remotely exhaustive.
To be honest, though, I've never really had much of a use for any language other than pl/pgsql and occasionally pl/r; I try to keep anything too complicated outside of the database.
Being able to implement such an API in $DECENT_LANGUAGE and not pl/pgsql sounds like an enormous win.
Postgres is awesome, but the JavaScript support from PL/V8 is a third-party extension, not a core database feature.
I don't think you'd say "well, Ruby is awesome but web application development support comes from a third-party project, not the standard library."
I agree, I just thought from the reference to JSON (which is a core database feature) that PL/v8 was being incorrectly attributed the postgres team directly.
> I don't think you'd say "well, Ruby is awesome but web application development support comes from a third-party project, not the standard library."
I might if someone pointed to Rails with a comment that implied it was a credit to the Ruby team and a next step to a stdlib feature.