Re: Split group?
Juha Laiho wrote:
clj.beans and clj.corba are admittedly of low traffic; it might be possible to
get those removed. However, beans seem to be a construct which every now and
then rises into the general interest in some form, so I would be careful
when deciding on removal of that group. clj.databases, on the other hand,
is a live group, and stays very nicely on topic. If we just could get the
rest of Java&database-related discussion from clj.programmer into the
correct group..
Discussion of Enterprise beans and of Netbeans occurs daily in c.l.j.p
right now, so I don't think beans aren't "in the general interest in
some form", but they don't seem to get discussed in .beans either ... :)
So, in short, I support creating comp.lang.java.server-side, and also
support having the clj.corba removed, but otherwise would leave the clj
hierarchy as it is today. One reason for this is that removing groups
hasn't worked that well in quite a long time: there are too many badly
run news servers that removed groups remain alive at least to some extent.
I don't care for the name ".server-side", since it makes sense for the
network programming, whether client- or server-side, to be in one place,
and away from the basic core language discussions.
If group removal did work, I'd propose replacing clj.programmer with clj.misc,
to keep in the spirit with other hierarchies.
That drags in everything to do with Java from an end-user perspective,
such as installing a JRE and the like.