In an Uber all graphite and glitter:
Sure, maybe O’Reilly’s post bugged me because he’s playing the familiar game of using recent Apple product news as a strawman to compare to an utterly different kind of technology, while throwing in coded phrases like “Apple hype machine.” (Replying to a comment on his own article, O’Reilly declares, “What I wrote wasn’t really about Apple Pay.” Of course it wasn’t.)
But I think what really rankles is that Tim O’Reilly is applying his vision to a Silicon Valley utopia where people take Ubers to their Cover-booked restaurants, always operating on their own recognizance and never, ever waiting for the check. There’ll be spandex jackets, one for everyone.
Apparently these people never go to the supermarket.
Microsoft, IBM, & Docker jump on Google’s Kubernetes project for managing app containers anywhere:
Now several companies that deal in managing infrastructure at scale have stepped up as contributors to the Kubernetes project, namely IBM, Microsoft, Red Hat, Docker, CoreOS, Mesosphere, and SaltStack.
Take the development as more proof that technology can now span a very wide variety of computing environments. Docker and its container technology have grown popular based on the notion that containers could be the basic unit of computing, and Kubernetes could be the tool to orchestrate all containers at the same time.
The new backing of Kubernetes could also be a turn away from more segmented and often proprietary hypervisor technology that sits on top of server operating systems and creates many virtual slices for running applications within each physical server. As developers and companies begin to try it, companies that sell hypervisor software, including VMware, could start to wonder how they should participate in the containerization movement.
Mesosphere · Mesosphere to Bring Google’s Kubernetes to Mesos:
The big trend driving containerization is a fundamental shift in the way apps are built. Today’s apps need to ingest big data. They need to connect to millions of devices. They need to scale out, elastically, in real time to handle surges in usage. They need to be highly automated, with no human operators. And they need to be fault tolerant and self-healing, so that zero downtime is the new normal. In this world, the old way of doing things simply—building ever bigger monolithic apps that run on ever bigger machines—simply does not work.
Building apps today means building them like Google does—or like Twitter, Facebook, and Airbnb for that matter. As the early pioneers of the “always on, always connected” world, these companies had to invent new ways to build apps. An “app” at one of these companies is not a single “binary” running on a giant server; it’s comprised of dozens (or hundreds or even thousands) of composable services running on fleets of servers, distributed across entire datacenters and clouds.
Building an app out of many composable services, distributed across just as many machines in a cloud or datacenter—stitched together using technologies like Mesos—is how apps are being built today. If you are not yet building apps like this, you will be. This is the new way to build apps. This is the new way to deploy apps. And this is what is truly driving the container revolution.
Jonathan Ive on Apple’s Design Process and Product Philosophy – NYTimes.com:
The benefit of hindsight is we only really talk about those things that did work out. You have this sense that you’re working on something incredibly hard. When working on projects, you have this determination. You just keep going. If doing anything new, you’re very used to having insurmountable obstacles. At some point you have to make a call — at some point you have to say, “We’ve stretched this and we’ve come up against laws of physics, which we cannot change.”
This URL shortener situation is officially out of control:
That’s a lot of back and forth just to get me a a web page. And getting me a web page is kind of the most important thing the web does. Redirects are being abused and I don’t see any work happening in HTTP 2.0 to change it.
The Internet With A Human Face:
Public and private surveillance are in a curious symbiosis with each other.
A few weeks ago, the sociologist Janet Vertesi gave a talk about her efforts to keep Facebook from learning she was pregnant. Pregnant women have to buy all kinds of things for the baby, so they are ten times more valuable to Facebook’s advertisers.
At one point, Vertesi’s husband bought a number of Amazon gift cards with cash, and the large purchase triggered a police warning. This fits a pattern where privacy-seeking behavior has become grounds for suspicion. Try to avoid the corporate tracking system, and you catch the attention of the police instead.
As a wise man once said, if you have something that you don’t want anyone to know, maybe you shouldn’t be doing it in the first place.
But there are also dangerous scenarios that don’t involve government at all, and that we don’t talk enough about.
I’ll use Facebook as my example. To make the argument stronger, let’s assume that everyone currently at Facebook is committed to user privacy and doing their utmost to protect the data they’ve collected.
What happens if Facebook goes out of business, like so many of the social networks that came before it? Or if Facebook gets acquired by a credit agency? How about if it gets acquired by Rupert Murdoch, or taken private by a hedge fund?
What happens to all that data?