Friday, July 25th, 2008
I do NOT work for Adobe. I do NOT work for Microsoft. I do not work for Borland. I do not work for Oracle. I do not work for any competing manufacturer of any kind. I am Joe Developer. In the end, it’s folks like ME that will decide which technology survives and which dies – simply by our choices.
Moxie Zhang summarizes the post starting with the good:
- “The first thing I really like is the concept of threading. Being able to spawn off complex tasks without choking the main thread is pretty cool. You could, for example, show a really smooth animation when you are loading a bunch of data in a separate thread.”
- “A Silverlight application can directly communicate with the HTML document it is hosted on by simply setting a parameter.”
- “Being able to code in either C# or VB.NET is also a great feature. Especially since these two languages are pretty familiar to people developing for the Windows platform. I’m not one of them, but I found that C# is similar to ActionScript. Next to those languages you also have XAML, which does more or less the same things as MXML.”
and then the rest:
- Code in XAML and C# is really verbose.”
- “Styling controls is an absolute nightmare! I honestly think that this is going to be Silverlight’s Achilles’ heel!”
- “Another thing that I really couldn’t grasp is the lack of HTML tag support in text fields.”
- “I know the Expression tools are still in beta, but it has to be said that all the tools (including Visual Studio, which is no longer in beta) felt extremely buggy and incomplete.”
- “Over these three days, I got a strong feeling that Silverlight was created by people who don’t know anything about designers.”
It was bound to cause a bit of a fuzz as people read into things. Interesting to ready from the side lines.
Posted by Dion Almaer at 1:21 am