text: in reply to
  Comparing Perl with C#, a simple templating example
  Your example is my first intro to C#. I probably won't live long enough to ever have to program in C# since I get to pick the languages that I use, but I can see a serious effort by MS to make something useful. To the 'C++' programmers, it is a natural extension to what they already know. But, I've never really trusted MS for their marketing and development plan. I hold some serious grudges with them for having intentionally gone after the destruction of non-proprietary (read "open") standards. They were doing this back when they first introduced their C-language compiler and libraries. They weren't alone in doing that. I criticized Borland for the same sin.
  It is hard to embrace a technology you don't trust.
  "I probably won't live long enough to ever have to program in C#"
  Try it at least once, at least I will ;-)
  As a matter of fact, one of our GUI user interface needs to be totally rewritten becaue of the user requirement changed. I am looking at C#, it was in Open Road (an engres thingy).
  BTW, for most of the application areas, C# is not targetting any thing else, but Java. GUI application is a good candidator to try C# with, because of the IDE. I took a look at the way C# defines event, handles event are quite interesting. C# even tries to beat Java with small things like how to define getters and setters.
  Perl should not be the one feels the most pressure from C#. For example, in this case, as a GUI interface thing, at least from my point of view, Perl is not a candidator any way.
  C# even tries to beat Java with small things like how to define getter
  +s and setters.
  [download]
  using System;
  public class MyClass
  {
  private string person = "";
  public string Person
  {
  set
  {
  this.Person = value;
  }
  get
  {
  return this.person;
  }
  }
  public static void Main()
  {
  MyClass app = new MyClass();
  app.run();
  }
  public void run()
  {
  string temp = "temp";
  // Crash me
  this.Person =