Really, even if you are completely ignorant about it, it does not take much more than a short reading to see how simpler IPv6 is. That's why it corrects so many issues.

The problem with IPX style local names assignment is in security. Doing it in the open, wild Internet is a certain way to destroy it. The nearest option that's actualy usable is dynamic DNS, and it's quite widspread.

I just decided to upgrade my 2011 computers, so I got out to searching what improved.

Changed the heat sinks, fans, and casing. Also, changed the power supply of one of them. Nothing else was worth it.

A high resolution display is on my list, but it's still too expensive, so I'm waiting...

What happened to Slashdot lately?

There's a xkcd for that: http://xkcd.com/1104/

"Administrative operations" is everything a governemnt does.

What about just not allowing passwords to connect from a network? Is it too simple, or what?

It's simply stupid to prohibit robots from connecting. It means you'll never be able to automate your work. It's also not viable to lock the system, as it'll turn any bot anywhere into a severe DoS attak. And trying to discern intent from behaviour is way too hard a task for a computer.

You can't change the referential during calculations. Not on Classical Mechanics, because referentials can not accelerate, and in general relativity things are much more complex. Thus, no, it does not take the same amount of energy to accelerate from 0 to 10mph as it does from 90 to 100mph.

What may help you is realising that classical mechanics do not hold for acelerating referentials. And, yes, the added energy varies with the choosen referential.

You're not talking a huge difference in speed at that point...

Are you aware that the kinetic energy is proportional to the SQUARE of the speed, right? There is a huge difference in safety - much bigger than between 40MPH and 70MPH.

You know, in a imaginary future where machines outcompete humans in every task, and no job is available for more humans to perform anymore, all those problems you cited just go away.

Syntax highlighting? Does that even work in the terminal version?

Yes, it works on the terminal. Autocompletion, and real time compiling also do.

Nah. Each one of those clocks are showing their own time, that may disagree by minutes or entire hours... I don't use a watch, but only use the computers and telephone clocks.

How would a telephone call work on a watch? One can put it near either the mouth or a ear, not both, and in any of those situations, it's quite an unconfortable position.

Thanks for the rerash.

People do use VoIP. And of course people don't use services that break in a NAT, they can't.

The problem is worse than that. It's a matter of the media missrepresenting the problem, and people not looking into the details to notice the hype.

I've never seen a technical forecast being delayed, only anticipated. The first one I saw from the working group was working with widespread adoption (like what we have now) of IPv6 by 2020-2025 and IPv4 addresses running out by as late as 2030. The media can't stand having that much time to fix a problem.

Which won't be for a long while because of all the old computers out there that have either no or insufficient IPv6 support.

Just how old are you estimating those old computers are? Windows XP has support for IPv6, as do the first 2.6 Linux kernel. I doubt there's a single smartphone without support for it.

The only reason we are not using IPv6 all along is because ISPs decided to save some 5% (probably less) of the cost on their last upgrades, or because they actively don't want to supply it.