HTML is a piece of p!$$. It's nice though when an application abstracts it away so you can approach web development from another angle.

The significant differences between what you say you are doing and what eT hopes to achieve is "scope" (eT is far more ambitious than Web2/AJAX- what about Silverlight?) and the dreaded "VFP" on which you are focused. IMHO, VFP is an added bonus with the eT system because I have plenty of valuable existing code but it is irrelevant to the abstraction and re-compilation power that delivers far more benefits than those offered by your "cool" HTML system. I'd also observe that while it is easy to call VFP dead, I'd expect there is a lot more commercially available expertise than there is for something like NOLOH. Surely we can agree that these sorts of tools create their own demand as I'm sure NOLOH will do if its beta continues to go well and it meets its milestones. Not sure how else I can explain.

While we're on the topic of language morbidity: people may also like to consider that (without getting tied up in what has happened since) the Pascal language was sidelined almost to academic interest in mainstream IT until Borland extended and reintroduced it in Delphi, to great acclaim. These days the broad reach of the net allows people like NOLOH and eT to carve new niches based on the competitive advantage they offer and without getting bogged down in particular languages. Bring on the abstraction, right? ;-)