Eiffel Programming Contest Results

Berend de Boer writes "NICE, the nonprofit International Consortium for Eiffel, has announced the results of its fifth International Eiffel Programming Contest. This year had cash prizes of up to 1400 USD and software valued up to $8000 USD. There were 17 entries. The top scores were:ePalm, bringing Eiffel to PalmOS; ewg, generating C code binding glue; and Hbchess, a chess engine."

ePalm

[ajagci]

Technically, ePalm sounds like it might be a good thing. SmartEiffel, which it is based on, can generate quite compact native code even from large, object-oriented libraries because it performs global optimizations; that makes it a better choice than VM-based systems like Java or .NET. Furthermore, PalmOS doesn't isolate programs very well from one another, so a language like Eiffel, with built-in garbage collection and error checking, has a real advantage over C.

Still, SuperWaba probably fills that niche well enough and Palm handhelds are getting powerful enough so that the advantages of ePalm won't be big enough to let it catch on.

Re:ePalm

[advocate_one]

tis a pity the project has been moribund in pre-alpha stage since the last release in Aug 2001...

never mind... it won't hurt to have a play with it... :)

Pity

[Euphonious Coward]

It's a shame they didn't get submissions that would have suggested relevance for the language -- i.e., programs that demonstrate the language used to do something actually useful. As it is, they were obliged to award (1) a platform port, (2) an adapter to call code in some other language, and (3) something for playing games. All are (no doubt) fine efforts, but none of them would make anyone not already committed to Eiffel feel a need to look into it.

The unison program written in OCaml does a job not done by any other program I know of, does it well, and has inspired many to look into the language. Freenet inspired me to install a JVM to try it out. (I deleted both based on the experience, but that doesn't detract from the lesson -- I did try it.) The number of really useful programs written in Perl far exceeds the merits of the language itself, but continues to inspire new users. Python came from behind, but the deep value of many of the programs written in it ensured its enduring success.

To demonstrate the value of an obscure language, don't write yet-another text editor, IRC client, or RSS aggregator. We don't need any more, and we will feel no desire to try yours. Write something useful that's hard to write in other languages, or (better) hard to write in any language. The obscure language will get some (much-needed) reflected credit from the effort, and if it really helps, that will become evident (only!) when people are inspired to read the code.

Re:Pity

[sporty]

To demonstrate the value of an obscure language, don't write yet-another text editor, IRC client, or RSS aggregator. We don't need any more, and we will feel no desire to try yours. Write something useful that's hard to write in other languages, or (better) hard to write in any language. The obscure language will get some (much-needed) reflected credit from the effort, and if it really helps, that will become evident (only!) when people are inspired to read the code.

Nothing is hard to write.. it's usually

Re:Pity

[Euphonious Coward]

Of course anything already done will be easy to copy. Anything interesting, by definition, demands serious thought. Actually coding it might not be very hard, once you figure out what, precisely, it should do, but that's the hard part. The question, then, is how natural it is to express. If the program does the Right Thing, the code to express it should be beautiful, if the language is any good. People inspired to look will see that.

It's silly to code another clock, because it won't matter how beautiful the code is, nobody will read it. Nobody needs another damned clock. Write something useful and meaningful. If you can't think of anything useful and meaningful, and you write a damned clock instead, all you're demonstrating is that you can't think of anything. What does that say about you, as a representative of the fledgling user community for your obscure language?

Maintainability

[Xtifr]

My understanding (which is admittedly shallow) is that the main benefit of Eiffel over most other compiled (or not) OO languages is the added maintainability provided by its "Design by Contract" features. (Not to mention the enhanced readability gained by not being based on C.) Unfortunately, "maintainability" is a bit of a difficult feature to show off in a programming contest. Although it's a pretty important feature in the Real World(tm).

Re:Maintainability

[axxackall]

Unfortunately, "maintainability" is a bit of a difficult feature to show off in a programming contest. Although it's a pretty important feature in the Real World(tm).

Unfortunately, "maintainability" is a bit of a difficult feature to show off in the Real World(tm) too where usually managers prefer to dictate their teams to write on Perl, C++ and Java.

By the way, the code written on OCAML or OHaskell is even more readable. Not to mention that both language are specially designed (as many other FPL) to ma

Re:Pity

[jc42]

Yeah, well, I was expecting an exciting Obfuscated Eiffel Contest, to really give the C and perl folks something to admire in eiffel.

Such a disappointment.

Re:Pity

[scubaken]

The only project that might get other peoples attention and attract newcomers to eiffel would be a large-scale development project. Maybe if the Mars rover system software was written in eiffel, more people might go, "Hmmmmm..." And take a peek at eiffel.

There's really no Eiffel projects that a single developer can write (in his or her spare time) that cannot already be done in C++ or Java. Eiffel's virtues are evident only when programming in the large.

At the moment, the best thing going for Eiffel has b

Re:Pity

[scubaken]

The great thing about the Eiffel Struggle contests is it allows those of us who would like to use Eiffel (in the RealWorld(tm)) a chance to write something substantial in Eiffel.

17 entries?

[twoflower]

This year had cash prizes of up to 1400 USD and software valued up to $8000 USD. There were 17 entries.

Okay, which Eiffel programmer submitted twice? I thought that was against the rules.

Re:17 entries?

[berenddeboer]

Till G. Bay submitted two entries. That is not against the rules. All other entries were by different programmers.

Perhaps a surprise that programmers are more diverse than you thought :-)