> What use is it to discuss controllers if you can't discuss 
> how to interface them, or the bits they interface?  Gotta 
> have EE.  Can't even understand why you would be against it.  
> Adds *so* little processing overhead, I doubt it's even noticeable.

Could be, and was, part of [PIC]. Actually if it has to do with interfacing
a PIC to something, that is STILL part of [PIC]. See the list FAQ:
http://www.piclist.com

But people wanted to talk about stuff that was not directly about PIC's but
still about engineering. The people who only wanted to talk about PICs would
get pissed off about that. So we made [OT]. Then someone who wasn't getting
OT heard about a great engineering discussion on the OT and got all pissed
off that they missed it. So we made [EE]. 

Now posts have to be sorted VERY carefully. The main one for me is this: If
it directly involves a PIC, use [PIC]. I try to enforce that one. Or rather,
gripe at people (offlist) when they post things that have nothing to do with
PICs in the [PIC] topic.

Then, if it doesn't involve a PIC, but it is still about engineering, use
[ee]. 

Then if it has nothing to do with engineering, use [OT]. 

This is why I won't allow more topics. It's difficult enough to sort
messages as it is. It may seem simple to you, but you don't have to deal
with people getting it wrong all the time. <grin>

Not to mention [AD] and [BUY] which keep the sellers and buyers out of the
ire of those who wear rose colored glasses.

And then [sx] and [avr] which pretty much don't get used (my bad idea).

---
James.
 
 

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist