I blame the lack of autopilot for these human fingers.
First Battleship, now this.
"Licensing issues" seems to be the standard reply. But, why would licensing in Australia be different from licensing elsewhere? Isn't a show streamed to Australia is just as profitable as a show streamed to Europe or America?
Yes, but Netflix must sign and *pay for* a license in each separate territory. The company pays per show/movie, per market, per year (or whatever licensing timeframe), and it doesn't make sense to roll out an actual service until you have the rights to a decent content library in that new territory.
Netflix is working on licenses for Australia, but doesn't have a service yet. And whatever agreements it did sign so far likely don't become active until Launch Date X.
So as usual, it all boils down to costs. Follow the money.
I'm still getting paid for some Perl 5 work. Learned some when it was still hot, built something with passing value, and now I'm pulling a small but significant monthly fee for supporting it.
It's still what I do best, thanks to all this regular practice. Coding is otherwise more of a hobby than a job for me. Can't say that I see a lot of demand for Perl code monkeys out there, though.
At first glance, I thought John Romero had reinvented the scooter. Segway 2.0 with a BFG on the handle bar?
Bring it on!
Some commenters say that Linux and Open Source have been mainstream tools for a while. That's true -- in the tech world. Whitehurst mentions this, then goes on to explain that more traditional industries are accepting FOSS now. Things like railroads and power utilities, where open source remained a scary, newfangled, and unproven security hole as recently as last year.
This was fun! Starting with my little router here in Tampa, the signal bounces to Washington DC, New Jersey, Atlanta, back up to Virginia, across to California. back to New York, before finally landing in Slashdot's native Illinois. Either that, or my IP geolocator is lying to me about the California piece. Ping times don't seem to increase enough to make it all plausible.
1 router (192.168.1.1) 0.415 ms 0.658 ms 0.731 ms
2 L100.TAMPFL-VFTTP-75.verizon-gni.net (188.8.131.52) 10.180 ms 10.310 ms 10.368 ms
3 G0-5-4-5.TAMPFL-LCR-22.verizon-gni.net (184.108.40.206) 13.401 ms 17.740 ms 18.155 ms
4 ae2-0.TPA01-BB-RTR2.verizon-gni.net (220.127.116.11) 17.794 ms 17.863 ms 17.921 ms
5 0.xe-11-1-0.BR2.ATL4.ALTER.NET (18.104.22.168) 30.529 ms 33.033 ms 33.157 ms
6 22.214.171.124 (126.96.36.199) 35.762 ms 35.573 ms 35.569 ms
7 cr2-te-0-0-0-0.atlanta.savvis.net (188.8.131.52) 36.872 ms 25.998 ms 61.362 ms
8 184.108.40.206 (220.127.116.11) 54.209 ms 56.239 ms 56.389 ms
9 hr2-tengigabitethernet-12-1.elkgrovech3.savvis.net (18.104.22.168) 56.506 ms 56.580 ms 56.730 ms
10 das5-v3032.ch3.savvis.net (22.214.171.124) 59.489 ms 59.562 ms 59.623 ms
11 126.96.36.199 (188.8.131.52) 58.696 ms 58.770 ms 58.846 ms
12 slashdot.org (184.108.40.206) 58.912 ms 58.976 ms 58.970 ms