Now that's better than just a "lisp?" reply!
C
'M' is already in use as the name of an existing ANSI-Standard language (X11.1-1995) with quite a long history behind it.
Since when did all the hate for xml and soap start? I missed it. I think json is easier to look at, but did it win all around and nobody told me? Doesn't WCF use soap at the bottom?
I feel slow here, but this is about the 3rd video I have seen on M, and still don't understand what it is or why I need it? Is this an n-tier solution. Will I be able to write an M model (w/ types) in VS and click deploy to setup the DB (to sql or Azure)? I assume that is the Write/Mod stuff your working on.
WCF is flexible, you can configure it to use different encodings including (since 3.5 SP1) JSON.
May be [probably is] a fail on my part but is the Zune WMV file broken?! Thanks.
Hi, can you elaborate? The file plays for me.
What is wrong with WSDL? Can someone elaborate what is wrong with it from the design perspective? Consuming a service that exposes WSDL is easy to consume in Visual Studio.