Note, that it is my prediction that Microsoft will be
implementing the latest version of ECMAScript (with
type-checking and OOP) in the next version of IE. I also
predict that it will (A) be CLI/.Net and thus (B) any
.Net language will run on the client, manipulate the
DOM, etc, and will render this conversation irrelevant.
None the less, it seems like an interesting project. So,
what have I done?
I am not so sure Microsoft will implement ECMAScript in its latest
version of IE. In fact, I think IE as it is known, is dead.
If I look at what XAML is (more or less, the same that XUL in Mozilla),
my prediction is that the distinction between a browser and a common
user interface in Windows will dissapear, so that I am not sure even if
a new MS (independent) browser will exist. In an scenario like this,
why to use ECMAScript when you have all .Net languages available?
Obviously, this is speculative, but I think the coming Longhorn will
not have any independent browser at all. Maybe the users will "think"
they have, but in my opinion the Operating System will do all the job.
In this scenario, script languages may become obsolete or may become
the most important client languages of all. Who knows?
\\jordi
|
_______________________________________________
o-xml mailing list
o-xml-zRfLyl9bSvv/LJnD5RR8eeqUGfbH9hYC@xxxxxxxxxxxxxxxx
http://lists.pingdynasty.com/mailman/listinfo/o-xml
|
| 
