Re: is glib too bloated?

[Gabriel Schulhof <nix go-nix ca>]

On Mon, 2007-04-23 at 21:24 +0200, Michael Natterer wrote:
> You just said "it's bloated" and did not state any specific
> problem you faced. So what exactly is the problem?
Personally, I don't really thing GLib is bloated in any way, but there
are $0.02 I would like to throw in:

Consider a simulation engine: a CLI whose sole purpose in life is to run
for a long time, and produce a file in the end, run, perhaps from some
GUI front end. Now, if the CLI were to have a --help, then niceties like
UTF-8 and gettext would still be appreciated.

OTOH, you might design such an engine to be rather terse - if, for
instance, the GUI were to create a "job package", to be executed by the
user on a cluster, without the user being aware that this CLI is being
invoked.

In this latter case, having a small, highly optimized library with only
the useful data structures could be more desirable. One way to
conceptually split up GLib might be this:

1. Application support (portability, string handling, main loop,
Unicode, ...)
2. Computational support

*shrug*