<snip>

>>1. Sequential execution
>>2. Repetitive execution
>>3. Conditional execution
>>
>>Nothing new in that department for many years.
>
>I don't agree with that. Especially if you look at ASP.NET and how the engine works it doesn't fit that model at all. Although the end result may be the same, the development approach is much more logical than the typical Web development approach. Add to that the superior design of the platform that was designed from the ground up for scalable Web development and you have something that is very different from the tools we have to use (COM) with VFP (or VB6 etc.).

Could you explain more what you mean here? You don't agree with that?

Perhaps you did'nt understand what I meant or I was'nt clear enough.

Computer make us work with binary values. Only two possible state. A bit is 0 or 1, True or False and this leads to


1. Sequential execution

Because the developer does'nt have to test if an instruction will execute.


2. Repetitive execution

Because the developer determined that some instructions have to be executed repetitively based on a given test.


3. Conditional execution

After a true or false test one or more instructions are executed.


I don't see how .Net or superior design or anything could change this way computers are working internally leading to the three possibilities I described.

Please give me more details on why what I said does'nt hold on anymore?