[wp-hackers] 2.1 Ongoing Work
peter.westwood at ftwr.co.uk
Sat Oct 21 21:21:04 GMT 2006
-----BEGIN PGP SIGNED MESSAGE-----
> On 21/10/06, Matt Mullenweg <m at mullenweg.com> wrote:
>> Rob wrote:
>> > Some people would want to disable it, therefore it's best left as a
>> > plugin", like Akismet is? I certainly agree with that line of
>> > thought—similar to wanting TinyMCE included as a plugin rather than
>> > actually
>> > being integrated.
>> The only reason Akismet is a plugin is because it requires a third-party
>> key to use it. TinyMCE will never be a plugin, unless we switch to a
>> better WYSIWYG.
> Fair enough. I like the idea of plugins as modularity as well as
> extensibility, though.
Personally I think plugins solve the type of problem where multiple
solutions are possible.
For some things making them plugins just for 80% of the user base to
enable them is a bad idea.
- From this point of view I agree with Akismet being a plugin as it isn't
the only solution to the problem it is trying to address. There are
many different solutions out there and people need to pick the one that
works for them.
I would also agree with widgets becoming a core feature as it would be
silly for multiple different implementations to compete. We need one
implementation which all theme authors can use to make there themes more
modular and easier for the end-user to customise.
The 80% rule above is what kills ripping TinyMCE out and making it a
plugin - most end-users expect it to be there - it is the type of
editing environment they are familiar with.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the wp-hackers