> --- On Thu, 8/14/08, Scott Barnes <[EMAIL PROTECTED]> wrote:
> C# is an ECMA-334 standard. As to how this affects Silverlight? Cole, could
> you elaborate?
Sure. Microsoft wants a new standard for web scripting using Silverlight's RIA
framework via .NET
and the Dynamic Language Runtime. They want to bring support for IronPython
and IronRuby to web scripting. Some see that as a Microsoft technology lock-in.
Just like some saw ES4 as an Adobe lock-in (or at least a validation of it).
ECMA-334 was precisely about Microsoft making C# a "standard." It's "a"
standard, but not "the" standard. It's an off-shoot. So, perhaps it is best
that history just repeats itself. Let them create a separate ECMA standard for
Microsoft/Silverlight, and another for Adobe/Flash. Let's whip out some
ECMA-402, and ECMA-402 -- pick a number.
My point was that this was not going to get resolved in ES4, where one idea was
going to get picked over the other. Standards promote commonality and adoption.
Those things can translate into competitive advantage. Microsoft was not going
to let Adobe have ES4 as "the" standard. It was too much of an advantage.
--Cole
