Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Joshua Cranmer Newsgroups: comp.lang.java.programmer Subject: Re: Managed-Code Bloat Date: Mon, 06 Jun 2011 11:35:37 -0400 Organization: A noiseless patient Spider Lines: 15 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Mon, 6 Jun 2011 15:35:38 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="bAymlyY9SkaJNa8Tz2rerw"; logging-data="13114"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19EZc46//CAvrAAEx1v+P1Ara89GLPwhus=" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.16pre) Gecko/20110305 Lightning/1.0b3pre Thunderbird/3.1.10pre In-Reply-To: Cancel-Lock: sha1:AQsS6Ok/VDEtEJWoQdtMq3zMUD0= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5016 On 06/06/2011 02:47 AM, Lawrence D'Oliveiro wrote: > The whole managed-code/auto-garbage-collected concept may really appeal to > corporate code-cutter types, but I think it has real trouble in the mass > market. From a programming language design concept, one thing is abundantly clear: manually-managed memory is a failure. Most programmers--even the very best--have very little ability to prevent memory from being leaked. That's why pretty much everyone accuses every very large application written in native languages as acting like a leaky bucket: Windows, Firefox, etc. -- Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald E. Knuth