While that is certainly true, that is not what I meant. For one, it's very cheap to reach such exchanges for companies like Hetzner, because they usually operate their data centers on the same campus, to safe exactly on that backhaul cost to the exchange. By implication all the ISPs are expected to extend their network into these facilities to pick up traffic. While it's true that some ISPs operate big POPs near exchanges, it's not where their customers are. And both users and data center operators rightfully expect a professionally built network with redundancy etc. In that respect it's not necessarily unfair that they charge for the traffic. (While it is certainly unfair that they don't upgrade their connections to extort outrageous prices from other market participants and what's much worse to contain internet growth on a large scale, which is why Germany is a fairly under-developed country in terms of internet connectivity).
But also, people who work for exchange point operators are the only ones left flying business class in the telecom industry. At the same time public exchanges are a single point of failure in the network that one should(!) design around anyway. There are much cleaner solutions you can design into a network at a fraction of that cost.
This reflects only the peering capacity available for public peering and only what has been documented by each ISP for that network. Private peerings (that are direct connections to another network) are much much more cost-effective and easier to scale for a large ISP. In any case you can safely assume that DTAGs peering capacity by far exceeds one or the other Tbit, but it's also far from being sufficient capacity after all. They may also be the largest ISP in Germany by user count, while other metrics may vary ;).
The most important point the author is missing is code readability - being forced to write opinionated code is one thing. Having a chance to read somebody elses code (or your own code 3 months later) and avoiding eternal debate on code formatting is priceless. Programming is not about being able to outsmart others, in particular not in a large-scale project.
At least with Chrome you can install the Daltonize! plugin. That plugin even has a "simulation" mode to help color-visible to see how your page looks like to (some of) the colorblind out there.
The answer is technically correct, if someone uses a weak enough cipher, they would be able to decode it. What else could they say? "We spend a lot of money on eavesdropping software, but really if people are encrypting their communication, it's all pretty useless."?
The point that the folks over at Evernote are really missing is that Joe Average is using the very same credentials everywhere else, from their Gmail to the Amazon accounts. If Evernote where sensible about security of their users, they would have explained why it is indeed a bad and common practice to use the same password everywhere, as it is a certain way to get your online identity hijacked sooner rathre than later by means of a breakin like this one. It is good to know that passwords have been stored salted, but nevertheless, eventually these credentials are now compromised and if Evernote where sensible about this they would have told their users to reset their password whereever they use the same one, which is probably lousy marketing compared to "hey, we got your password stolen, but don't worry, it was encrypted".