Comment Re:I love Perl. (Score 1) 174
it's not so much that native code doesn't deal with garbage collection as much as it's that the normal c libraries dont' support it.
as far as those niceties hampering performance... it is true. cool things like garbage collection trade ease of coding and safety of code for a loss of speed. however, c# supports stepping out of the runtime and write "unsafe" code. basically forgoing the sandbox, allowing you to do "fun" stuff like pointer operations and such. for even more leeway, you can step out into managed c++, all without losing interopability with all other .net languages. allowing you to write the high performance objects in c++, inherit from of just wrap that object in vb.net or perl.net or c# to do whatever you want in a more friendly ( or at least in perl's case, familiar :P )language.
at any rate, regardless of all this functionality... writing straight to the clr classes without dropping out of it will still be much more performant than mod_perl can be. along with all the goodies that the starter of this thread pointed to.
as far as those niceties hampering performance... it is true. cool things like garbage collection trade ease of coding and safety of code for a loss of speed. however, c# supports stepping out of the runtime and write "unsafe" code. basically forgoing the sandbox, allowing you to do "fun" stuff like pointer operations and such. for even more leeway, you can step out into managed c++, all without losing interopability with all other
at any rate, regardless of all this functionality... writing straight to the clr classes without dropping out of it will still be much more performant than mod_perl can be. along with all the goodies that the starter of this thread pointed to.
