Quote Originally Posted by RhinoBull
You think about it - Mono wouldn't be there if it wasn't for .Net framework. Right?
Therefore what comes after is simply a simulator/replicas/[you name it]. That's the end of it but you may continue to argue if you wish.
Alright I'll quit (thread is becoming derailed anyway, heh) but I do not agree with your line of thinking. I would like to briefly mention that simulations and replicas are different (your post implies they are interchangeable) and, according to the webster dictionary, a simulation is either an attempt of deception (which Mono is not), a simulation of a physical system (Mono is not), or the imitative representation of the functioning of one system or process by means of the functioning of another (which I will concede that depending on how you're looking at this Mono could fit the definition but I don't believe it does entirely since its inter-workings and the output it creates (i.e. GUI) are different than .Net since it's using the OS' native GUI toolkit. Mono also has additions when compared to the .Net framework such as GTK#).

I also don't think you can say "Therefore what comes after is simply a simulator/replicas/[you name it]" otherwise you would be saying that cars of today are replicas or simulations of the Ford Model-T (or whichever car was the first car) or that all computers are simulations of a commador 64.

Mono has improved upon the .Net framework so it's somewhat of a different beast anyway. GTK# and other open-source implementations are built into Mono.