Rules for buying/selling of IPv4-addresses has already been put in place at the regional internet registries (RIPE, ARIN, APNIC, etc.) as far as I know.
Not that that is really all that important, if people just deploy IPv6 already.
It just helps to make IPv4 more expensive to run, which will just be one of many reasons to deploy IPv6.
"HTML 5 is a major undertaking to rewrite how HTML works in a radically different way."
Actually it is the opposite. It does everything HTML4 does, without the rules everyone thought are stupid and already ignored. And includes a lot of things native which people where already doing through because browsers supported it but wasn't in the spec, javascript-workarounds, plugins, etc. Like HTML5-video people used plugins, now it is native. Like webcam-support, the HTML5-device-tag which isn't support by any browser yet allows that. It was already in Flash, now it will be 'native' to the browser, so you can import an image and manipulate it in javascript directly through the canvas-tag.
They are adding some other things as well, like WebGL.
Things go wrong if your OS thinks it has working IPv6 and prefers that over IPv4 (the default) and tries to connect but the browser needs to wait for the timeout because IPv6 isn't actually working.
Usually this is things like old Mac OS X versions with an Apple Airport with IPv6 enabled which prefers automatic IPv6-tunneling over native IPv4. And automatic tunneling (like 6to4 or Toredo) isn't working all that well.
The automatic tunneling should really only be used if the server/peer you are trying to talk to only has IPv6 and you have no native IPv6.
Look at banks. When a fake bank site goes up, it only takes hours sometimes a few days for it to be taken down after it was asked. Anywhere in the world.
But it is probably better not to take the site down, but to collect IP-addresses and so on anyway.
What you see a lot in the case of Microsoft bugs is, it usually comes from stupid design decisions in the past. Sometimes they just give up and just disable a feature completely.
It is really fun to watch. A lot of the times you can even predict them. Take for example Windows DCOM RPC, I predicted this would be a problem before Windows XP was released.
(if I remember correctly)
Microsoft releases Windows Vista "a completely new version".
They say our development model which leads to much safer code and we've checked old code as well.
Then, look at what happends, a DCOM RPC bug is found all versions of Windows from NT 4 up to Vista are vulnerable.
Slashdot Mirror
Or use a different domain ofcourse.
The real solution is to set a cookie with a path on the site where people are logged in and not have any images in that path on the webserver.
Why ? It does not solve this problem.
That is the first thing they did after they created their source repository.
I'm not very familiar with American culture, but I think the graph says, if you slowly change something no one objects. It's like boiling the frog.
Why hasn't it happend now ?:
http://en.wikipedia.org/wiki/File:Oil_Prices_1861_2007.svg
It's called (like) a CDN, think: Akamai, etc.
As it currently stands we need the rest of the planet to survive to keep ourselfs alive and living fairly comfortably.
Let me correct that, for the spelling nazis and why ever else wants to complain:
A transfer fee agreed between 2 providers for something they do not own
Rules for buying/selling of IPv4-addresses has already been put in place at the regional internet registries (RIPE, ARIN, APNIC, etc.) as far as I know.
Not that that is really all that important, if people just deploy IPv6 already.
It just helps to make IPv4 more expensive to run, which will just be one of many reasons to deploy IPv6.
"HTML 5 is a major undertaking to rewrite how HTML works in a radically different way."
Actually it is the opposite. It does everything HTML4 does, without the rules everyone thought are stupid and already ignored. And includes a lot of things native which people where already doing through because browsers supported it but wasn't in the spec, javascript-workarounds, plugins, etc. Like HTML5-video people used plugins, now it is native. Like webcam-support, the HTML5-device-tag which isn't support by any browser yet allows that. It was already in Flash, now it will be 'native' to the browser, so you can import an image and manipulate it in javascript directly through the canvas-tag.
They are adding some other things as well, like WebGL.
Paving the cowpaths, baby ! :-)
The problem usually is just settings.
Things go wrong if your OS thinks it has working IPv6 and prefers that over IPv4 (the default) and tries to connect but the browser needs to wait for the timeout because IPv6 isn't actually working.
Usually this is things like old Mac OS X versions with an Apple Airport with IPv6 enabled which prefers automatic IPv6-tunneling over native IPv4. And automatic tunneling (like 6to4 or Toredo) isn't working all that well.
The automatic tunneling should really only be used if the server/peer you are trying to talk to only has IPv6 and you have no native IPv6.
http://en.wikipedia.org/wiki/Category:IPv6_transition_technologies
Pay a hefty fee, sell your soul or do nothing.
I think I'll choose do nothing (/go somewhere else).
Judging by a recent 27c3-presentation, I have some doubts a good PDF reader actually exists. The format is such a mess I can't believe it:
http://www.youtube.com/watch?v=54XYqsf4JEY
Is it faster because of the ZFS intent log and second level cache on SSD ?
If the day is 'marketed' properly, then yes that should be fine.
I call this bullshit.
Look at banks. When a fake bank site goes up, it only takes hours sometimes a few days for it to be taken down after it was asked. Anywhere in the world.
But it is probably better not to take the site down, but to collect IP-addresses and so on anyway.
They are thinking of the children that is whole problem ! ;-)
I was talking about OSS in general, PHP is not a very good example of that though. They made many mistakes in the past. :-/
It actually starts at 5 minute, 44 seconds:
http://www.youtube.com/watch?v=rOwMW6agpTI#t=5m44s
"You test and you test and you test, but nothing's certain in the eyes of management. So the shipping is delayed, the testing continues"
This is how Microsoft does it:
http://www.youtube.com/watch?v=rOwMW6agpTI
That does not look like how you described it.
What you see a lot in the case of Microsoft bugs is, it usually comes from stupid design decisions in the past. Sometimes they just give up and just disable a feature completely.
It is really fun to watch. A lot of the times you can even predict them. Take for example Windows DCOM RPC, I predicted this would be a problem before Windows XP was released.
(if I remember correctly)
Microsoft releases Windows Vista "a completely new version".
They say our development model which leads to much safer code and we've checked old code as well.
Then, look at what happends, a DCOM RPC bug is found all versions of Windows from NT 4 up to Vista are vulnerable.
Nice. :-)
1 day, really that long ? ;-)
I've sometimes even seen 1 hour or even minutes from certain OSS projects. I guess it was trivial to fix.
Intel has already a line of Atom-processors with a FPGA for I/O operations.
It isn't very impressive if it hasn't found any bugs. Then it's just plain boring.