From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Mon, 2 Dec 2013 19:12:48 -0500 To: 9fans@9fans.net Message-ID: In-Reply-To: References: <5fc4ecdb1523a9dbda1829df0018500a@proxima.alt.za> <20131202183901.Horde.so34A23woqwLYjKomWz6Ag1@ssl.eumx.net> <74126e01b30ebb946afb3adcd8705e01@coraid.com> <20131202212426.0730342a@zinc.9fans.fr> <23d08c32941ef86be9e751700edf48b0@coraid.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Go and 21-bit runes (and a bit of Go status) Topicbox-Message-UUID: 8ef7af3e-ead8-11e9-9d60-3106f5b1d025 > At a high level it is about excess baggage that needs to be carried to > provide a familiar environment for either language. Python needs Posix, so > we have to carry its APE baggage, whereas Go brings its own Plan9-ish > baggage (?[cl], lib9, libbio, etc.) and you'll need to give it some hooks > to hang them on. python's requirements are a proper subset of go's, since building go requires python be installed. > 2. Use of Go's libbio, rather than Plan 9's. Alternatively libbio on Plan 9 > can be changed. It's not clear to me why this would be a bad thing. i object to the macros they have been adding. they haven't been included in p9p, either. adding B(put|get)(le|be)(Biobufhdr *b, int width) might be an interesting convienence, but what they've got for the sake of 1% on micro benchmarks seems to run counter to the plan 9 culture to me. - erik