>I'm not actually interested in what eT is doing either.
>Which is why you opened a thread about it. ;-)

I didn't.

>How do you define mature?

I don't have a definition. Suffice to say that .NET is stable enough and well-known enough to have been used for applications by many companies all around the world. There are well defined best practises and massive support resources. This, I believe, is mature enough for it not to be considered "risky" developing an application in .NET. To say that because it is not 20yrs old makes it not mature enough is just plain wrong. It was on this basis that I, ahem, intervened :)

>Of course I agree and made similar comments regarding LAMP when Linq was released. So I'm curious: had eT decided to compile to LAMP rather than NET, would you still be disinterested?

I have no beef with eT or what they are doing. However, I don't know enough about it to give any kind of qualified opinion. However, what I do know of it is that it is aiming for VFP9 compatability in the .NET world. As to whether it targeted LAMP is immaterial because I really have no desire to write code in the VFP way anymore. To be honest, I much prefer C# and C-like syntax so, its a case of been there, done that. Just my preference.

>You're saying there are lots of NOLOH jobs?

Nope, not at all. I couldn't care less really. You know why? Because I am building my own product in NOLOH and using NOLOH brings me many benefits that couldn't be had using other, more mainstream web technologies. This is what for me is so reminiscent of Fox. I had my own business for circa 23+ years that greatly benefited from the availability of Fox products. I was able to do great things with minimal resources. I didn't care that the rest of the UK largely wasn't interested in Fox. When I sold that business, circa 2002, it was at that point that Fox became a problem for me, or the fact that from a contracting and job POV, no-one used Fox and therefore no-one wanted a Fox developer, irrespective of how experienced I was. So, to re-iterate, NOLOH is for the development of a SaaS type product and it is a good fit. However, since using it, I have picked up PHP skills, greatly improved my JS and got into PostgreSQL too (which is really good). Even if it all went south with NOLOH, I have acquired skills that I didn't have before.

>Then you should use NOLOH.

And I will, thank you very much :)