Reading Programming

Thanks for the info, Jaz (and everyone else).

Have you guys heard anything about Perl 6? Man that stuff sounds cool.

Source enters the parser. The parser emits a syntax tree.

The syntax tree enters the compiler. The compiler spits out bytecode.

The bytecode enters the optimizer. The optimizer spits out more bytecode.
(But better!)

The bytecode enters the runtime, which then Does Something with the
bytecode. (Presumably run it, but possibly turn it to Java bytecode, or
.NET bytecode, or an Alpha executable, or an encoded DNA sequence for
fruitflies or something)

Have you guys heard anything about Perl 6? Man that stuff sounds cool.

It does, but it's been vaporware for too long already.

'Yeah, That's what Jesus would do. Jesus would bomb Afghanistan. Yeah.' - snowlion

I apologize for the late reply. Keep in mind I've done very little in web dev. My background is mostly in C++. I've made a couple web apps in php, extended with perl as a glue language to do various tasks related to file manipulation. I've found this works very well. From what I've done and read about others work, I can forsee perl playing second fiddle in web dev, as an extention language, well into the future. Can't say much about ruby/python/java, though from briefly reading snippets of python and java, both's OO model and memory management look cleaner and safer than C++. Most languages boil down to subtle differences in features, personal preference, and overhead/speed issues.

http://www.caucho.com/articles/benchmark.xtp

That said. I've found more often then not, its not the language, its the implementation.