Slashdot Mirror


Microsoft Dilutes Open Source, Coins 'Open Surface'

sfcrazy writes "Now, Microsoft is coining yet another term to further confuse users — 'Open Surface.' Senior Director for Open Source Communities at Microsoft, Gianugo Rabellino, said at Oscon 2011 that customers don't care about the underlying platform as long as the APIs, protocols and standards for the cloud are open. That's when he threw the term 'open surface.'" This seems to have more than a grain of truth to it — after all, programmers have been creating open-source software with closed-source programming languages for many years, and I'm certainly more impressed by Google's willingness to let me export my data than I am turned off by the fact that they use a mix of open and closed source software to run the Google circus.

31 of 191 comments (clear)

  1. Embrace, Extend, Extinguish by Gr33nJ3ll0 · · Score: 4, Insightful

    I believe this is step 2

    1. Re:Embrace, Extend, Extinguish by starfishsystems · · Score: 4, Insightful

      Indeed. I'm glad you got first posting for this.

      It's not that specifications and standards aren't important. Of course they are. But Microsoft is more than a bit disingenuous in pretending to advocate them when it has been so egregiously, perennially active in undermining them. This hypocrisy is all too familiar.

      Thanks, Microsoft, for reminding me why I loathe you.

      --
      Parity: What to do when the weekend comes.
    2. Re:Embrace, Extend, Extinguish by TheRaven64 · · Score: 4, Insightful

      The problem is that API's, protocols and standards pretty much never are open without releasing a reference implementation.

      Not true. In fact, having a reference implementation is a good way of making a kludgy standard. The IETF's requirement, for example, does not require a reference implementation. It requires two independent implementations. If the standard can't be implemented by two groups who aren't sharing code then it's not a standard it's just documentation.

      --
      I am TheRaven on Soylent News
    3. Re:Embrace, Extend, Extinguish by TheRaven64 · · Score: 2

      And that was a good reason. The WebDB specification said 'accept the SQL that SQLite accepts'. It was a horrible specification. SQLite is okay, but creating a specification that requires SQLite to implement it correctly is horrible. A client-side SQL API for the web should define the exact subset of SQL that it accepts and it should be possible to implement it on top of any SQL database with a query validator, or on top of a your own storage mechanism with a SQL parser.

      --
      I am TheRaven on Soylent News
  2. What is the point of the linked page? by ToasterMonkey · · Score: 3, Insightful

    This is so backwards from Slashdot norm. A summary with a tidbit of "news" in it and intelligently written opinion, no FA to read.

    Am I missing something, did Microsoft not really coin this term or is there some biased, slanderous opinion that was unintentionally left out of the summary?

    1. Re:What is the point of the linked page? by Sulphur · · Score: 5, Funny

      This is so backwards from Slashdot norm. A summary with a tidbit of "news" in it and intelligently written opinion, no FA to read.

      Am I missing something, did Microsoft not really coin this term or is there some biased, slanderous opinion that was unintentionally left out of the summary?

      In other words, an Open Surface post.

    2. Re:What is the point of the linked page? by Anonymous Coward · · Score: 3, Informative

      Submitter is an idiot.

      Anyway, for a coherent link, zdnet, which has more than three sentences. What it boils down to is that the Microsoft Azure platform is not open source - but how to interact with it is well known and open. You can then run Open Source programs on top of a closed-source platform.

      To be honest, I think it's a complemntary idea to Open Source; and I'm not sure that he explicitly set out to 'dilute' the term open source.

    3. Re:What is the point of the linked page? by GumphMaster · · Score: 3, Interesting

      I'm not really sure how this differs from typical APIs where the programmer...

      One is a marketing term that Microsoft can slap a trademark application in for, the other is not? Then Microsoft can claim to be the only vendor with Open Surface(tm) systems, or OSS.

      --
      Patent litigation: A doctrine of Mutually Assured Destruction... in which everyone seems willing to push the button
    4. Re:What is the point of the linked page? by rtb61 · · Score: 2

      It is all about thinking for today versus thinking for yesterday, today and tomorrow. You might know the current APIs, protocols and standards but when the underlying platforms are closed off from input and control, you have no idea what you will have to deal with tomorrow and how that will affect what was done yesterday.

      When it comes to M$ they have been unreliable, manipulative, insensitive and arrogant. If it saves them money and enables them to make more whether it be saving costs by not fixing bugs and security faults, holding out on simple improvements and forcing upgrade cost plus lost productivity for years waiting for upgrades or simply dumping their costs on end users to be replicated millions of times.

      So lack of control of the underlying platform in many other areas of computing have wasted billions of dollars, a lesson that should be and never forgotten. It would be the same to hand over all infrastructure services to one for profit corporation, like roads, rail lines, airports, footpaths, bridges, electricity, storm water and sewer and expect things to term out well without being screwed at every turn. That kind of thinking was OK early on in the computer industry but just doesn't make any sense at all any more.

      --
      Chaos - everything, everywhere, everywhen
  3. Re:Everybody knows about open interfaces by Midnight+Thunder · · Score: 2

    Chalk this down to a marketing team with nothing better to do.

    --
    Jumpstart the tartan drive.
  4. "Published API" by Alex+Belits · · Score: 3, Insightful

    It's called "published API".

    Microsoft, as usual, is trying to conflate "published protocol" (an interface that can be used by independently developed software that may share no components with software providing interface) and "published API" (an interface that requires direct use of software providing the interface within common framework such as libraries, plugins, compilers' handling of interface definitions, etc.)

    Shut up, Microsoft. Nothing short of published, open protocol is going to suffice. And none of your products will survive if you won't hide and obfuscate protocols used by them. You know that and we know that, so don't pretend that you are not our enemies.

    --
    Contrary to the popular belief, there indeed is no God.
    1. Re:"Published API" by shutdown+-p+now · · Score: 2, Informative

      "published API" (an interface that requires direct use of software providing the interface within common framework such as libraries, plugins, compilers' handling of interface definitions, etc.)

      It doesn't. You can take a published API, and provide your own clean-room implementation of the same - see .NET/Mono.

      Nothing short of published, open protocol is going to suffice.

      http://www.microsoft.com/openspecifications/en/us/technical-specifications/default.aspx

    2. Re:"Published API" by shutdown+-p+now · · Score: 2

      I am describing normal use, not reimplementation.

      In normal use, there's no difference between e.g. a network protocol and a shared library interface. Both are ultimately about pushing some bytes in, and getting some bytes (and side effects out). That in one case your bytes are packaged in packets and sent between processes and computers, and in another they are pushed onto the execution stack, is immaterial.

      Mono is a failed reimplementation of a useless product.

      Your expert and well-referenced opinion on this will doubtlessly be extremely valuable to people who mistakenly use either or both in their products with great success.

      And none of that is actually useful for interoperability or reimplementation.

      AD and Exchange protocols are not useful for interoperability or reimplementation? What happened to the holy grail of making full-fledged FOSS replacements for either one?

    3. Re:"Published API" by Sloppy · · Score: 2

      People like you will always deride anything MS does because if you didn't have MS as your enemy you wouldn't have anyone to hate on.

      As long as there is unmaintainable software, users (and any programmer who empathizes with them, or who values economic efficiency) will have enemies. You don't need Microsoft for that, but they sure help. :-)

      Documented APIs are a fine start, and as long as the size/complexity of the components that provide these APIs is small/simple enough, the resulting systems can approach the maintainability of Free Software. Just as a high-level language programmer doesn't worry about the object code that one of his lines of code compiles to, a bash scripter might not worry about using a proprietary awk or sed alternative, as long as it behaves in a known way. If there were a problem with MS sed, you could replace it with GNU sed, so MS sed's unmaintainability wouldn't matter. (And therefore, if MS sed had any advantages, such as speed, using it might indeed be tempting and relatively low-risk.)

      But somehow I doubt anyone thinks Microsoft has systems this small in mind, or that they are considering using APIs that have already been implemented by other tools. And of course as others have mentioned, there's always the threat that a documented API might be specified in such a way that implementing it at all, could require getting a patent holder's permission before you're legally allowed to do it. If you can't easily replace an API-well-documented component, then all the maintenance headaches of proprietary software are in full force, and the "Open" aspect of its "Surface" is useless to you.

      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    4. Re:"Published API" by unity · · Score: 2

      You know that and we know that, so don't pretend that you are not our enemies.

      Speak for yourself; MS is my sugardaddy and I like it that way.

    5. Re:"Published API" by unity · · Score: 2

      Mono is a failed reimplementation of a useless product.

      That is funny, I coulda sworn that my customers put through hundreds of millions of dollars of sales on .net software every year. Hell of a useless product.

  5. Free Surface by Stradenko · · Score: 2

    I'll be the first to coin "free (as in freedom) surface."

  6. open APIs must remain open by petes_PoV · · Score: 4, Insightful

    as long as the APIs, protocols and standards for the cloud are open

    The key thing is to ensure that the APIs cannot be controlled, or changed or withdrawn or have conditions of use imposed on them. Open means more than just having them documented.

    The only way to ensure that the APIs remain usable is to have the ability to rebuild the underlying software, rather than simply have a third party provide us with it - where the way the API is still under their sole control. To do that requires unencumbered access to the source code, and the entitlement to copy it and make other things that use it.

    Without those abilities, there will always be the possibility that the original owner could arbitrarily change it, refuse to support it, add private functions and features or prevent certain classes of users from benefitting from it. These are the attributes that make free software valuable.

    --
    politicians are like babies' nappies: they should both be changed regularly and for the same reasons
  7. Security by obscurity, still... by jenningsthecat · · Score: 4, Insightful

    Whether or not this is a move to co-opt FOSS, I can't say, although I have my suspicions. But from a security standpoint, it sucks. Security breaches are becoming more and more common; with the underlying code being closed, there can be no independent confirmation of the quality of security measures, patches, etc. So when a vulnerability is found and 'patched', we still won't have any assurance, beyond Microsoft's say-so, that the patch fixes the problem and doesn't introduce any new ones.

    This announcement doesn't really change anything, and on the face of it it's non-news. But as propaganda, it stands a good chance of getting more people to drink the MS Kool-aid. And remember when MS used to use undocumented OS calls to give their own applications an edge over competitors? I think we can expect such abuses to increase greatly - the appearance of openness will hide what's really going on.. The 'surface' may be 'open', but the underlying code, and the underlying politics, are murkier and more closed than ever.

    Besides, 'Open Surface' sounds rather shallow, doesn't it?

    --
    'The Economy' is a giant Ponzi scheme whose most pitiable suckers are the youngest among us and the yet-unborn.
  8. There's nothing to dilute. by thegarbz · · Score: 2, Insightful

    His revelation is right on the mark. I constantly see proponents of Open Source say things such as "It's auditable because the source code is free". Well yes it is, but no one cares. I think even from the Slashdot crowd the number of people who bothered to build Firefox from source is a small minority compared to those who downloaded it. Those who actually look at the code are an even smaller subset of those bothered to build from source.

    People talk about open source as if users give a damn. Users are only interested in 2 things, how much it costs, and if it works. Open APIs are part of the ability for something to work if your idea of working is interoperability.

    1. Re:There's nothing to dilute. by Jah-Wren+Ryel · · Score: 3, Insightful

      "It's auditable because the source code is free". Well yes it is, but no one cares. I think even from the Slashdot crowd the number of people who bothered to build Firefox from source is a small minority compared to those who downloaded it

      That exact same logic condemns "open surface" too - the vast majority of customers don't give a damn about documented interfaces, they just want to use the product.

      It's only a very tiny minority that need to get their hands dirty. And of that tiny minority, only a minute fraction are good with "open surface" but not actual open source. The minute that one of those API's turns out to be only partially documented, or the code behind it buggy, or disabled for marketing reasons, then those same people now need real open source and not a sucker's stand-in like "open surface."

      --
      When information is power, privacy is freedom.
    2. Re:There's nothing to dilute. by Robert+Zenz · · Score: 2

      There's a difference between "having the right to vote", "actually voting" and "STFU I'm in charge!".

  9. Patents covered seperately by Anonymous Coward · · Score: 5, Insightful

    I believe the following statement on the front page says it all:
    "rights under Microsoft patents covering such specifications are available separately"

  10. Strawman attack by enoz · · Score: 3, Interesting

    Published APIs are important, nay, necessary for "cloud" applications and services to be useful to developers to build upon. Open source is necessary for community based development of the underlying applications or services.

    Open source software is completely irrelevant in this instance and this appears to be a simple strawman attack from Microsoft against the open source movement.

  11. Customers or Providers? by Bob9113 · · Score: 5, Insightful

    > customers don't care about the underlying platform as long as the APIs, protocols and standards for the cloud are open.

    That seems true. Customers want openness in the part that they deal with. Since the customer does not deal with system maintenance and development, he does not care whether the underlying platform is open. The provider of the cloud service, on the other hand, has a deeply vested interest in the openness of the platform. Maintenance, repair, and extension requirements all strongly favor an open platform from the cloud service provider's perspective.

    Pointing out that the customer does not care about platform openness as long as the protocol is open is a bit like saying that automobile drivers do not care if the paving crew uses horse-drawn paving machines as long as they get the job done in a timely manner. It does not necessarily follow that horse-drawn paving machines make sense.

  12. You can have ... by PPH · · Score: 2

    ... any style house you can. As long as its built in our company town, we own your ass.

    --
    Have gnu, will travel.
  13. Open source allows someone else to fork by erice · · Score: 2

    His revelation is right on the mark. I constantly see proponents of Open Source say things such as "It's auditable because the source code is free". Well yes it is, but no one cares. I think even from the Slashdot crowd the number of people who bothered to build Firefox from source is a small minority compared to those who downloaded it. Those who actually look at the code are an even smaller subset of those bothered to build from source.

    It isn't necessary for a user to personally view, modify, or even compile the source to benefit from open source. At some point the copyright holder may add shovelware, spyware or just plain bugs. They may choose not to port to other platforms. They may just abandon the product. In these cases. a user of a closed source app can do little but continue to use the old version until it no longer runs on current platforms or until advanced security threats make it unsafe.

    But as long as one person has the will and ability to adopt what the developer has effectively or literally abandoned, the freeloaders can still their updated binaries. They won't be exactly what they wanted but the freeloaders never had or asked for that anyway.

  14. Who does that server really serve? by joeaguy · · Score: 3, Interesting

    All I am going to say to those of you who think "open source" does not matter is read Richard Stallman's paper "Who Does That Server Really Serve?"

    http://www.gnu.org/philosophy/who-does-that-server-really-serve.html

    Having open and honestly published API's and protocols is important and certainly better than nothing, but there are so many other reasons why access to source code is important for trust and freedom in computing.

  15. Re:Simple solution. by kevinmenzel · · Score: 2

    Um... what? That's not what the word "open" means. If a door is "open" is might at some point in the future be "closed". The word open describes the current state of something.

    Unless you mean "Take the word as it is given the specific context I will now thrust upon it, thus defeating the point of my own argument that the word has a specific universal meaning"

  16. Re:Embrace, Extend & try the tuna salad by Hognoxious · · Score: 2, Funny

    Look on the bright side - with M$ involved nobody's going to suggest intelligent design.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  17. Open Cybercloud by qxcv · · Score: 3, Funny

    Is it just me, or are open* and cloud* becoming the new cyber*?

    Middle manager: "Hey, did you try the new CyberCloud 2.0 Open-Surface ® operating system by OpenMicrosoft ®?"

    MS patent goon: "You bet your Zune ® I did! It allows me to innovate my value-added cyberdata to enhance availability in scalable cloud based enterprise architectures channeling an enterprise virtualisation solution, thus leveraging existing ROI and increasing key delivarables as per OpenMicrosoft ® BestPractise ®!"

    --
    "The most dangerous enemy of a better solution is an existing codebase that is just good enough." -- Eric S. Raymond