I can agree that a cleanup might be needed, though, but I really don't want a split.
I only add things I consider to be at least marginally useful to a random program writer to Pike. I have added the AIDO modules to aido directly, as an example (MPlayer bindings etc), not to Pike.
And then some modules are very server or client oriented.
But I think it's not a good idea to have a pike-server and pike-client distribution, though. As an example, client applications generally don't need Shuffler, Databases (mostly), Java, Kerberos, Yp or Fuse.
Fuse is useful for server-applications on Linux, btw, you can very easily provide a normal filesystem view of your data, with editing and all. Saves a lot of time otherwise spent writing UI:s (eg, edit your data and metadata for your files in your HTTP-based content manager with emacs or word or whatever)
(It's also very pleasing to write a new filesystem in 10 minutes. :-))
Server applications tend to avoid GTK, Gnome, SDL, GL and the other UI modules.
As for cleaning up, I think these modules no longer have to be kept in Pike: Pipe (Shuffler replaces pipe, pipe kept for compatibility) GLUT (SDL is much better, and provides similar services) Perl (But it's sort of cute to emped Perl in Pike) SSleay (who uses this when the built-in SSL module works better)
And then we have the modules with very interresting names: _Roxen (this is mostly HTTP utility functions) spider (XML parser, compat HTML parser)