405467
story
BrianAU writes
"Firefox 2.0.0.11 has been released, the Release Notes show the only major change as a correction of a compatibility issue with some websites and extensions as discovered in Firefox 2.0.0.10."
383607
story
nil0lab writes
"In a case of 20/20 hindsight, Princeton DARPA Grand Challenge team member Bryan Cattle
reflects on how their code failed to forget obstacles it had passed. It was written in Microsoft's C#, which isn't supposed to let you have memory leaks. 'We kept noticing that the computer would begin to bog down after extended periods of driving. This problem was pernicious because it only showed up after 40 minutes to an hour of driving around and collecting obstacles. The computer performance would just gradually slow down until the car just simply stopped responding, usually with the gas pedal down, and would just drive off into the bush until we pulled the plug. We looked through the code on paper, literally line by line, and just couldn't for the life of us imagine what the problem was.'"
339979
submission
VORNAN-20 writes:
Yesterday's item here about Comcast screwing around with P2P traffic brings up an idea. Is it time to change the P2P standard to encrypt all traffic? I think that almost any current PC would have no problem handling the extra load, and really, Comcast or any ISP has no business knowing what you are sending in the first place. I am not a network guy but I think that this is doable. If azureus, ktorrent, etc were all to come out with an "encrypt all packets using " option maybe this could be managed quickly and cleanly. It would be best to move quickly before all of the ISPs catch on to this. Come on developers, liberate us from the network meanies!!
