Jon Udell cURL's with SQL Server Data Services
Just read Jon Udell's post on SQL Server Data Services (SSDS) here. Happy to hear that Jon was able to explore SSDS with cURL "within minutes of cracking open the SSDS documentation". Readers who are wondering what Jon is talking about, should read Jeff Currier, one of the guys writing real code that we ship in SSDS, talking about using cURL to explore SSDS here.
When few of us crazies started thinking of SSDS, a non-negotiable requirement was that developers should be able to start exploring and using the service quickly. There is so much going on in the cloud services space that if it took too long to experiment with a new service, we were afraid that developers will put it on the shelve and may never give it a spin. I know I do not like to spend months on something to see if I would use it. It was hard for us to "cover up" the SQL Server heritage of SSDS, but we argued that simplicity is a virtue that we should aspire to.
Jon hits on an interesting point when he says 'while the novelty of “just coding to a URL” on a Microsoft platform will undoubtedly attract some tirekickers who otherwise wouldn’t show up, the real draw will be the ability to exercise choice along the whole continuum'. Internally we use the words "reach" and "rich". We believe that to be a platform with large adoption, one needs to provide both "reach" (so that people from all other platforms can use you) as well as "richness" (so that people who use your platform exlusively have a rich set of tools to leverage). Today it is easy to see that SSDS is aiming to "reach" as many developers as possible. To do this we have to address "the continuum of access styles". Jon seems to be saying that we are meeting that goal. What do you think? Are we close? Are we way off base? Or we should not worry about the "continuum of access styles".
It will be interesting to hear from you all.
