Re the environmental impact: A large contingent of internet networked servers are webservers, transacting with the HTTP protocol (be it spiders or producers or whatever). If it takes more computing resources to provide HTTP/2.0, then it would in fact require more servers, and thus increase the energy consumption.
But given how large datacenter consumers are considering how to build greener/smarter operations to reduce their impact (and costs) then clearly it's something to be mindful of.
The point is that it's not sufficient to run the current 20k tests against head daily; there are so many unplanned variations and 'emergent' design that there's a full time job just in keeping up with the changes to MRI ruby.
And even if there wasn't, @brixen has repeatedly pointed out how the MRI authors have chosen to ignore the RubySpec project entirely. That's really sad.
You're assuming they a: notice and pay attention to the road, and b: they're familiar with how to drive, so know that is a trickier maneuver, and c: that they know how well you drive, so can contextualize a pause based on your ability.
Not if you want approval from the payment card industry you can't.
They'll want proof that no other app can access the screen, that screen presses can't be recorded and lots of other stuff.
I'm going through this with a hardware pinpad at the moment, the list of requirements is very long and quite stringent.
--edit-- I'm not saying this is impossible, but I find it very unlikely. All the other EMV devices I know of that are designed for use with iOS and Android devices have built-in hardware pinpads because it's just easier... the PCI is very precious about PIN data. For good reason.
Agreed, they own some of the most well known typefaces in the world. Sadly, their pricing is absurd.
For example, I run a forum with a million daily page views. If I wanted to use Gotham, I need to pay $150 for the font, and then subscribe to their cloud service and pay $450 per month for that amount of page views.
I might be willing to pay a one-time $100 fee to use one of their fonts, or a $100 per year subscription to use any of their fonts. However, $5,500 a year for my site? That's almost as much as my servers. It's a laugh, I'll stick with the well respected free web fonts.
might be kind of interesting to do an IamA on reddit. I'd like to hear more about what it's like to work in HPCs -- even simply considering how to build that kind of processing and how to think in terms of jobs that take real time to complete.
> 1. a bunch of netsec/security geeks have looked at it (calling @tptacek, @cpercival)
Agreed - but it seems that this is an authoritative-only name server, which means it shouldn't be susceptible to cache poisoning, which is where the most awful DNS server security vulnerabilities have been.
It is nice to see that we are moving from huge and clumsy DNS servers (BIND) to smaller servers with a specific focus: unbound as resolver, NSD/Yadifa for authoritative servers.
Now that we have them, couldn't some core code be shared between all these projects and receive more scrutiny than it receives now? For example the code that parses incoming packets or generates replies could easily be shared (in theory).
I'm no fan of BIND though operationally having separate servers can be problematic: if you want to run both a recursive and an authoritative DNS server on the same host (pretty common for DNS servers on internal networks) you need two IP addresses. PowerDNS works around this by having their authoritative server forward recursive queries to a host/port that you specify.
Agreed that code sharing would be nice, and more important than ever since the rise of small servers with specific focus.
I think djb is a brilliant programmer, and he has written some absolutely fantastic code, but I also think that he is becoming less and less relevant as time goes on. Various DNS servers have massively improved, security is being taken more seriously (due in part to him, no doubt) but his software doesn't seem to be moving forward...
dnscache for example doesn't (at least in my testing) connect over IPv6 to a remote name server to resolve a domain, nor does it do DNSSEC validation (and I understand DJB doesn't like DNSSEC, unfortunately it is here and I think that more and more having a validating resolver is a good idea).
Thanks; I was especially thrown because I tried "home", which was the first example in the example image (!) but it didn't work and I thought I'd misunderstood what was going on. I guess I should have blindly tried others from that list, hoping for a different result. :P