mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Call for ideas for future musl-related talks
Date: Tue, 30 Dec 2014 14:45:15 -0500	[thread overview]
Message-ID: <20141230194515.GS4574@brightrain.aerifal.cx> (raw)
In-Reply-To: <20141229002929.GC3156@port70.net>

On Mon, Dec 29, 2014 at 01:29:30AM +0100, Szabolcs Nagy wrote:
> my whishlist is
> 
> - why do posix and c matter in the age of web/mobile/cloud
> 
> - good/bad/ugly parts of posix/linux/toolchain from libc pov
> 
> - metrics (benchmarks, size, complexity, amount of libc code
> executed in various use-cases, time spent in libc, etc)

I like your ideas, and IMO this is potentially interesting as a
less-technical talk -- or at least one that's compelling to a less
technical audience but that still gives an opportunity to bring in
technical material.

The "why does it matter" part is nice for bringing up the pitfalls of
container deployment with glibc and mainstream library stacks --
circular dependencies and difficulty of reproducible builds, need for
large supporting infrastructure in your containers, large bug/attack
surface, etc. Of course this doesn't really cover the matter of why
C/POSIX are needed (versus e.g. a core OS built on node.js or lua or
similar) but that's an opportunity to talk about resource accounting
and how hard it is to make a robust system groundwork in a language
that doesn't have a concept of storage and storage duration.

Rich


  reply	other threads:[~2014-12-30 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15  5:04 Rich Felker
2014-12-28 16:24 ` Justin Cormack
2014-12-29  0:29   ` Szabolcs Nagy
2014-12-30 19:45     ` Rich Felker [this message]
2014-12-30 22:11       ` Laurent Bercot
2014-12-31  7:12     ` Natanael Copa
2014-12-30 19:32   ` Rich Felker
2015-01-04  4:17 ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141230194515.GS4574@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).