I’ve had a Dell XPS 9550 since around February. It’s a fantastic laptop but there definitely have been teething pains with the Skylake processor and Linux, specifically related to power management.
Today I installed Linux kernel 4.8-rc5 and got a nice surprise vs 4.7.2 which I was running.
That’s quite a bit better than observed with 4.7.2 and far, far better than 4.5.X when I first got the laptop.
Usually, comments are not worth commenting on but this one, on a story about the Dell EMC merger, is worth pointing out:
“I’m just fascinated by the fact that in 2016 there are still huge companies like this making their money on ancient tech that is insanely overpriced to the alternatives.”
You’re not wrong.
The problem with your point of view (which I share – it is also my point of view) is that you’re operating on the wrong layer of abstraction.
These customers don’t need a server (or a network or a SAN) – they need business objectives to be met – again, at a very highly abstracted layer.
You’re thinking about technology and capabilities and features and configuration options … and maybe you’re even thinking about price … but that’s not the layer they are operating at. They need an airplane to be built. They need a mine to be dug. They don’t care about LUNs or stripe sizes or jumbo frames. They do care about contracts and legal commitments and “synergy”. And that’s why they rely on heuristics like business lunches and enterpris-ey sales guys and CIA guys giving keynotes at RSA.
I don’t like working at that layer of abstraction so I built a business that operates on the layer I like to work at.[1] But as much as I dislike the higher layers of abstraction, it would be childish of me to think they were “wrong”.
[1] You know who we are.
A fun view of programming today from 1973.
https://www.slideshare.net/mobile/ThomasGraf5/linuxcon-2015-linux-kernel-networking-walkthrough
I stumbled across an interesting paper called The road to SDN: an intellectual history of programmable networks (ACM DL link) this morning. It’s good to place current trends in historical context especially while keeping RFC 1925 Rule 11 in mind.
The concept of active networking is particularly intriguing to me. Could eBPF be the instruction set for a revival in this area? This may not make sense on a per-packet basis but perhaps for larger PDUs/messages?
Today I rebuilt one of our micro-services using Go 1.7.
1.7’s new SSA compiler produces faster code but I was surprised to see this much improvement. This isn’t a perfect comparison – a couple of library dependencies got updated as well and Kubernetes may have put the containers on different machines in the cluster.
Go 1.7 is out. One of the big features is the new SSA based compiler. The article below describes some of the tooling around this new feature.
Looking at your program’s structure in Go 1.7
The Go project does a great job of tooling.
Hadn’t seen this before. Looks interesting.