From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3184 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Re: go support (was: Best place to discuss other lightweight libraries?) Date: Wed, 24 Apr 2013 09:39:48 -0400 Message-ID: <20130424133948.GG20323@brightrain.aerifal.cx> References: <1366683267.18069.155@driftwood> <5176FE83.3010301@gentoo.org> <20130424114852.GA99797@intma.in> <5177E020.9000706@barfooze.de> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1366810803 22311 80.91.229.3 (24 Apr 2013 13:40:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 24 Apr 2013 13:40:03 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3188-gllmg-musl=m.gmane.org@lists.openwall.com Wed Apr 24 15:40:04 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1UUzvW-0003XG-3o for gllmg-musl@plane.gmane.org; Wed, 24 Apr 2013 15:40:02 +0200 Original-Received: (qmail 6113 invoked by uid 550); 24 Apr 2013 13:40:01 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 6100 invoked from network); 24 Apr 2013 13:40:01 -0000 Content-Disposition: inline In-Reply-To: <5177E020.9000706@barfooze.de> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3184 Archived-At: On Wed, Apr 24, 2013 at 03:37:36PM +0200, John Spencer wrote: > On 04/24/2013 01:48 PM, Kurt H Maier wrote: > >On Wed, Apr 24, 2013 at 01:18:43PM +0200, Daniel Cegiełka wrote: > >> > >>btw. has anyone used go with musl? > >> > > > >Go ships its own libc, which I'm fairly certain it depends on. It's > >also not suitable as a system programming language and they dropped that > >claim from their propaganda some time ago. > > correct, the go runtime is *very* heavy, and it's always linked statically. > this adds ~ 1.5MB to any binary (at least on x86_64). > that's about equivalent to the bloat imposed by the C++ stdlib. > > on the suckless page, there's something written about plans to > migrate the coreutils functionality to go, this seems like an insane > plan if even dead-simple tools like cat will eat 1.5 MB of your RAM > and storage space. Storage space, yes. RAM, no. It's read-only mapping so it doesn't consume commit charge, and it won't consume physical memory either except for the parts that get paged in. In reality it might still use less RAM than a dynamic-linked program, especially one linked with glibc or with multiple shared libraries. Rich