The idea of solving the problem by reclaiming IPv4 addresses was considered, but the math doesn't work:

Now, average daily assignment rates have been running at above 10 /8s per year, for 2010, and approached 15 /8s towards the end. This means any reclamation effort has to recover at least 15 /8s per year just to break even on 2010’s growth. That’s 5.9% of the total IPv4 address space, or 6.8% of the assignable address space.

Looking at the /8 blocks assigned to organizations other than regional NICs, there are 40 of them. So even if we could persuade all those organizations to give up their /8s, and even if we could organize it all quickly enough, the best we could do would be to put off the problem for 3 more years.

In addition, reclaiming IPv4 addresses is far more expensive than rolling out IPv6, and it's hard enough to persuade companies that they need to roll out IPv6.

And the calculation for class B allocations is even worse, because you have to deal with a lot more organizations; the cost is higher for far lower returns.

If you are working on an existing project that has already chosen to use jQuery, then you should learn it.

Otherwise, I wouldn't bother. Just learn Vanilla JS, and skip jQuery. Your pages will be faster and better.

jQuery was a useful thing a few years ago, but now that browser standards compliance is so much better it's a big chunk of unnecessary code.

"Now seriously..." doesn't stop a sexist joke from being sexist.

Indeed. And he was given the chance to put his side of the story on June 10th. Unfortunately for him, he made a non-apology apology, saying:

"I did mean the part about having trouble with girls. It is true that people - I have fallen in love with people in the lab and people in the lab have fallen in love with me and it's very disruptive to the science because it's terribly important that in a lab people are on a level playing field. I found that these emotional entanglements made life very difficult."

and

"It's terribly important that you can criticise people's ideas without criticising them and if they burst into tears, it means that you tend to hold back from getting at the absolute truth. Science is about nothing but getting at the truth and anything that gets in the way of that diminishes, in my experience, the science."

As for the idea that he was taken out of context, the linked article which is supposed to support that idea quotes him as saying:

"Let me tell you about my trouble with girls. Three things happen when they are in the lab: you fall in love with them, they fall in love with you, and when you criticise them they cry. Perhaps we should make separate labs for boys and girls?”

So yeah. He was sexist in context, he was given the chance to put his side of the story, he doubled down and said he stood by his comments and made more sexist remarks, and only then did he lose his job on June 11th.

Submitter should probably spend less time reading Brietbart.

I have native IPv6 on Time Warner. I just had to arrange a modem swap. Call 'em up and ask if you can get a DOCSIS 2 modem.

2: If IPv6 were backwards-compatible, we wouldn't. We could go from IPv4 to IPv6 just like going from CDs to DVDs to BluRay. But it isn't and therefore we won't ever replace that structure.

IPv6 is backwards-compatible in exactly the same way that BluRay is backwards-compatible with DVD.

Your BluRay player has a BluRay VM and Java VM, and uses H.264 encoded video. None of that is part of DVD playback. There's a totally separate stack of code that handles DVD menus, MPEG-2 video, and interleaved MPEG transport streams. Your separate DVD software stack and BluRay software stack sit on top of a single piece of hardware for reading data from the discs. The UI then makes the distinction largely invisible.

And similarly, my computer has an IPv4 stack and an IPv6 stack, and they both sit on the same network hardware that reads the packets. And the OS makes the distinction largely invisible to the end user.

According to the man page on my Mac:

          The getopt_long() and getopt_long_only() functions first appeared in GNU
          libiberty. The first BSD implementation of getopt_long() appeared in
          NetBSD 1.5, the first BSD implementation of getopt_long_only() in
          OpenBSD 3.3. FreeBSD first included getopt_long() in FreeBSD 5.0,
          getopt_long_only() in FreeBSD 5.2.

Not to mention SMS is not reliable. SMS messages are not guaranteed, they are delivered on a "best effort" basis. Your mobile network is free to drop them on the floor and not retry if your phone moves out of signal range, the network is congested, or any other reason they feel like. This is particularly prone to happening when messages have to go across network boundaries.

Obviously the person who wrote the summary was under the mistaken belief that SMS is designed to be reliable, just like lots of people believe that email is designed to be instant...

And depending on how it goes about it, I may have no problem with that.

Learn Ruby. It's what Perl 6 should have been — the good stuff from Perl, but cleaned up.

Then you can either go the devops/sysadmin route — both Puppet and Chef are written in Ruby — or you can go the Rails or Sinatra route and head towards web services development.

So yes... it is theft. Suggesting that it isn't is just a specious rationalization used by people who don't want to feel guilty about it.

Like the US Supreme Court, for example.

But I was wondering if some slashdotters could share some constructive real-life experiences of planning a transition to a relatively offshore-proof career.

Well, how good are you at giving blow jobs? The oldest profession is unlikely to get offshored.

BSD got its automatic live self-defragmenting code from OS X. Then there's libdispatch/GCD, LLVM, and so on.

Yeah. I was there at the time, writing patches for the Minix kernel... Linus specifically wanted support for 386 protected memory and virtual memory. AST wouldn't do it, because it would mean Minix wouldn't run on 68000-based systems like my Atari ST. So Linus went away and hacked together his own 386-only replacement kernel over a weekend.

ROGER CARASSO died last year while on vacation. I think that is more worthy of a thread on Slashdot.