🚀 go-pugleaf

The "Metrowerks Community" seems much more of a hassle than a simple
newsgroup like we have here.  First of all, I have to remember that I
am now "JHOYLE499" and I am not allowed to change it (And why the hell
can't I choose my own ID name?!?!?).  Secondly, there is this
complicated tier of folders and non-trivial organizations that must be
traversed.  Besides, newsgroups are much more easily accessed, even as
I am doing now through google.groups.

I understand the need to simplify, but then why not just say, "Okay
from now on, MWRon will be answering questions only from the
codewarrior.* newsgroups, and that's it."  And you can pair down the
ones you no longer wish to continue supporting.  (For example,
codewarrior.config, codewarrior.unix, etc. don't get much traffic and
they could be absorbed into one of the other newsgroups.)  But a
newsgroup is much more obvious.

What I don't think you are realizing is that people will come to
newsgroups (not knowing about the Metrowerks proprietary board),
seeing no Metrowerks responses and unanswered questions and think,
"See, Metrowerks really is on the way out...they no longer support
newsgroups."