Editing Glibc (section)

===Use in small devices===
glibc has been criticized as being "[[Software bloat|bloated]]" and slower than other libraries in the past, e.g. by [[Linus Torvalds]]<ref>{{cite web|last=Torvalds|first=Linus|url=http://ecos.sourceware.org/ml/libc-alpha/2002-01/msg00079.html|title=Posting to the glibc mailing list|date=9 January 2002<!-- 19:02:37-->|access-date=22 July 2007|archive-date=12 October 2015|archive-url=https://web.archive.org/web/20151012215444/http://ecos.sourceware.org/ml/libc-alpha/2002-01/msg00079.html|url-status=live}}</ref> and [[embedded Linux]] programmers. For this reason, several [[C standard library#Implementations|alternative C standard libraries]] have been created which emphasize a smaller footprint. However, many small-device projects use GNU libc over the smaller alternatives because of its application support, standards compliance, and completeness. Examples include [[Openmoko]]<ref>{{cite web
 | url   = http://wiki.openmoko.org/wiki/OpenMoko
 | title   = OpenMoko components
 | quote   = We will use glibc (not uClibC) ... The alternatives may save more space and be more optimized, but are more likely to give us integration headaches
 | access-date   = 13 May 2008
 | archive-date   = 22 April 2016
 | archive-url   = https://web.archive.org/web/20160422073925/http://wiki.openmoko.org/wiki/Openmoko
 | url-status   = live
 }}</ref> and [[Familiar Linux]] for iPaq handhelds (when using the [[GPE Palmtop Environment|GPE]] display software).<ref>{{cite web
 | url   = https://marc.info/?l=familiar&m=118666899424374&w=2
 | title   = Re: [Familiar] Which glibc for Familiar 0.8.4&nbsp;&nbsp;?
 | quote   = Question: which version of the GLIBC was used to build the Familiar 0.8.4 ? Answer: 2.3.3
 | access-date   = 26 November 2018
 | archive-date   = 12 March 2022
 | archive-url   = https://web.archive.org/web/20220312062719/https://marc.info/?l=familiar&m=118666899424374&w=2
 | url-status   = live
 }}</ref>