the blog for developers

The Erlang hype is grotesque

Take for example this recent post on hacker news with the title “Amazon and Google Discover Erlang (IMDB is switching from Perl to Erlang)”. There in the comments someone gives a source for the IMDB claim: “IMDb on Java/Erlang (a job posting)”. Going to the job listing results in

We are currently working in Perl but have plans to use Java, Erlang and any other language that we think will suit our purposes.

Constructing an “IMDB is switching from Perl to Erlang” (though everything is better than Perl) out of this job listing is grotesque.

As a side node, I’ve been looking into Erlang for some time but I’m still undecided. With some functional style in Java, Kilim, Terracotta and a Supervisor modul (see Scala), I guess most of the Erlang failover/distribution stuff can be done in Java too. I’m interested in CouchDB, but I have no reliability numbers and performance is said to be very low (for now?). The feature set of CouchDB is compelling though.

Ah in the end I only wish for some more functions in Java, better separation of concerns, constructors which can return any type instance, syntactic sugar like in Groovy, structural interfaces, enforced nice-style non-null references, catch(E1,E2,E3) … well well well. I’ll better stop before this turns into another How-to-improve-Java rant.

About the author

stephan Stephan Schmidt has been working with internet technologies for the last 20 years. He was head of development, consultant and CTO and is a speaker, author and blog writer. He specializes in organizing and optimizing software development helping companies by increasing productivity with lean software development and agile methodologies. Want to know more? All views are only his own. You can find him on Google +

You can leave a Reply here. Of course, you should follow me on twitter here.

You can share this post!
Do you want to tell others about this article? Use the social bookmark icons to submit this artice to the service of your choice. Thanks.

Leave a reply.

Comments

Jan

Check out the CouchDB developer’s reply to the performance: http://damienkatz.net/2007/12/couchdb_perform_1.html

In addition: Things are sub-par now but are resolved easily and will be soon.

Cheers
Jan

Stephan, you are correct that it is unreasonable to read that IMDb is switching to Erlang based on that job posting. You are also right about the hype. It really does a disservice to a language to promote it with hyperbole and misrepresentations.

This is a sensible criticism of the blog post no hacker news. I will keep it in mind and restrain my own enthusiasm to realistic levels as I present Erlang to people.

stephan

@Jan: Thanks I’ll take a look.

stephan

Looks promising what Damien says.

I won’t use Erlang – it’s not my style – but Erlang applications with distribution and failover look interesting. I would prefer Couch DB – especially as I’m heavily into SOFEA – to MySQL anytime.

Reedo

What’s also unreasonable, etc. is flatly stating “everything is better than Perl”. If that were true, Perl would never have existed, y’know…it still has a userbase and it continues to improve (Perl 5, I mean. Perl 6 is a different language.). However, I’ll gladly concede that many options are better than Perl for many tasks.

stephan

@Reedo:

From a software engineering point of view with software development as a team effort, yes “everything is better than Perl”. From my perspective most Perl efforts are one man shows because of Perls programming style.

I’ve canned several Perl projects because the lead developer left and the code was not understandable to the newly hired Perl guy.

The last bastion for Perl was shell skripting, if awk and grep isn’t good enough. Today I use mainly Ruby for that though.

Jack9

“If that were true, Perl would never have existed”

You’re confusing axioms.

Everything has always been better than Perl != Everything is better than Perl.

Everything is better than ADA. It was good for its time and produced tools and concepts that led to better languages.

Leave a Reply

What people wrote somewhere else:

Additional comments powered by BackType

Guide to CodeMonkeyism

Over the last 4 years I wrote many articles on this blog. To make it easier for you to find the relevant ones, I've organized them into topics.

Top 10

6 reasons why my VC funded startup did fail

Go Ahead: Next Generation Java Programming Style

Java Interview questions: Write a String Reverser

The dark side of NoSQL

7 Bad Signs not to Work for a Software Company or Startup

Is Java dead?

Scala vs. Clojure

Never, never, never use String in Java

No future for functional programming in 2008 – Scala, F# and Nu

Clojure vs Scala, Part 2

Java Developer

Is Java Dead?

Go Ahead: Next Generation Java Programming Style

Be careful with magical code

All variables in Java must be final

Never, never, never use String in Java

Bending Java: More readable code with methods that do nothing?

NoSQL Guy

NoSQL: The Dawn of Polyglot Persistence

The dark side of NoSQL

Essential storage tradeoff: Simple Reads vs. Simple Writes

Sharding destroys the goals of your relational database

The unholy legacy of databases

Startup/CTO

Development Dream Teams

6 reasons why my VC funded startup did fail

American vs. European style of Software Development

12 Things to Reduce Your Lead Time and Time to Market

The high cost of overhead when working in parallel

Essential storage tradeoff: Simple Reads vs. Simple Writes

Job Seeker

Another Good (Java) Interview Question

7 Bad Signs not to Work for a Software Company or Startup

Java Interview questions: Write a String Reverser (and use Recursion!)

Java Interview questions: Multiple Inheritance

As a Manager: What I value in developers

Top 10 Tips (+1) to Get a Pay Raise

Agilist

What Developers Need to Know About Agile

5 Practices Better to Change in Your Scrum Implementation

Scrum is not about engineering practices

ScrumMaster and ZenMaster: The joke of certification

What is Trans-Scrum?