Link: The Improbable Rise of the Daily News Podcast

Turns out there’s money in enclosure tags. Who knew? “In recent weeks, The Daily announced that it was becoming a national radio show. In doing so, it proved that scale can generate millions of dollars in new revenue, as well as (potentially) a hugely valuable spot on the national FM radio dial. That radio slot, in turn, will do wonders not only for The New York Times’ income statement, but also for its standing as a national brand. To put it another way: The Daily’s radio show won’t just make money on its own right, it will sell subscriptions to the newspaper and the website while doing so.”
Original source: The Improbable Rise of the Daily News Podcast

Pivotal Conversations: Debunking Cloud Foundry Myths

Our podcast this week:

There’s a whole slurry of myths about Cloud Foundry. With the platform updating so quickly, many of the issues behind these myths have long been addressed, and many were just false from the get-go. Coté and Richard talk about a recent post dismissing common myths. We also discuss recent news from the infrastructure software world and go over a bunch of upcoming events that Pivotal will be at.

If you use something like Overcast, be sure to check out the overly-extensive chapters and links right inside the podcast.

You should subscribe to the podcast!

Pivotal Conversations: Bringing Agility to Enterprise Data Workflows, with Sina Sojoodi

The summary:

This week we talk with about how organizations are increasingly looking to improve how they use data and workflows around data to innovate in their business. As with discuss with our guest, Sina Sojoodi, More than the usual ideas about “big data” and “machine learning,” we talk about the practical uses of data workflows like insurance claims handling and retail optimization. In many large, successful organizations the stacks to support all this processing are aging and not providing the agility businesses want. Of course, as you can guess, we have some suggestions for how to fix those problems, and also how to start thinking about data workflows differently. We also cover some recent news, mostly around Google Cloud Next and Pivotal’s recent momentum announcement.

Check out the SoundCloud page, or download the MP3 directly.

“[E]verybody likes growth in someone else’s backyard”

So, long run growth comes from one thing, and one thing only: Productivity. New and better ways of doing things. New and better products, new and better companies. It doesn’t come from 90% of the things that we talk about. So, the Federal Reserve, stimulus programs, even anti-inequality programs–over 10-20 years, it’s about productivity. Our ancestors may have, you know, you might have had a grandparent who dug coal with a pickaxe; and how did you get so much richer? Not by your union getting him higher wages and he still digs coal with a pickaxe at 20 cents an hour, not 10 cents. It’s because one guy left and he uses a bulldozer. Right? Growth comes from productivity. And productivity–everybody likes growth in someone else’s backyard. Productivity comes from new companies, doing things new ways, and making life very uncomfortable for everybody else. Uber is the great example. Uber is–that’s a great productivity enhancement. It’s putting a lot of people to work who otherwise couldn’t go to work. And the taxi companies hate it. And most of economic regulation is designed to stop growth. It’s designed to protect the old ways of doing things. So, what we need for growth-oriented policies is exactly that kind of innovation, that kind of new companies coming in an upending the status quo, that make everybody uncomfortable and run to their politician to say, ‘You’ve got to stop this.’

I don’t know the politics of economics enough to figure out if that’s a dick thing to say or not, but it sure makes grim-sense. The rest of the interview has some fun mental gymnastics and suave “turns out”’ing.

(And check out the show notes! That’s some intimidating work.)

Source: “EconTalk: John Cochrane on Economic Growth and Changing the Policy Debate”

071: Unbreakable Docker, or, elephants, er, like other elephants – Software Defined Talk

Eventually, you have to decide how your open source software is going to make money, and your partners probably won’t like it. That’s what the dust-up around Docker is this week, it seems to us. We also talk briefly about VMware’s big conference this week, and rumors of HPE selling off it’s Software group to private equity.

Check out the full show notes for links to the recommendations, conferences, and tech news items we didn’t get to cover:

Listen above, subscribe to the feed (or iTunes), or download the MP3 directly.

With Brandon Whichard, Matt Ray, and Coté.


Show notes

  • Nippers – “Nippers learn about safety at the beach. They learn about dangers such as rocks, and animals (e.g. the blue-ringed octopus), and also about surf conditions, such as rip currents, sandbars, and waves. Older Nippers also learn some basic first aid and may also learn CPR when they reach the age of 13.”

Can someone explain this “Docker forking” hoopla?

  • Coté’s write-up.
  • Docker Inc. doesn’t want to be a commoditized building block
    From a Red Hat person: “The conflict started to escalate earlier this summer, when Docker Inc used its controlling position to push Swarm, it’s own clone of Kubernetes-style container orchestration, into the core Docker project, putting the basic container runtime in a conflict with a notable part of its ecosystem. Docker Inc. then went on to essentially accuse Red Hat of forking Docker – at the Red Hat Summit no less. After that, Docker Inc’s Solomon Hykes came out strongly against the efforts to standardize the container runtime in OCI – an initiative his company co-founded.”
  • Re: that episode where we discuss Docker ecosystem challenges: “Yet on a regular basis, Red Hat patches that enable valid requirements from Red Hat customer use cases get shut down as it seems for the simple reason that they don’t fit into Docker Inc’s business strategy.”
  • A fight over where to draw the line between free/open/commodified and costs/proprietary/competitive: “And while I personally consider the orchestration layer the key to the container paradigm, the right approach here is to keep the orchestration separate from the core container runtime standardization. This avoids conflicts between different layers of the container runtime: we can agree on the common container package format, transport, and execution model without limiting choice between e.g. Kubernetes, Mesos, Swarm.”
  • Don’t bring a pistol to a bazooka fight. Enterprises love RHEL – have you ever tried to sell Ubuntu into organizations? It’s like what selling NT must have been like.

VMware hybrid cloud solutionaring

This Week in Tech Private Equity…

BONUS LINKS! Not covered in podcast.

Spaces vs. Tabs