extensibility

The issue of size can be further addressed by separation of mechanism and policy, and building for extensibility.

Building anything that rivals Wordpress in terms of features, extensibility and ease of use is a massive undertaking.

Regarding extensibility, again, there are people who argue against it and have an opposite opinion to Lispers.

Isn't part of the issue at hand that the extensibility of Firefox is deep, while that of Chrome is shallow(er)?

Virtual methods and functions behave very differently from an extensibility point of view.

Not sure what more, aside from macros, you could want regarding extensibility.

They also typically give better error messages, better performance, better extensibility etc.

A lot of Two's competitors have APIs that take into account things like performance and extensibility, but are harder to explain because of it.

The good scenario is that it provides extensibility for technology that simply isn't standardised yet, and gives vendors a way to differentiate their product.

Overall, the XEP process, conceptually, is a great example of open extensibility.

Chrome has positioned itself towards performance at the cost of extensibility.

Of the people I know who prefer Emacs, what they like is the extensibility and customisation, and not necessarily the keybindings.

That money is better spent on a Mac Mini, or if you need more extensibility from your server then have a look at your local "silent pc dealer" - various levels of noise reduction can be had, from dampened cases to completely passively cooled systems.