Check it out ! .NET Gets a new Logo ! Keep your eyes out for the new branding this week at #PDC 2008 !
Archive for October, 2008
Monday here at PDC in Los Angeles, Sara Ford will be doing a book signing of her new book with coppies available at 20% discount and proceeds going to a great cause.
By now you’ve probably heard that we’ve shipped Silverlight 2.0. Many folks love it, some folks don’t care.
Though I avoided spend much time at all with Silverlight 1.0 and resisted 2.0 until it neared commercial quality delivery, my personal interest is just gaining momentum. So now that Silverlight 2.0 is an officially released product I thought I’d share some thoughts.
When it comes to software development, I tend to be PRAGMATIC above all else. I’m not one of those guys (and we have them here at Microsoft, even on my own team) who emerge themselves in the latest technology for little more reason then that fact that it’s the “new thing”.
Don’t get me wrong, we NEED those guys. They will flush out the problems and shape the technology that the rest of us will be using in 5 years; it’s just not where I choose to spend my limited time.
My preference is to focus on the technology that can have meaningful impact on the next 6 fiscal quarters at the customers that I work with and to help Microsoft Developer Product feature teams understand what customers need and want relative to what he have already delivered.
So, Silverlight 1.0 was of only passing interest to me. Silverlight 1.0 has a GREAT media story but it didn’t fire me up.
Silverlight 2.0 (and what’s coming in 3 and beyond) has my attention.
The most common questions I get about Silverlight are in the “Flash Killer” category.
Why would I switch, and isn’t this just Microsoft wanting to take some of Adobe’s market.
Sure, Silverlight, in some regards is vying for adoption in what might previously been Adobe Flash land. Just as Flex and Air are competing for the more conventional developer audience that has been largely a Microsoft customer base.
The things that Flash and Silverlight both do well are of little interest to me either. Flash has a nearly ubiquitous adoption. If simply streaming standard web video or adding <object> based user interface glitz to my application were my goal, I might never dive deep into Silverlight.
But, my pragmatic nature forces me to additional considerations.
If you’ve ever heard me give a conference keynote you are likely to have heard me quote Albert Einstein who said, among many other brilliant things, “The SIGNIFICANT problems of today cannot be solved with the KINDS of thinking that created those problems in the first place.”
This is the facet of new technology that excites me the most; the ability to examine problems both new and old, and think about solutions that were not possible with the technology available to us even a year or two ago.
Enter Silverlight 2.0. Below I’ll highlight some of my favorite attributes of Silverlight 2.0 and mention why I think they change things.
1.) CLR based runtime.
The browser embedded runtime will change what we can build in our browser based applications. Now, it’s not the first time we, as an industry, have tried this browser extension thing. ActiveX failed because it lacked a mature security model. Java Applets failed for a variety of smaller reasons. Different browser hosted JVMs yielded vary different renderings, while there were security flaws the restrictive sandbox prevented the use of client side resources, they were hard to write, internet connections at the time were too slow, and Sun was far more interested in the server side story for Java.
All the above issues aren’t here to inhibit Silverlight 2.0 Application deployment.
The Silverlight 2.0 runtime is tiny and the applications are even tinier, but the performance of code execution is FAST. This download and execution performance opens up new doors for us to implement complex client side logic, including rich business implementation running right there in our browser hosted application. What’s more, writing these applications will be easier due to the rich .NET Framework subset that is implemented with Silverlight 2.0.
What’s more, if you ware already a .NET developer, your learning curve is minimized because Silverlight Development is .NET Development. If you are building WPF applications, you’ll add Silverlight to your toolbox and feel like you never left home.
2.) First class language support.
This model does nothing to distribute processing between the client and the server and, from a user experience perspective, we are restrained by the semantic requirements of the traditional Web based Client / Server implementation scenario.
With Silverlight 2.0 we can implement our logic in C# or VB.NET if we choose to leverage full OO constructs, strong typing, and the like.
If you lean to the Dynamic Languages view of the world you can choose Python, Ruby, PHP (Phalanger) and whatever languages might be implemented.
First, please understand (and embrace) the fact that XAML is NOT just a presentation syntax. XAML is an Extensible Application Markup Language. This means that is can be used to define any type of .NET object, behaviors and associations.
The use of XAML for Presentation definition in WPF and Silverlight is only one possible use and a broader use of XAML will create very interesting scenarios.
XAML is interesting to me for many reasons, but let me be say up front, I hope to never write a single line of XAML code “by hand”. That fact that you COULD write XAML by hand is not where the power is. In fact, if you had to write XAML by hand, it would never happen. (Just like SOAP, and many other useful XML dialects.)
First, XAML is important because it is a verifiable XML syntax which means tools (like designers and IDEs) can reliably read it and interpret it in identical ways. This is very important because it means that we may, after many attempts in the industry, actually have a development process where developers and designers can truly work on the same project with their respective tools of choice in a very seamless way (read NO technology conversions / translations ever time the work product passes across the designer / developer boundary.)
Next, XAML is XML. Lest we forget the “X” means EXTENSABLE. This means that the base syntax for XAML can (and will) be extended by developers and vendors for specific purposes and this can be done without breaking the base implementation.
Also, XAML enables Vector based rendering. Bitmaps are fine for photos, but as the variety of display devices continues to increase with a huge disparity in screen size and resolution, bitmap driven user interfaces are sure to vanish.
4.) Timeline based behaviors.
My video and animation contacts tell me that Timeline based design experience is a huge thing.
From a personal experience, as an artistically challenged geek, the Timeline based design process is simple enough that even I can do some reasonably good work in the tools. (It’s just like editing a video.)
5.) Isolated User Storage.
Remember the Einstein quote above? If you ask me, user configurable client storage is pure genius. Think about the things you can do with it. Need REALLY rich view state? Put it in client storage and drastically reduce your state driven HTTP traffic. For that matter, do it with ALL our state data. Client profile, etc.? Not only can you save all that traffic and server resource consumption, but you can still keep the master copy on the server so that you can reconstitute it on the client when a user connects from a new machine. How about client side object persistence? (Even for objects that get manipulated on the server.)
And think even beyond those possibilities. How might we use client side storage to enable “not-always- connected” application scenarios?
And how about integrating client side storage with Microsoft Live Mesh services or the Cloud Computing technologies that you will start hearting about at PDC J ? The possibilities are only restricted by our own creating abilities.
6.) Sockets Support.
Sometimes you need RAW SPEED. Silverlight 2.0 provides a well factored class collection to implement client side Sockets conversations in your applications. This means you can “speak sockets” which are supported on about every server platform since the birth of the World Wide Web, and bypass the overhead of HTTP if you need the extra performance. This way, if you need to build a chatty application you won’t have to worry about the platform painting you into a performance box that would require a massive rewrite.
7.) Enhanced Media Experience.
I mentioned earlier that the idea of streaming “standard” video wasn’t so interesting to me since there is a bunch of technology out there that already does a pretty good job of this.
Note the emphasis on “standards”. In the long term, Silverlight hold some very interesting promise for steaming media. Apart from the great Codec and High-Def work the Silverlight Team is doing, the “built in” performance throttling in Silverlight is bloody brilliant. In layman’s terms, the Silverlight infrastructure will dynamically adjust the stream based on network conditions (like latency and available bandwidth) in order to deliver optimum viewing quality with as little of the “pause and stutter” that we often experience in our Flash or Real based streaming video experiences.
And don’t forget to think about the business logic that we can add with our Client Side C# or VB.NET code. By combining metadata in the video stream and interpreting users behavior while viewing the videos, we open up LOTS of new and exciting opportunities. I’m playing with a “Smart” Video Player for all the technical How-Do-I videos that we publish on www.asp.net
Last, but not least, the Expression tools that support Silverlight (and WPF) are slick. Already in version 2, they are enjoying great popularity and rapid adoption from both new users as well as the traditional “design” community. Sure, there are folks that would like Adobe to add XAML support to Illustrator, etc., but at least there are very good, and complementary tools for folks doing Silverlight 2.0 development
So that’s a look at what I think is important and exciting about Silverlight 2.0 and it’s release this week.
I hope you’ll share your thoughts on the subject with me.
Check out the .NET Developer “Buzz”
Or just find a bunch of smart folks to follow on Twitter.
Do you know about Microsoft.com/web ?
Wanna get up and running quickly ?
Wanna auto install free ASP.NET or PHP Applications on your Windows Stack.
Then this is some real coolness for YOU !
Previews are below.
Hop over to http://www.microsoft.com/web to download and be sure to check out the other cool news and resources !!!\
The Web Platform Installer Beta (Web PI) provides a single, free package for installing and configuring Microsoft’s entire Web Platform, including IIS7, Visual Web Developer 2008 Express Edition, SQL Server 2008 Express Edition and the .NET Framework. Using the Web Platform Installer’s simple user interface, you can select specific components or more…
The Web Application Installer (Web AI) is the smoothest way to install the freely available PHP and ASP.NET applications on the IIS Web Server. Simply select the applications you want, enter your personal configuration, and click a button. Web AI even checks that all the database and framework components more…
Last night I was catching up on the day’s Twitter exchanges when I can across a conversation between two Microsoft employees.
One of the participants was a member of my team and another was member of the Microsoft “field” DPE organization.
The “DE” was telling the guy on my team that “whether he liked it or not, he working in a marketing role”.
I thought, man, if that DE was so clueless about what my team does, then tons of our customers don’t know what my team does either.
I suppose it makes sense. For years it was just me and the team owner (Simon Muzio). It’s only been in the last year that we became a full blown team.
The confusion in the aforementioned conversation might start with the fact that a DE (Developer Evangelist) IS a marketing role. A DE’s job is to drive awareness and adoption of Microsoft Developer Tools and Platforms. Their salaries and activities are primarily funded by a marketing organization.
They do this, for the most part, in very concise geographic areas. For example, there are New England DEs who focus exclusively on developers and customers in the New England geography. (Though there are some “Corporate DEs” who focus on specific technologies with no geographic restriction.)
Now, the DE role has changed in recent years and continues to do so. DE’s are no longer measured on sales impact; they don’t track their revenue impact, etc. But their role is to be expert in Microsoft’s Developer Technologies, to engage customers in their geographic areas, primarily in 1-to-many activities and increase the adoption rates of Microsoft’s products as well as increase the satisfaction levels f our developer customers.
That’s not what my team does.
We don’t really have a team name as yet, though internally we are sometimes refer to as ScottGu’s Secret Ninja Army ☺
Simon Muzio manages my team and apart from our general charter we have the agility to do what Scott Guthrie thinks is important on a week-to-week basis.
My team consists of the following folks:
• Joe Stagner (Me) – Focusing on Web Technologies with specialties including Security, Scale and Performance, Non-Microsoft Web Developer Technologies, interop, and relative business issues.
• Jesse Liberty – Focusing on Slverlight
• Tim Heuer – Focusing on SIlverlight (Tom and Jesse divide up areas of Silverlight)
• Steven Walther – Focusing on ASP.NET MVC
• Scott Hansleman – I’m actually not exactly sure what Scott does but he moves between technologies and focuses a lot on unreleased technologies.
• We have a collection of great support staff that does things like media production and web site management.
So, apart from each of our technological specialties, WHAT do we do and how do we differ from “Developer Evangelists”.
First, we are actually ON The product teams, our salaries are paid from R&D not sales and marketing. This means that our focus is different than that of Developer Evangelists.
Yes, we also do a lot of 1-to-many activities, but to a different end than driving sales and adoption
Our role is two fold.
1.) To communicate product details and strategy (and thereby catalyze real and full understanding of the technology’s intent) directly from the folks who design and develop the products
2.) To ACTIVLY solicit feedback from developers, to aggregate that feedback and present it to the product feature teams and thereby by shape the developer products that we are developing today and that we will develop tomorrow.
The 1-to-many activities that we do are, in large part, simply the vehicle that we employ to connect with many, many developers in order to gather the data we need to positively affect the product our teams build.
While all Microsoft employees are interested in customer satisfaction and adoption, my team’s positive results in these areas might be thought of as by-products of the ongoing conversations that we MUST have with customers in order to bring much needed data back into the development process.
They are not the end target result of our activities.
While both teams are important to the Microsoft Developer community, I think this difference is very important, both for developer customers to know, and for DEs to understand.
DE work primarily with the product that we release.
Our team’s role is to help DETERMINE what those products should be.
Anyway, that’s what our team does (I think – might be different next week.
In addition to my real job, I’ve been building a recreation area (1000 SqFt) on the side of my house for the kids.
Each evening I put in an hour or two. This photo was taken last night. I’m on my knees while my children are enjoying the hot tub
Since I do allot of PHP programming and more and more PHP Developers are using MacBooks, I’ve started doing some Coding on the Mac and cross platform testing of PHP on the Mac and then on Windows.
It’s funny, though I use my MacBook daily, I seldom use OSX. I’ve found the MacBook Pro to be a fine host for Virtual Machines.
I spend several hours every day answering customer email and more and more I’m asked questions about versions that I don’t have installed on my machine due to limited disk space or compatibility issues. So, I’ve finally gotten to a place when I need to get virtualized so that I can support older versions of Visual Studio, etc.
So, I’ve decided to do this with my Mac.
For about $230 I got a 320 Gig 7200 RPM SATA Hards Drive and 4 Gig of RAM from NewEgg and a screw driver kit with the NECESSARY T6 screw driver.
I’ve upgraded Mac Desktop hardware before. G3s were easy, iMacs were less easy but my MacBook Pro was a pain in the ass on the hardware side.
I like my MacBook Pro hardware. It’s “sleek”. But not at all designed for end user hardware updates.
My Lenovo, Toshiba, and Compaq Laptops let me change hard drives in under a minute.
The MacBook pro is a MAJOR disassembly. Something like 25 screws. Disassemble the entire case, remove the keyboard, etc.
20 minutes minimum.
Having said that, you don’t know how much Time Machine ROCKS until you install a new hard drive.
After I installed the new drive and the new memory (anybody want to buy 2 gig for their MBP ?), I fired it up and held my breath.
After booting from the OSX DVD, I provisioned the new drive and selected restore from backup.
Selected the Time Machine backup I made yesterday, and BAM! 90 minutes later I have my machine just as it was yesterday except faster and 200 gig of extra disk space.
No reinstalling the OS, no reinstalling (and finding the serial numbers) for all my software!
It “just works”.
Note to Windows Visa Team, need that for Vista !!!
No question it’s faster. Eclipse loads in just a few seconds.
Now – building VPCs !
Very cool !