Re: Why Binding Scripting in Style Layer Conflates Semantics

This is basically a reply to everything I've read till this point... 
which is a lot, so I'm not pasting any of it.

Shelby, I don't mean for this to sound like critisism, BUT it seems to 
me that XAML is by no means complete or well documented for the world 
that exists outside of MS offices.  As such it seems a lot of what 
you're discussing here is really just conjecture as to how you assume it 
will work based on what little information MS has actually parted with.

With that in mind... doesn't it seem like this conversation might be a 
little premature? I understand that this goes much deeper than XAML for 
you, and that XAML is really just the icon that represents what you've 
been preaching for the last 3 years, but seeing how we know very little 
about XAML as a whole, why not write up your own spec and give us some 
"non-MS" examples to show your point.

I personally have a big problem with seeing how the internet would be a 
better place if things were more complex than good old xhtml.  Having 
stolen/borrowed/reverse-engineered every bit of css and xhtml I could 
find just to learn how it all works, it bothers me that a future 
generation of web coders might have to learn a significantly larger 
number of layers before being able to implement any code.

With that said I'm all for the xml/xslt duo seeing how it allows for OOP 
of html.  But this particular technology takes what we understand 
already and merely gives us more control over it.  XAML seems to toss 
all these things we've already been using out the window in favor of... 
of what?  That still hasn't been very well defined.

Again, I'm not trying to attack you, I'm just saying that I still don't 
understand the end goal of this.  And from what I've read it still seems 
like a premature debate (at least where XAML is involved)

Kris

Received on Monday, 28 November 2005 14:52:38 UTC