With C and C++, the programmer has to keep up with it; thus they are constantly aware of memory usage. (well, those that aren't complete shits do.) In Java, the programmer has no say in it, so they don't think about it -- or for younger "programmers" (who may have never learned C/C++), don't know how.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
You've obviously not work in the Real World(tm). Companies will continue using hardware as long as it works -- not broken, don't need new features/functions not possible through software update(s), or don't need additional capacity (based on space and/or power)
(Cell providers cycle through tech due to the last two.)
Unless you're AT&T (Uverse), whose entire plan for IPv6 is 6rd.
How the hell do you summarize two distant
We've allowed that bullshit in IPv4 for decades. The potential size that represents within IPv6 means it must be absolutely FORBIDDEN , from day one until the end of days.
RA, aka. ICMP router advertisement. Abandoned circa 1970 as a "bad idea". It was a colossally bad idea in the 90's, and f'ing suicidally bad in 2000+. Yeah, let's trust whoever the f*** on the cable claims to be a router and send it our traffic. Oh, to protect my network(s) from that brain damage, I have to buy new switches that support "RA Guard".
They didn't like DHCP. So "no f***ing DHCP in IPv6!" DHCPv6 is a bolt-on, staple-on, and bandaid addition to IPv6. It's a horribly incomplete shadow of DHCPv4, and still requires an RA tell you to use it.
SLAAC... originally 80bit prefix plus 48bit MAC. They ignored the fact that ethernet is not the only technology in the universe. That was later amended (breaking older stacks) to 64bits. The entire purpose for the vast over-simplification of address selection (for tiny embeded systems with limit RAM/ROM/CPU) became moot 7sec into the IPng committee's existance -- IPSec shoots all three in the head, repeatedly, with artillery. Everything supports privacy extensions these days, so the logic for random address generation and duplicate address detection is there -- and rather trivial. Yet it, and SLAAC, demands the prefix-length be 64. Just to put that silliness in perspective, that's a single LAN with every ethernet device ever created (that will ever be created) in it 65,536 times over.
This leads nicely into the blindness to history... a 64bit LAN is pure lunacy. Today and likely for several decades. But we "have an infinite amount of address space." Actually, NO, it is, in fact, quite finite: 128bits, to be exact. If we carve it up with the same pez-like abandon as the early IPv4 assignments, it will be even less "infinite". Sure, we can change the way we do things "with the next
If you're behind CGN, then by definition you aren't allowed to run "servers" -- i.e. services that require outside systems to initiate connections toward you. (www, smtp, bittorrent, etc.)
Bullshit. XP supports IPv6. (it's "experimental" and has no GUI, but it a) exists, and b) works.)
Why would the home be the "first" place for wide IPv6 adoption
Because it only takes one ISP to stop being a little shit and turn it on for millions of users to suddenly appear. Enterprise networks require the network admin(s) to actively set it up; no amount of tweaks at the ISP can convert them.
Indeed. A great many don't know that switch has been flipped (aka Uverse.) In many cases, it's not until things are suddenly "broken" that anyone notices. (youtube suddenly gets slow -- going through an overloaded 6rd tunnel server, websites don't load as fast -- trying IPv6 first that then timesout, etc.)
1: No encryption.
Wrong. The protocol has IPsec bolted-on at the socket level. However, you are correct in that nothing knows how to actually use it.
2: Attackers can view your entire IP space.
A: FIREWALL. B: A 2^64 (::/64) LAN will take a LONG time to scan. But, yes, if you know the address of the machine not protected by anything, it's a lame duck.
3: Untested stack, relatively.
Less tested than IPv4, maybe. IPv6 has been around a lot longer than you may realize, and while issues are still emerging, many of them are due to poor protocol design and not poor stack programming.
4: Support is spotty.
This depends on where you are and how much work you put into correcting it (read: tunnels.) But this is ultimately what the entire thread is about... ISPs simply aren't bothering to support IPv6. Those that do are doing so in a mostly jedi-hand-wave gesture for marketing.
Most of it already can. If your ISP is still using 20 year old hardware without IPv6 silicon, it's time to find a better ISP.
Not extensively tested within their network (software, hardware, and management) is the real bottleneck.
Not the way most idiot admins want to use it. "Can I announce "my"
Hah! Can you say "reference leak"? I knew that you could. (it's actually *easier* in Java/C# to leak memory, because you have no way to explicitly destroy an object, so programmers never think about it.)
Something we've gone out of our way to intentionally break (read: FIREWALLS) on purpose for decades.
Actually, in the process of solving the one problem it's supposed to solve, they created about 14 trillion other problems, stuck their head in the sand refusing to learn from history or listen to the industries that use the technology -- *cough*DHCP*cough*, didn't give a single second to privacy or security, and finally simply gave up without ever trying when it came to any type of transition policy/mechanism.
We might as well be converting the internet to Appletalk. While they share a few characters in their name, IPv4 and IPv6 are radically different technologies. From an application programming level, there's not much difference, but that's never been much of a hindrance to IPv6 adoption.