<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Software bloat - Page 2 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Software_bloat&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Software_bloat&amp;p=3">3.Next</a>
</p>
<p>including to describe undesired <a href="page.php?w=user_interface">user interface</a> changes even if those changes had little or no effect on the hardware requirements. In long-lived software, bloat can occur from the software servicing a large, diverse marketplace with many differing requirements. Most end users will feel they only need some limited subset of the available functions, and will regard the others as unnecessary bloat, even if end users with different requirements require those functions.</p>

<p>Actual (measurable) bloat can</p><p>
<a accesskey="1" href="page.php?w=Software_bloat&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Software_bloat&amp;p=3">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
