Is newlib' primary intent still targeted for embedded system use?

[Paul Schlie]

Just curious, as newlib seems to be increasingly growing in both size and
complexity seemingly to satisfy either Cygwin's platform requirements
and/or more comprehensively satisfy various standards often with seemingly
little apparent corresponding embedded system need, and/or correspondingly
becoming increasingly dependant on presumptions of data type sizes typical
of larger 32-bit platforms and memory availability, as opposed to those
Likely 32-bits or less in size (typical of most smaller embedded systems).

Is this intentional, or just a misperception; as not clear what newlib's
role is intended to be if likely to slowly approximate the comprehensive
complexity that glibc already offers?

Please note I don't mean to single out any particular feature, but merely
note that without any constraining philosophical guidelines, newlib may
likely continue grow in complexity to the point where it may no longer
be considered an appropriate basis for an light-weight embedded system
C library; if this remains it's intent?

Alternatively although aware of the growing interest in Linux being used
as the basis of larger embedded systems, however personally don't consider
an embedded system based on a reasonably comprehensive Linux (or Unix) OS,
a true typical embedded system, but rather simply a small computer platform
in it's own right; likely well beyond the scope of 99% of all embedded
systems implementation requirements in practice.