>
Why not stick with what you´re doing now, and use the new advanced technology when it is mature and available.
>

Several flaws in this reasoning

1. It assumes that new/advanced technology is not available.

2. It assumes there is an absolute definition of "mature". One can credibily argue that .NET is mature. It has been out for several years now.

3. When technology becomes mature, it by definition, is no longer new - although it may still be advanced.

4. When VFP 3 came out, it was both new and advanced. And...in spite of this, it was advocated quite heavily.

There is a good deal of anti-fox prejudice/fox-bias going on here. The rule is thus:

If it is new, advanced, immature, it is acceptable if Fox. On the other hand, regardless of maturity, if it not fox, it is not acceptable.