- Revealed: The jobs that will be wiped out by cloud computing | TechRepublic
- Latency numbers every programmer should know — Gist
- HIPAA Compliance Cheat Sheet for Cloud Storage – Symform
- Twitter / justinwolfers: A passive-aggressive nudge - RT @R_Thaler: Agree“@justinwolfers: A passive-aggressive nudge. I bet it works. (cc @R_Thaler) ”
- The rise of the 17-hour journalist... | ZDNet - "The stark economic reality of the media business is that there’s little money in producing original content. In a world where a click is a click, and has about the same value, regardless of the quality of the underlying journalism - it is the means of production that defines the final product. Henry Blodget and the Business Insider editorial team aren’t the ones responsible for the poor state of journalism today, they are merely the expression of what’s currently possible given the means available - which isn’t much, a whole lot of nothing much (about 250 news stories a day at Business Insider). We desperately need a viable mass-media business model that rewards quality journalism. It’s one of the most challenging problems we face as a society, and one of the most elusive."
- 11 reasons your infographic isn’t an infographic
- Irish Mathematicians Solve The Guinness Sinking Bubble Problem - Technology Review
- MacSparky - Blog - About Apple Rumors - "Sadly, the Apple rumors just magnify everything that is wrong with the Internet’s busted click to pay advertising model and Apple rumors will continue as long as people can make a few pieces of silver on it. What we can do, however, as a community, is not click, not cover, and generally ignore this fictitious digital vomit."
- 2012 Internet Trends — Kleiner Perkins Caufield Byers - Mary Meeker's latest.
- Stop Visually Assaulting Me. - Nice, succinct dos and don'ts.
- An Early Summer Dinner On The Grill - Saveur.com
- Java WORA Defences Spent? - Simon Says...
- New ‘Digital Divide’ Seen in Wasting Time Online - NYTimes.com - Not convinced there's really anything new here. Just new ways to waste time.
- Going Paperless on a Mac - ProfHacker - The Chronicle of Higher Education - "In “Stanzas from the Grande Chartreuse,” Matthew Arnold famously lamented that he finds himself “Wandering between two worlds, one dead, / The other powerless to be born.” A Victorianist by training, I feel confident in saying that Arnold refers here to the well-known problem of having lots of tools for managing digital information, and for digitizing yet more, and yet somehow still finding oneself overwhelmed by stacks of paper. The journey to a paperless workflow often feels like a two steps forward, 1.8 steps back affair."
- Mass. and MIT launching big data initiatives - Business - The Boston Globe - "Research conducted by the bigdata@CSAIL initiative will focus on domains such as finance, medicine, social media, and security. Sam Madden, an MIT associate professor and leader of bigdata@CSAIL, said one project would be “to develop more sophisticated tools for in-depth processing of medical information, which could lead to more accurate diagnostic techniques and better treatment methods for patients.”"
- Leadership Development in the Age of the Algorithm - Harvard Business Review - Seriously????? "Log on to your Facebook page, look at the column on the right, and you will see ads that seem uniquely relevant to you."
- Cloud migration: The applications killing season • The Register
Thursday, May 31, 2012
Tuesday, May 29, 2012
Manhattan is going to be cloud computing central from June 11 to 14.
Cloud Expo is something of the center of gravity, but there's plenty else going on. CloudCamp NYC is on the evening of June 12. It's free and they're always great events with lots of interaction. On Wednesday, Rishidot Research is organizing DeployCon, an Enterprise PaaS Summit. This new event cuts right to one of the hottest topics in cloud computing--bringing together the developer-friendliness of PaaS with the operational needs of enterprise IT.
I'm going to try to spend some time at all three of those events, but what I'm most focused on is the Open Data Center Alliance's Forecast 2012 conference on Tuesday. The ODCA is a consortium of major IT organizations including, notably, large end-users; it's no vendor smoozefest. The idea is to identify customer requirements and to influence industry innovation to address those requirements. One such example is virtual machine interoperability, as is demonstrated in this Red Hat video using our CloudForms open hybrid cloud management software.
The event has a great lineup. For my part, I'll be a panelist at a pair of Forecast panels: one on software innovation and one on regulation. I'm excited about these panels for two reasons.
The first is that the organizers are doing a bang-up job of doing their best to ensure that these panels don't embody all those things that make us dread panels. You know what I mean. By the time everyone is done clearing their throats and telling you how smart they are, there's only time left for all the panelists to give more or less the same long-winded answer to a couple of desultory questions. No panelist slides on these ones. And I can assure you that the panelists are now quite familiar with terms like "rapid fire" and "interactive" as we've gone through our prep calls. The sad thing is that panels often have great potential. That potential is just so rarely achieved. I'm hopeful for these ones.
The other is that the topics for the two panels on which I'll be sitting are really interesting to me. I'm not going to steal my thunder in advance here, but I wanted to share a few thoughts in advance.
Rapid Fire Panel: Cloud Regulation (2:35-3:20)
Moderator: Deborah Salons
Brett Smith, Deutsche Bank
José E. González, Chief Business Development Officer, Trapezoid Digital Security Services, LLC
Gordon Haff, Cloud Evangelist, Red Hat
Marvin Wheeler, Chairman and Secretary, Open Data Center Alliance
There are a lot of aspects to regulation but, given that I am neither a lawyer nor a governmental affairs expert, my real interest here is where regulation and technology interest. From the perspective of cloud computing--and cloud computing within large organizations in particular--my concern lies with questions such as how appropriate policies can be embedded in applications and control mechanisms so that automated processes don't run afoul of regulatory regimes. This is an important question because automation means "Hands Off!" Start interjecting manual processes to deal with regulatory requirements and you can't realize the benefits of automation.
Cloud Software Innovation Panel (1:50-2:35)
Moderator: Richard Villars, Vice President, Information & Cloud IDC
Elad Yoran, Chairman and CEO, Vaultive, Inc.
Gordon Haff, Cloud Evangelist, Red Hat
Greg Brown, McAfee
John Engates, CTO, Rackspace
Reuven Cohen, Senior Vice President, Virtustream
This should be an interesting discussion. On the one hand, some question whether open source matters in the cloud even while almost all of the top public clouds have open source as their foundation. Their argument revolves around the fact that availability of source code doesn't have the same meaning in a world where software services are often delivered over the network and are intimately tied to the data and compute infrastructures on which they run. However, I'd argue that open is both a bigger and a broader issue in cloud computing as I wrote in Why the Future of the Cloud is Open.
How does this relate to software innovation? It relates because, even if open source historically was often about cheaper substitutes for expensive proprietary software, it's now more and more about fostering innovation through communities, including user communities. Is open source the only mechanism through which innovation can happen? Of course not. But it's a powerful mechanism as are other aspects of openness such as open APIs.
Friday, May 25, 2012
- Doc Searls Weblog · After Facebook fails - "But totally personalized advertising is icky and oxymoronic. And, after half a decade or more at the business of making maximally-personalized ads, the main result is what Michael calls “the desultory ticky-tacky kind that litters the right side of people’s Facebook profiles.”"
- Kodak was never going to be the Kodak of digital photography | Challengers - CNET News - "It's also not as if some other company has emerged as the Kodak of digital. In the company's golden age, consumers used a Kodak camera to take pictures on Kodak film, which they then had processed by a Kodak lab on Kodak paper. Today, no single company has replicated that ecosystem in digital form. There are camera manufacturers, and memory-card manufacturers, and printer companies, and photo-sharing sites--and all of these businesses benefit from healthy competition among multiple major players, rather than the monopolistic position that Kodak once enjoyed."
- Facebook IPO Post Mortem – Killer – but not for the reasons you think ! « blog maverick - Cuban hits some key points. It's even harder to monetize with ads in mobile and he (I believe correctly) notes that we're moving away from all-you-can-eat mobile data which will make the situation even worse.
- Stealing the Shows - TIME - RT @poniewozik: Fox suing over Auto Hop ad-skipper. I have a (pre-suit) column on it this week: my life as a TV thief.
- Secret memo reveals which telecoms store your data the longest | Ars Technica - Not sure I buy that only Verizon retains text message contents. The others must store it somewhere for some length of time in order to transmit it, e.g. to phones that aren't currently on.
- The Facebook Fallacy - Technology Review - Some good discussion in comments here about limitations of gaining insights from even large qtys of data.
- Java creator unhappy with Oracle trial outcome | ITworld - Seems to sum things up pretty well (though I'd leave out the word 'sadly'). -- "Based on testimony in the trial, and remarks from Gosling and others, it's clear that whether they meant to or not, Google very much irked people at Sun Microsystems when Google decided to bypass Java and go with a clean-room implementation of Java in the form of the Dalvik VM in Android. And "irked" is probably an understatement. But sadly, you can't really sue people for being jerks. And there's also the argument that Sun may have forced Google's hand by dual-licensing Java under the GPL and a proprietary license for commercial use. That was certainly Sun's prerogative, of course, but it doesn't completely jibe with their much-touted "Java is free" mantra."
- Create Custom Skins for Laptops & Netbooks | GelaSkins - This is very cool. You can create laptop skins with your own photos.
- Update: Mike Lynch leaves HP Autonomy - ComputerworldUK.com - RT @maslett: "the entire management team and 20 percent of all Autonomy's staff have left since the HP takeover"
- Opposing the New York Public Library - The Daily Beast - RT @thedailybeast: A battle for New York Public Library's (@NYPL) soul prompts the question: Who's reading the books?
Wednesday, May 23, 2012
- Jonathan Ive interview: Apple's design genius is British to the core - Telegraph
- Skilling up for Cloud architecture & planning | The Cloud Evangelist
- Sheryl Sandberg Is The Valley's 'It' Girl - Just Like Kim Polese Once Was - Forbes
- OSI Board Elects New Officers | Open Source Initiative - RT @richsands: “@robilad: "The board is happy to announce that ... Simon Phipps is the new President." ” Congrats @w ...
- The hype cycle of Vendor Briefing Requests « The IIAR Blog - RT @jpuppet: RT @cloudpundit Hype cycle of Vendor Briefing Requests <- hilarious .. (analysts get frustrated too ...
- (Humor) The Rosetta Stone of IT Industry Analysts | ZDNet - RT @IIAR: (Humor) The Rosetta Stone of IT Industry Analysts | ZDNet
- The Levelator® from The Conversations Network - Levelator did a nice job of fixing up a podcast I recently recorded with very uneven levels
- Identity Management in Red Hat Enterprise Linux - YouTube - A new (short) video about identity management in Red Hat Enterprise Linux
- The-Cloud-Computing-Debate-Cutting-Through-the-Cloud-Clutter - CA Technologies
- 30 Minute Video Limit in Digital Cameras May Be On Its Way Out - RT @petapixel: 30 minute video limit in digital cameras may be on its way out: << tariff related
- Oracle Itanium Exhibits Chronological
- How to Scan Film Negatives with a DSLR
- What's next after GPL and Apache? - "While the newest open source projects such as OpenStack and OpenShift have chosen to use the Apache License, a non-copyleft or "permissive" open source license with good patent protections, I believe in time we will see the licensing trend for new open source projects targeted at commercial collaboration swing back to the center, away from either the GPL or Apache extremities. Until recently, none of the mainstream "center ground" open source licenses has been optimal. These are the Mozilla Public License (MPL -- and its many "vanity name" variants), the Eclipse license, the CDDL (used widely by projects influenced by Sun Microsystems), and of course, the LGPL."
Thursday, May 17, 2012
Kurt Milne is the managing director of the IT Process Institute and has been surveying organizations about their cloud adoption. The most common strategy is to leverage existing resources where possible by taking an open, hybrid approach. Kurt is also co-author, along with Andi Mann and Jeanne Morain of Visible Ops: Private Cloud. Kurt discusses:
- Strategies for cloud adoption
- How open cloud approaches are proving most popular
- How organizations are achieving agility through self-service
- Owning vs. renting capacity
- How IT decision makers need to look at cloud through a framework of cost, benefit, and risk
- The need for a portfolio view
Listen to OGG (0:14:44)
Tuesday, May 15, 2012
- Making Choices in the Age of Information Overload - NYTimes.com - "The Internet is, among other things, a massive, chaotic marketplace. Too much information, it turns out, is a lot like no information. “If we researched every single purchase, we wouldn’t have time to make any purchases,” says Anna Kirmani, a marketing professor at the University of Maryland. “I have better things to do with my time.” Signaling can be a shorthand to identify whom you want to buy from. That’s why we may need it now more than ever."
- The Fertile Unknown: Improv Theater and Complex Adaptive Systems
- Death of a Saleman: A Heartbreaking Work of Staggering Mediocrity : The New Yorker - "Ten years later, at the Ethel Barrymore, I found myself squirming in my seat from boredom and exasperation, amazed at how much glaringly conventional stagecraft “Salesman” was able to pack into its two acts. The rising action, the dramatic irony, the laborious, grandstanding speeches (“Spite, spite, is the word of your undoing…When you’re rotting somewhere beside the railroad tracks, remember, and don’t you dare blame it on me”)—I kept wanting to exclaim, “It sounds like a play!”"
- How Yahoo Killed Flickr and Lost the Internet - Quite the read, though IMO somewhat overstated.
- Anatomy of an iTV rumor - Apple 2.0 - Fortune Tech - So many "column inches" in the online tech press is devoted to endlessly regurgitating these sorts of rumors. Cheap clicks.
- VMware pros glean vSphere roadmap from CTO in VMUG videos - "“Those of you who know our products deeply know that they don’t fit as well together as they need to,” Herrod told the VMUG attendees. “Some have multiple databases. Some don’t look the same. Some install differently. And what I can’t stand is that currently Site Recovery Manager doesn’t work with vCloud Director.”"
- Do I Build or OEM My Cloud Service? The Top 5 Considerations | BostInno
- Bits or pieces?: On the death of great companies
- More Americans Leave Passports at Home for Summer Vacation | BostInno - More domestic flying than international in summer Euro airfare this summer was really $$ when I looked
- Expensify Trips: Track your itinerary from your expense report « Expensify Blog - Expensify is apparently trying to bridge to offering a Tripit-like service
Cloud computing requires a mindset that approaches system architecture as a much more distributed, heterogenerous, and even self-organizing entity than was the historic norm in IT. VP of Product Strategy and GigaOm blogger James Urquhart shares his thoughts on the topic as he discusses:
- Complex adaptive systems
- What high availability means in the cloud
- The role of standards
Listen to OGG (0:14:22)
Gordon Haff: Hi everyone. This is Gordon Haff, Cloud Evangelist with Red Hat. I'm here at the Open Cloud Conference in the Bay Area. I'm sitting here with James Urquhart, who's the VP of product strategy for enStratus. Hi, James.
James Urquhart: How are you, Gordon? Good to see you.
Gordon: We've known each other for a while. You've had blogs in a number of places that I've also written on and currently on GigaOm, right?
James: Yeah. I'm a regular contributor to the GigaOm cloud section. I should be blogging more often than I do. You'll see me about every two to three weeks on GigaOm.
Gordon: I have the same problem, James, getting stuff written on a regular basis.
We've had some really interesting conversations about how the cloud is changing systems architecture. In fact, you had some really interesting thoughts about how to think about architectures with the cloud.
James: For a long time I've had an interest in the subject of complex adaptive systems. There's an entire science around a world in which there are many, many different individual agents that each have their own behavioral decision making process, whether that's DNA or whether it’s the economic space with buyers and sellers. And then, they interact in very arbitrary ways over a very large scale creating a system that ends up having its own emergent behavior as a system that comes with no central control of that behavior. That's just the way things work out as these agents work out.
If you look at cloud computing, what we're really beginning to do in a very large way is to step out of the silo world into much more of a heavily integrated world where the applications, the infrastructure, the services being delivered are all agents that are being very often decided by different people. A great example of that is I might have multiple agents as an enterprise running on Heroku, which in turn is running on Amazon Web Services.
And so, the behaviors of the systems are decided very independently. The subcomponents of the system are decided very independently. What you're beginning to see is that complex adaptive systems behavior slowly but surely starting to show up in IT in general, in computing in general, on the Internet in general. In part because cloud computing is an enabler of that.
What that means is, if you embrace and understand the complex systems piece of the puzzle, what you're really going to begin to see is a way to understand and to embrace the complexity of the system and to understand how to do your little pieces to make sure that your agents that you care the most about thrive and survive in that system.
I think that's really, to me, the critical shift in thinking. From trying to figure out how to build something that just works and will never break to building something that adapts to the environment and constantly is able to thrive within a changing environment.
Gordon: I think one way that's sort of an interesting way to think about that at a conference a couple weeks ago, someone got up, up and asked "Is there a way to get five nines reliability in the cloud?" And of course, you’re coming from among other things working in a large systems in the past...The traditional thinking there was that you had some sort of failover clustering capability among large Unix systems or among large mainframes whereas from a transactional perspective, stock transactions, whatnot, you got however many minutes of downtime a year equated to five nines.
And really, though, that's not the right question to ask in the cloud, is it?
James: No. In fact, there's a really, really interesting part of complex adaptive system science that's really just starting to come out now and be explored by academia in a large way. Now, there's actually a tradeoff between stability and resiliency. If you attempt to say "I want five nines by knowing exactly what my stack is and exactly how that stack works and that nothing is going to fail in that stack," or "If something fails, I know exactly how something else will come in and replace it. But I'm going to make sure that this thing is as stable as possible." The problem you have is there's a number of things that can come in from the environment that shift the ground underneath your designs so much that there's no way that your design can in fact adapt to that change and it will fail as a whole.
A resilient architecture is one much more where you say, "Look. The individual components each have to be able to not only survive the environment as it stands, but the individual components have to be designed in a way that as a horizontally scalable system, as a group of agents working together, that as changes happen in the environment that the system somehow keeps going. The subsystem somehow finds a way to at least meet a minimum set of capability that keeps the system going."
If you look at the way Amazon's designed, if you look at the way that Netflix is designed, this is exactly what they do. That front page of Amazon's not an application that’s made up of a whole bunch of pieces that are all designed to be stable. It's made up of a whole bunch of things where there's a whole bunch of failover and a whole bunch of different ways that data can be gathered.
So go to a cache. If the cache is gone, you go to the core data source. If that data source is gone, there's this other data source that will give you kind of a remotely good picture that you can adapt to. If that data source is gone, then you can say, "Well, I'm just not going to display that element of the page."
But the home page, that Amazon purchase page, is always there. When was the last time you went to Amazon and it was gone completely? That kind of resiliency...Right? Things fail all the time in Amazon, but that resiliency of the overall system gets you the appearance of five nines plus.
I think that that's the beginning shift of the mentality to say, "Rather than focusing on the component and making the component as stable as possible, focus on the relationships between components and how components work together and how can you build as much resiliency into the different relationships and the way things work together so that the system as a whole is in fact quite available, and quite resilient.”
Gordon: This sort of idea that we're just going to have these utterly standardized APIs that work together in lockstep and communicate with that way. That's really not the future. What we're really talking about architecting for this very heterogeneous environment where you need to sometimes translate from one thing to another, connect to things in a loosely coupled way.
James: I don't think standard APIs are the problem. I think the way to look at it though is, you're trying to find the patterns and you're trying to make sure that you can build to the patterns that work and to adapt and evolve those patterns over time. But I think there's a place for standard APIs. I think there's a place...Frankly, provisioning a server as an action, there's very little highly differentiated ways that you can provision a server. I think it's very fair to say that we're getting to a point for a Linux system working on an X86 environment, there can be a very, very standard way of doing that basic task.
But that's not the application. That's not the thing that solves a business problem up above.
I believe that there are standards in places that you can come to, but the idea that there's one stack that solves the problem is...And I don't think I've heard anybody really argue that it's all going to be this one big stack and everybody's going to move to this or they're non standard.
I think what you have to realize is that there are different components in the different stacks, that they give you different value. I think it's fine to talk about open standards for interfaces and then for formats, but I think when you go farther than that, when you try to say the stack is locked down, you have to do it this way with these sets of components. I think that that's the point that you break the model. I think that's when the market says "That's a broken model," and they do something different.
A great example, really quickly, about that is just when ITIL took off and companies started identifying ITIL and really, really being hip on it. DevOps shows up. Because ITIL was broken for some aspects of what the business wanted to do, DevOps is much more flexible in terms of the agility when you need agility. So, in fact, it is disruptive to what we thought was the commodity way of doing IT. It's always going to be that way.
Gordon: I think, really, if you look at the history of IT, you've got big monolithic approaches really have not done as well as more nimble, more modular approaches.
James: And that's exactly true. I think...There's a gentleman by the name of Simon Wardley who has great writing on this, where he talks about there are spectrums of business activities and there are times when you need to be highly, highly agile and there are times when you need to be locked down and to very closely control change and control adjustments. But what happens is you go through that cycle and get to the end of the cycle, to where things are little bit more like that. That enables a whole new set of innovation on top of that which, in the end, may trickle down and say, "Yep, we need to rethink the way that we're doing X."
It's being prepared and being able to understand that that constant churn is a fact of life. It's something you need to develop your processes with that concept in mind. And that the patterns and the toolsets and the infrastructure that we build out for the cloud is going to have to take that complex systems approach in mind, as well, and really begin to embrace this concept of focusing on the relationships between things more than focusing on the components themselves.
Gordon: And we do certainly seem to be shifting to an API driven world in a lot of ways. I guess a lot of people tend to think in terms of the Amazon APIs, and the Flickr APIs, and in many cases the more consumer oriented services. But more and more businesses, credit card processors, banks, what have you are starting to expose APIs, if not for general public use then the use of their partners.
James: Yeah, and I think what's really, really fascinating about that is why those APIs are being exposed. If it's of a surface that you give it some data and instruction and it returns something back to you that's of value. You're basically providing that service through an API instead of through human methods or whatever it might have been before. In other areas where you're saying, "Well, the API is really about how you consume another resource downstream." The problem that you have is the API isn't enough. And so, I think what you're going to see is giant success in terms of exposing business capability through APIs. I know of companies out there like a giant construction company that has this phenomenal API layer over all of their backend systems. They're writing mobile apps that will blow your mind at a rate that, in turn, would blow your mind as well because they just call to a standard REST kind of syntax and structure.
That stuff really works really, really well. But when it comes to saying, "Hey, I want to provision a service so here's my API and that's going to work all the time." That's not true today and it may never be fully true. It may be more true than it is today, but I think you have to understand that there's a lot more that has to be standardized than just APIs to get to that point. That's going to take more work and that's going to take more effort.
But projects like OpenStack, like CloudStack, like Eucalyptus, they have a great opportunity to, in fact, create mini ecosystems or even large ecosystems out there where that's more true than it would be for the cloud as a whole.
It excites me that the API story is taking off because for developers it's powerful. But I also...It's temporary when I say that. I'm sort of saying it's not enough to say APIs. We need common formats and additional common interfaces. That work still needs to be done.
Gordon: Yeah, you really need hybrid cloud management to take care of some of that really at a level that's below what developers really ought to be worrying about.
James: Yeah, and that's why...This is the reason why enStratus is focused on the application level of operations. We're about application operations in the cloud. How do you consume cloud services to deliver application capabilities? We're largely focused on infrastructures and service today, but that's obviously an evolving picture. I think when you look at the problem of saying, "I'm going to...My tools for running my application are in a cloud service," that's very limiting in terms of how you do things.
Having tools that say, "Let's step back and abstract how we want to operate our applications in general," and then apply that to the different clouds we might want to consume in the way that we operate. Make sure we're applying consistent governance. Make sure we're applying consistent automation to the approach. Make sure we're applying that in a very independent way so not only are you independent from the clouds that you can choose but also in terms of the tools that you apply to operate.
So with DevOps tools, you want to use Chef/Puppet. What management tools do you want to use? Monitoring tools, those kinds of things, do you want to use in the environment? That's really what the enterprise needs, is that ability to begin to abstract application operations and begin to incorporate the things that they need to in that way.
Looking at application operations as separate from infrastructure and services operations. The delivery of a cloud service to the end customer. So building your private cloud is not an application operation problem. It's a service operations problem. Consuming that private cloud is an application operations problem.
Gordon: Great. Thanks very much, James. Anything else to add?
James: No. Congratulations to Red Hat on their wonderful launch and with their OpenShift stuff. I'm very excited to see what's going on in that PaaS side of the market. I think that's a really exciting space to watch. And I'm very happy to have been here with you today and have a chance to talk to you.
Gordon: Great. Thanks, James.
Friday, May 11, 2012
- Tabletop Studios | Modahaus Table Top Studio Lighting Kits
- The Man Who Took on Amazon and Saved a Bookstore - Forbes - RT @mathewi: how the owner of the Harvard bookstore figured out a way to compete with Amazon: -- will have to check out
- HP Is Still Full of Leaks - Businessweek - "Time heals all wounds. Except at Hewlett-Packard (HPQ), where old wounds fester with remarkable persistence and where there seems to be a deep bench of executives unfamiliar with the concept of a bygone."
Thursday, May 10, 2012
Lots of growth forecast. I'd argue that the relatively slow pickup to date has been a function of the fact that many first-generation PaaS platforms have been specific to a single provider. More open approaches, such as that taken by Red Hat's OpenShift, are provider-independent--which greatly reduces the possibility of vendor lock-in.
- Why "Freemium" Fails for Startups: 3 Business Lessons from the Band New Order - Forbes - "Freemium is fantastic when it works. Problem is, it doesn’t work all that often."
- How Hewlett-Packard lost its way - Fortune Tech - "Your comments are being live-blogged," one employee told her defiantly. Whitman challenged the man. "You all have taken leaking to a new art form," she said. "It's a sign of an unhappy company. You wish HP ill." The tapping suddenly stopped, and as the room fell silent, the mobile devices were lowered.
- The trouble with PandoDaily – Milo Yiannopoulos – The Kernel - "The first time I saw PandoDaily, I was convinced it was unfinished, or a spoof. Now it’s been running for a while, I’m aghast. Were one to crowdsource the ten most anachronistic WordPress theme features from the last five years and jam them together with horse glue, you would struggle to come up with something uglier or more difficult to navigate." << Amusing in a high school fighting cliques sort of way.
- 10 Salts to Know - an article from Food52
- Sell Oracle And Buy This Software Stock - Seeking Alpha - RT @screnshaw: "Red Hat is the leader in open source and cloud computing" @seekingalpha
- Moore's Law Over, Supercomputing "In Triage," Says Expert - Technology Review - "If Sterling is right, and he is one of the deans of high performance computing, it seems likely that we'll never reach the next milestone in supercomputing in silicon. Physicist Michio Kaku says Moore's Law will collapse in about ten years. Sterling agrees, and says it comes down to the basic physical restrictions of working with atoms."
- The 2nd Tenet of PaaS: The P in PaaS Stands for Platform, Not Product | tentenet.net - RT @bryanwche: Why #OpenShift is the ultimate cloud application platform for enterprise developers #PaaS #redhat
- Red Hat OpenShift's Technology Foundations - YouTube - Here's video of @matthicksj explaining how #redhat infrastructure products used to support @openshift PaaS
- Red Hat | Implementing an open cloud architecture - Long day of webinars about implementing an open cloud. Stop by if you get a chance!
- Red Hat Unveils Enterprise Platform-as-a-Service (PaaS) Roadmap and Strategy - MarketWatch - RT @joefern1: Red Hat Unveils Enterprise PaaS Strategy << Multiple PaaS operations models
- OpenCloudConf - Future of Clouds - Gordon Haff - YouTube - Here's a video of my cloud trends presentation from #opencloudconf
- Oracle gets a chance to rewrite software law | Business Tech - CNET News - RT @bobmcmillan: A great take on the Google-Oracle case by @stshank Well written, dude. << Yep. Nice.
- Politico endorses post-first, check-later journalism - Erik Wemple - The Washington Post
- Searching the Internet B.G. (Before Google) - Input Output
- Cloud is a corporate strategy, not a tactical solution — Cloud Computing News - "OK, maybe there are more bells and whistles, but treating cloud like a technology solution purchase is the wrong approach. Take a holistic approach to how IT can and should participate in the business of doing whatever your company does, then build the operational model to support that. Seek alignment in your organization and in your technology choices so you’re prepared for a Cloud Operating model and Fluid IT. Welcome to the modern IT world."
- Why Publishers Don't Like Apps - Technology Review - "And Technology Review? We sold 353 subscriptions through the iPad. We never discovered how to avoid the necessity of designing both landscape and portrait versions of the magazine for the app. We wasted $124,000 on outsourced software development. We fought amongst ourselves, and people left the company. There was untold expense of spirit. I hated every moment of our experiment with apps, because it tried to impose something closed, old, and printlike on something open, new, and digital."
- An IT Forecast: Where Cloud, Mobile and Data Are Taking Us | SYS-CON MEDIA - "A thorough piece on CNET by Gordon Haff looks at the interconnectivity of cloud computing, mobility and Big Data, and sees these three forces as instrumental in shaping the future of IT. "Through the lens of next-generation IT, think of cloud computing as being about trends in computer architectures, how applications are loaded onto those systems and made to do useful work, how servers communicate with each other and with the outside world, and how administrators manage and provide access," Haff writes."
Monday, May 07, 2012
- Can Amazon become the biggest platform peddler in the world? • The Register
- The frequent fliers who flew too much - latimes.com
- (403) http://www.yelp.com/biz/WAo42c41_0Y0tifXbwuo8w?pt=check_in&ref=twitter&v=4b - I checked in at Fuki Sushi (4119 El Camino Real) on #Yelp
- On APIs and Copyright – tecosystems - RT @sogrady: new post | "On APIs and Copyright": << Nice piece. Will be quoting from it shortly :-)
- 2012 Best Food Blog Awards: The Winners! - Saveur.com
- Does the Noncommercial Creative Commons license make sense? | The Pervasive Data Center - CNET News - .@jasonbrooks NC is longtime beef of mine w CC as well Though believe @sogrady disagrees.
- Computational Journalism Server – The Way Forward » Borasky Research Journal - Nice vote for OpenShift
- Recapping the OpenShift Origin Launch and What Happened to Express and Flex? | OpenShift by Red Hat - Good overview of available resources.
- Where Do All Those BuzzFeed Cute Animal Pictures Come From? - Alexis Madrigal - Technology - The Atlantic - ""I would love if every image contained some secret metadata and a way to license that image," Peretti told me. "But the practical reality is that it is pretty challenging, particularly in the web culture of animals and the images that spread on Pinterest and Tumblr." " --ME: Even when you try to do the right thing, it's usually not straightforward to provide attribution.
- Rough Type: Nicholas Carr's Blog: Pay up, Yochai Benkler - I mostly agree that the center of grab in the Web (etc.) has shifted more commercial.
- 563 - Pop by Lat and Pop by Long | Strange Maps | Big Think
- Triggertrap Mobile | Triggertrap
- Revenue could be fatal: 3 reasons your startup should consider waiting | FoundersVoice - Pretty much agree with the people puking all over this.
- Facebook Urges Members to Add Organ Donor Status - NYTimes.com - RT @R_Thaler: Yay! “@timoreilly: Wow. Facebook adds "organ donor status" to profiles. This is Sunstein and Thaler's ...
- The 10th Tenet of Cloud: The Linux of Cloud is…Linux | tentenet.net - RT @bryanwche: The 10th Tenet of Cloud: The Linux of Cloud is...Linux
Thursday, May 03, 2012
[As I touch on intellectual property issues herein, I'd like to remind everyone that this is my personal blog and should not be in any way taken as official Red Hat positions or statements, nor presented as such.]
Just because something is widely used doesn't make it a standard--de facto, de jure, or otherwise--in the sense that anyone can use and build implementations of that standard without restriction. Indeed, as we shall see, even standards that are "blessed" by powers-that-be are not always fully open in the ways that I have outlined previously.
Standardization has been around for a long time. The IEEE tells us that:
Based on relics found, standardization can be traced back to the ancient civilizations of Babylon and early Egypt. The earliest standards were the physical standards for weights and measures. As trade and commerce developed, written documents evolved that set mutually agreed upon standards for products and services, such as agriculture, ships, buildings and weapons. Initially, these standards were part of a single contract between supplier and purchaser. Later, the same standards came to be used across a range of transactions forming the basis for modern standardization.
A lot of this early standardization pretty much came down to custom. The convoluted history of why we drive on one side of the road in a given country is instructive. (Though each country's conventions are now enshrined in The Geneva Convention on Road Traffic.)
The history of the shipping container, as detailed in Marc Levinson's The Box: How the Shipping Container Made the World Smaller and the World Economy Bigger, offers another, fairly typical, historical example. Incompatible container sizes and corner fittings required different equipment to load and unload and otherwise inhibited the development of a complete logistics system. The standardization that happened around 1970 made possible the global shipping industry as we know it today--and all that implies. The evolution of standardized railroad gauges is similarly convoluted. The development of many early-on computer formats and protocols was similarly darwinian.
It's tempting to take this past as prologue and conclude that similar processes will continue to play out as we move to new styles of computing in which different forms of interoperability assume greater importance. For example, published application programming interfaces (API) are at the heart of how modular software communicates in a Web services-centric world. One set of APIs wins and evolves. Another set of APIs becomes a favorite of some particular language community. Still another doesn't gain much traction and eventually withers and dies. It sounds like a familiar pattern.
But there's an important different. In today's software world, it's impossible to ignore intellectual property (IP) matters whether copyright, patent, trademark, or something else. An API isn't a rail gauge--though perhaps someone today would try to patent that too.
As a result, tempting as it might be to adopt some API or other software construct because it's putatively a "de facto" standard, which is mostly a fancy way of saying that it's popular, that may not be such a good idea.
it’s worth noting that many large entities are already behaving as if APIs are in fact copyrightable. The most obvious indication of this is Amazon. Most large vendors we have spoken with consider Amazon’s APIs a non-starter, given the legal uncertainties regarding the intellectual property involved. Vendors may in certain cases be willing to outsource that risk to a smaller third party – particularly one that’s explicitly licensed like a Eucalyptus [coverage]. But in general the low risk strategy for them has been to assume that Amazon would or could leverage their intellectual property rights – copyright or otherwise – around the APIs in question, and to avoid them as a result. Amazon, while having declined to assert itself directly on this basis, has also done nothing to discourage the perception that it has strict control of usage of its APIs. In doing so, it has effectively turned licensed access to the APIs into a negotiable asset, presumably an outcome that advocates of copyrightable APIs would like to see made common.
In fact, lack of openness can even extend to standards that have gained some degree of governmental or quasi-governmental approval--which is, after all, a political process. Last decade's fierce battle over Microsoft's submittal of its OOXML document format as a standard to ECMA and ISO is perhaps the most visible example. The details of this particular fight are complicated, but, in Kurt Cagle's words, "The central crux of the [then-]current debate is, and should be, whether Microsoft’s OOXML does in fact represent a standard that is conceivably implementable by anyone outside of Microsoft."
Issues of the conditions that should be satisfied in order for a vendor's preferred approach/format/etc. to become a "blessed" standard continue to reverberate. The latest round is about RAND (Reasonable-and-Non-Discriminatory) licensing and whether that can take the place of truly open implementations. It's essentially an attempt to slip proprietary approaches requiring a patent license into situations, such as government procurements, that require open standards.
The presence of RAND terms at best chills developer enthusiasm and at worst inhibits engagement, as for example it did in the case of Sender ID at IETF. As Välimäki and Oksanen say, RAND policy allows patent holders to decide whether they want to discourage the use of open source. Leaving that capability in the hands of some (usually well-resourced) suppliers seems unwise.
At one level, the takeaway here might be "it's complicated." And it is. But another takeaway is pretty simple. You can dress up proprietary standards in various ways and with various terms. And such standards have a place in the IT ecosystem. But they're not open, whatever you call them.