There's no such thing as 'water proof' -- everything is simply water resistant up to a certain level, see http://en.wikipedia.org/wiki/I...
What we really need is IPv8, based on IPv4 with a larger address pool and no other irrational changes to the protocol. IPv6 simply adds too much complexity to the system.
The vast majority of IPv6 addresses being assigned aren't routable anyway -- do you really think those random local addresses you gave on your LAN at home can be globally routed from anywhere? Sure, if you get an assignment from your ISP, but do you really want your home alarm system, clock radio and fridge globally routable in the first place?
Why do you believe IPv6 routing is faster than IPv4?
Don't confuse people with the facts -- money spent on their own pet subject is legit, and money spent against it is wrong of course.
You might want to consider understanding the language you use before making a point in it
Weak encryption is *worse* than no encryption because it gives people a false sense of security they shouldn't have. It makes them feel safe to say or do things they wouldn't do if they realized how bad the encryption they're using really is.
I was thinking the same thing -- I've even used kernel code to explain certain C techniques to new programmers.
I have the same comment about nearly every networked camera system ever.
That's a flood-length post? How much do you suck at typing exactly?
Those 174 words took me no longer than 2 minutes to write; maybe you should do something more productive than troll.
Actually they have 16 GiB of RAM; its a number very close to a billion but based on powers of 2 instead of 10.
Words have meanings, and so do prefixes; the metric numbering system was usurped (stupidly) to mean something it didn't mean.
One wonders if disabling that last 500MB of RAM would in fact improve performance.
No, its an ambiguous word and I've complained about it in life on numerous occasions.
Except that MB is a metric term that was co-opted in computing for no good reason (base 2 calculation rounding), and correcting it makes sense.
1 million bits is a megabit. 1 million bytes is a megabyte.
I appreciate your insights, but your assumption that this has something to do with being 'good for Google' is hogwash -- they already had SPDY and HTTP/2 doesn't implement everything SPDY has. I see Google being a good citizen here and joining the new standard instead of continuing to push their own protocol they obviously preferred.