On Sat, 17 Nov 2007 21:16:47 +0000, Roy Schestowitz
<newsgroups@xxxxxxxxxxxxxxx> wrote:
>____/ Phil Da Lick! on Saturday 17 November 2007 20:36 : \____
>
>> [H]omer wrote:
>>> C# Memory Leak Torpedoed Princeton's DARPA Chances
>>>
>>> .----
>>> | 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.'"
>>> `----
>>>
>>> http://developers.slashdot.org/article.pl?sid=07/11/17/0552247
>>>
>>> Microsoft's finest "coo-ality" Slopware.
>>>
>>
>> Never liked the idea of sloppy coding based on garbage collection
>> myself. It's alright assuming that things will be deleted on idle action
>> if you can't be arsed to delete it yourself but what happens if your
>> application is mission critical and mostly working?
>>
>> Bad approach = bad result.
>
>lwn.net has a new long new article on memory.
>
>Memory part 6: More things programmers can do
>
>http://lwn.net/Articles/256433/
>
>The best part of the "Microsoft Car Needs Rebooting Because of Memory Leaks"
>article above is this:
>
>"After 40 minutes, we would stop the car and reboot the computer to restore the
>performance."
>
>http://www.codeproject.com/showcase/IfOnlyWedUsedANTSProfiler.asp
No, the best part is:
"We added one line of code to remove the event subscription and, over
the next three days, we successfully ran the car for 300 miles through
the Mojave desert."
Which means: we are idiots. We don't know how to write code and we
don't know how to test.
The next best part is:
"Driverless Truck Running on 10,000 lines of C# Code"
How much can you achieve with 10,000 lines of C? I bet that's not
enough to even initialize the damn hardware... let alone drive the
car...
|
|
