Posted on 06/23/2012 7:18:05 AM PDT by SmokingJoe
Many have scoffed at the idea that Redmond's tablet will succeed. But there are three crucial reasons to take the effort seriously. By Don Sears
FORTUNE -- Do not underestimate Microsoft's Surface tablet move. Its gambit to design and build its own hardware is a bold play to develop a thriving ecosystem of new products. It is centered on Microsoft's dominant property: the operating system. Monday's flashy Surface launch may have felt like an Apple event with its bright, pastel-colored keyboard, slick introductory videos and breathless hyping from little-known engineers. But, in fact, Microsoft's play is anything but Apple-like. The company is clearly trying to make tablets into hybrid PC-mobile devices, something its California rival has said is a bad idea. We don't yet know all of Surface's details -- battery life, pricing, official release dates are all to-be-determined for instance. But here are three important reasons Microsoft's Surface is likely to be anything but dead on arrival:
Reason #1: Microsoft can build an ecosystem
Microsoft (MSFT) has had success in the consumer market with the Xbox and most recently with the Kinect motion-control devices. The Xbox has become a household name with major brand extensions as an entertainment device. Microsoft disrupted gaming, and it can disrupt hardware.
Microsoft has serious engineering chops. Josh Topolosky, Editor-in-Chief of The Verge and not exactly a fanboy, was blown away by a visit to Microsoft's R&D in 2011. He wrote of that visit: "[MS] showed me a project
which would allow you to create a virtual window from one room to another, utilizing a variety of display, motion sensing, and 3D technologies
dubbed
the 'magic wall.' It was nuts. It was awesome. It was ambitious. The whole time, all I could think was: where has Microsoft been hiding guys like this?"
(Excerpt) Read more at tech.fortune.cnn.com ...
What is RPC mean?
I’m not in the market for any TabletToy at this time, but just one look at that ridiculous screen format (what is that, 2:1?) would immediately make me look elsewhere.
DOS isn’t done until Lotus won’t run.
RPC = Remote Procedure Call.
Aka WCF aka DCOM/COM aka OLE aka...
XEROX/SRI RPC
http://www.google.com/#hl=en&sclient=psy-ab&q=XEROX+SRI+Remote+Procedure+Calls
There is nothing new under the Sun.
Microsoft deprecated RPC (DCE) in Windows 8 and is switching to WS-MAN (WinRM) for remote management and control. For example the new Server Manager in Windows Server 2012 is all WinRM.
See http://redmondmag.com/blogs/it-decision-maker/2012/05/ws-man-in-remoting.aspx
Microsoft deprecated RPC (DCE) in Windows 8 and is switching to WS-MAN (WinRM) for remote management and control. For example the new Server Manager in Windows Server 2012 is all WinRM.
See http://redmondmag.com/blogs/it-decision-maker/2012/05/ws-man-in-remoting.aspx
Microsoft Newspeak.
The Service Interface of WCF is an implementation of RPC.
Quack, Waddle, Duck.
Glad to hear that.
And I’ve seen nothing from MonkeySoft to indicate the clipboard isn’t still DDE, aka Windoze 2.0 RPC, either.
http://en.wikipedia.org/wiki/Dynamic_Data_Exchange
WS-MAN (WinRM) is emphatically not RPC (DCE) based. It is SOAP based. There is no IDL, no huge range of TCP ports to firewall, no 32-bit/64-bit argument translation, just XML. There is no ‘remote procedure call’ per se, but rather alerts (like SNMP traps) and info requests (like SNMP queries). WinRM is based on WMI, which is more closely related to SNMP (with its MIBs) than any RPC implementation like OSF DCE or Sun XDR/RPC.
WCF is just a .NET API for communication. It is orthognal to RPC and WS-MAN (it can access both).
They can call it whatever they want. Whether Im consuming a WCF service from a Delphi SOAP client/WSDL, or via a proxy using a net.tcp binding, the functional end result is the same:
An interface to an remote object.
Quack, Waddle, RPduCk.
>>WCF is just a .NET API for communication.
No. Its a robust framework for persisting a remote interface to, and serializing data between, remote objects via a variety of bindings.
IOW, whatever the M$hills are calling it its just DCOM/OLE/DDE/RPC for the Internet.
Hopefully they'll have better luck getting away from that than they did with WINS.
Now, that's funny! They are probably right. After all, Microsoft did make an mp3 player for them (zune).
I haven't had a chance to look into this specific case, but knowing the history it could either be a completely rewritten communications subsystem, or a WCF call is just a wrapper over the same old DCOM routines. OTOH, from what I've heard the whole TCP/IP stack has been rewritten, so hopefully these got the same treatment.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.