177 karma · joined September 25, 2012
But the impression I get from my (possibly biased) sample is that most non-trained people intuitively see proof by contradiction (or any form of nonconstructive proof, really) as a way of "cheating", because it asserts something does or does not exist without actually producing a (counter)example. YMMV, of course.
First off, to dispel any misunderstanding, I was talking about the process of becoming a mathematician, which you necessarily go through before you can call yourself one.
But even for full-fledged mathematicians, what I'm saying is true to an extent. For instance, although ZFC set theory is usually accepted as the basis for all mathematics, most mathematicians (precisely: those who do not study formal logics or other areas of metamathematics) do not state their results in terms of set theory, but instead write informal proofs that appeal to other established results in their field of study.
That is absolutely not the same as saying that their thinking is fuzzy or sloppy. The fact that I personally do not state (or, even, understand) all the details behind an established theorem X has no bearing on the validity of my proof for a theorem Y that hinges on X being true.
> The Incompleteness Theorems show the degree to which mathematicians expect to know why something is true, and if they cannot, why not.
This is a separate matter. Whether in theory it is possible for you to ascertain whether X is true or not, and whether you fully understand (down to first principles) why X is true before you use it as a stepping stone for other results are different issues.
In order to be able to understand and appreciate mathematical proofs, you have to develop the ability to accept the truthness of a result - and to realize the consequences of it being true - even though you do not yet understand why it is true. You have to learn to accept the ensuing confusion as a natural state of mind (read [0] if this idea intrigues you).
[0] http://j2kun.svbtle.com/mathematicians-are-chronically-lost-...
And thanks also for your thoroughly enjoyable talk.
This step of the proof invokes the Fundamental Theorem of Arithmetic [0]: the statement that every natural number can be expressed as a unique product of primes (uniqueness isn't the important bit here, just the fact that such a factorization exists).
So you need to accept the Fundamental Theorem of Arithmetic as true before you can fully understand this proof.
[0] http://en.wikipedia.org/wiki/Fundamental_theorem_of_arithmet...
var x []string = strs ?
If you make a copy of the slice's underlying array and point x to the copy, then you are hiding a potentially expensive allocation behind an apparently innocuous initialization (something that Go tries very hard not to do).If, instead, you make x point to the same underlying array as strs, then you would have to have immutable slices, which is something that currently does not exist in Go.
I'm not saying neither of the two options is acceptable, but they surely raise issues that go against the grain of the language.
Oh, I see your point now. You mean the IPv6 addresses assigned to the nodes that the router forwards the packets through (i.e., the egress nodes), not the destination addresses for those packets.
> Unless the gateway is always at the front of the address block, which I'm sure "they never taught us" in small network design school, at least I believe I've seen routes where the gateway was inside the netblock range or at the end rather than beginning, but again... big networks maybe.
Sure, the gateway address almost never belongs to the address block you are forwarding to. You could be forwarding to a very distant network which isn't directly connected to, nor belongs to the same address block, as your gateway.
I can't tell for sure how routers implement this, but it's safe to say that the total number of egress nodes for a router is much, much smaller than the total number of routes (prefixes). So the obvious optimization is to store the egress node addresses in a lookup table, and only store an index into that table for each route. That way, the fact that you are now forwarding through IPv6- instead of IPv4-addressed gateways does not increase the routing table size (though it does increase the size of the much smaller lookup table).
> What I was trying to say was that when you have the freedom to write bigger ranges by an exponent factor of four like you have if you're the governing bodies of the internet with IPv6 vs IPv4, the expressive part of your network number can be made shorter, at least until your new network begins to approach the size of your old network.
I think you probably meant "at least until the used fraction of your new address space begins to approach the used fraction of your old address space".
> You don't avoid this problem at all, even if you are not storing 128 bits of address there are probably never scenarios where two internets of the same size last longer on the same hardware because IPv6.
I'm not sure I understand the last sentence. The sense in which the IPv6 network will "last longer" in the same hardware is that, for the foreseeable future, you will be able to satisfy most new allocations by choosing an address block that is adjacent to an already existing allocation for the requesting entity. Because the two blocks can then be aggregated into a single prefix, the routing table stays the same size.
However, applying it successfully to IPv4 is severy compromised because, due to rampant address space fragmentation during the last years, increasingly longer prefixes (i.e., smaller address blocks) have had to be assigned. IPv6's much larger address space makes it unlikely that the routing table will ever become that fragmented in the foreseeable future.
That's only achievable in the long term, though - the currently assigned IPv4 prefixes will have to coexist with the IPv6 ones for a long time.
Except for the speed of light, interestingly.
Second, if ISPs are willing to keep records of IP-address-to-customer mappings, it's not much of a stretch to add TCP/UDP ports to those records as well.
What I get from this announcement is that their crawler is becoming good enough at executing dynamic pages that having to serve a separate static version may soon become unnecessary.
[0] https://developers.google.com/webmasters/ajax-crawling/docs/...
The point of net neutrality is that, while ISPs should not be held liable for what other entities in the network do, they shouldn't engage in those practices themselves. In logical terms, that's a perfectly reasonable goal.
Doesn't OpenSSL fit this definition perfectly?
They are compatible if you decouple the infrastructure owner from the service providers, as it happens in other industries.
My point today is that, if we wish to count lines of code,
we should not regard them as "lines produced" but as
"lines spent": the current conventional wisdom is so
foolish as to book that count on the wrong side of the
ledger.
[0] http://www.cs.utexas.edu/users/EWD/transcriptions/EWD10xx/EW...Disclaimer: I am not a cryptographer.