4 ms·
I'd like to chime in and point out that the Java approach had by far the best performance (about 7 seconds), for all you Java haters out there ;)
by BenjaminCoe 17y ago
I'd like to chime in and point out that the Java approach had by far the best performance (about 7 seconds), for all you Java haters out there ;)
- Groxx 17y agoCompared to the Ruby one, of course. Semantic tree > string mangling. I'm not a Java hater (I just think it's a horrible language to start in), but I'll make the counter-point that the Java approach is significantly larger and less readable than either of the others. There's likely a significantly simpler implementation somewhere deep in Java's frameworks, but ouch.
- BenjaminCoe 17y agoI think the main culprit hurting the readability is the inner classes. Which is bad form, in my opinion, unless someone is being very lazy.