Apple Watch: Function Over Form Otherwise It's Just a Fad
So yet another technology company wants to put some jewelry on my wrist. Good luck. You know it’s not that I don’t want the Apple Watch to succeed. It’s just that I’ve been down this path already.
This past weekend I was reading a piece in the San Francisco Chronicle by Thomas Lee, “Why we need Apple to fail.” While I’m not really buying Mr. Lee’s line of thinking - my ego is not going to be bruised one way or the other should Apple fail or succeed with this product - it did start me thinking.
My father was an employee at Hewlett Packard back in the good old days. One of the latest and greatest products of those days was the desktop calculator. It was a time when each successive year found significantly more computational power in much smaller footprints. Eventually someone said, “Hey, we could make a calculator as small as a watch now.” So they did.
I don’t know how many watches HP produced over the lifetime of the product Continue reading
When you buy a server, you don’t worry whether or not Windows will run on the server. You know it will. That’s because the server industry has a comprehensive solution to a hard problem: rapid, standard integration between the OS and underlying open hardware. They’ve made it ubiquitous and totally transparent to you.
This is not the case for embedded systems, where you have to check whether an OS works on a particular hardware platform, and oftentimes you find out that it’s not supported yet. Bare metal switches are a good example of this.
It’s time to change that. We need the same transparent model on switches that we have on servers.
To make open networking ubiquitous — and to give customers choice among a wide variety of designs, port configurations and manufacturers — the integration between the networking OS and bare metal networking hardware must be standardized, fast, and easy to validate. We need open hardware.
Today, a bare-metal networking hardware vendor supplies their hardware spec to the NOS (network OS) provider. The NOS team reads the spec, interprets it and writes drivers/scripts to manage the device components (sensors, LEDs, fans and so forth). Then Continue reading
It’s 9am and CloudFlare has already mitigated three billion malicious requests for our customers today. Six out of every one hundred requests we see is malicious, and increasingly, more of that is targeting DNS nameservers.
DNS is the phone book of the Internet and fundamental to the usability of the web, but is also a serious weak link in Internet security. One of the ways CloudFlare is trying to make DNS more secure is by implementing DNSSEC, cryptographic authentication for DNS responses. Another way is Virtual DNS, the authoritative DNS proxy service we are introducing today.
Virtual DNS provides CloudFlare’s DDoS mitigation and global distribution to DNS nameservers. DNS operators need performant, resilient infrastructure, and we are offering ours, the fastest of any providers, to any organization’s DNS servers.
Many organizations have legacy DNS infrastructure that is difficult to change. The hosting industry is a key example of this. A host may have given thousands of clients a set of nameservers but now realize that they don't have the performance or defensibility that their clients need.
Virtual DNS means that the host can get the benefits of a global, modern DNS infrastructure without having to contact every customer Continue reading
One of my readers left this comment to the Four Paths to SDN blog post:
You didn't mention Cumulus. SDN protocols become much less important when you have an open Linux switch platform. You can compile and install your own management daemon and implement whatever protocol best suits the task (and blend local and remote control).
Here’s my usual response to this line of thinking:
Read more ...When I started studying in earnest for my CCIE, I started a log of how I was spending my time studying, which books and papers I’d read, videos I’d watched, and so on. I thought it would be a neat exercise to look back afterwards at what it took to achieve this goal. I’m also somewhat self-deprecating and tend to minimize my accomplishments, so having this data is a way for me to remember that this wasn’t a small accomplishment at all.
1,041,248 bytes of digital notes taken
13,916 km traveled (8,711 mi)
1,432 total study hours
652 hours in the lab
321 hours of just reading
223 videos watched
161 hours spent watching those videos
128 PDF documents read
23 books read
5 figures worth of expenses and costs
1 completely trashed USB mouse
Beyond these numbers there’s the intangibles that went into this goal too. No vacations. Giving up free time on evenings and weekends. Not seeing friends as much. Not spending as much time with family. Maintaining focus constantly on the end goal. Constantly staying up late and getting up early.
Looking back at all of this, I realize that becoming CCIE certified isn’t just about Continue reading