Post by thread:[PIC]: Other mailing lists?

I have two lists running on my domains (rc-hydros.com and montanadesign.com) and neither costs me 1 centa more than if I didn't have them. A lot of the guys on this list are subscribed to spam_OUTpiclistTakeThisOuTmontanadesign.com already. Andy James Newton <.....jamesnewtonKILLspam@spam@PICLIST.COM> on 10/02/2000 01:41:09 PM Please respond to jamesnewtonKILLspampiclist.com To: .....PICLISTKILLspam.....MITVMA.MIT.EDU cc: (bcc: Andrew Kunz/TDI_NOTES) Subject: Re: [PIC]: Other mailing lists? For several reasons (may I answer that in monthly installments?): A) List server software (sans ads ala egroups) costs big bucks B) There is more in common between AVR's and PIC's than there is different... think about that, its true. There is certainly little difference between SX's and PIC's. C) You can't get the finest 1800 embedded engineers in the world automatically subscribed at the start of the list. (Although I think we can and would start this with people not subscribed to the AVR topic by default) D) You don't have to learn how the new list runs or look for admins or whatever. E) Its address wouldn't be EraseMEPICListspam_OUTTakeThisOuTMITVMA.MIT.EDU... cough, cough, that is MIT.EDU <GRIN> F) You'd miss this admin group. Come on, you know you would... <VBG> G) All you have to do to not see the additional traffic is click on LISTSERVspam_OUTMITVMA.MIT.EDU?body=SET%20PICLIST%20TOPICS:%20-%5BAVR%5D> or (in other words) by sending SET PICLIST TOPICS: -[AVR] in the body of an email to @spam@LISTSERVKILLspamMITVMA.MIT.EDU With an [SX]: topic it would be KILLspamLISTSERVKILLspamMITVMA.MIT.EDU?body=SET%20PICLIST%20TOPICS:%20-%5BSX%5D> and the truly PICish would never hear about Scenix again. Neat huh? --- James Newton (PICList Admin #3) RemoveMEjamesnewtonTakeThisOuTpiclist.com 1-619-652-0593 PIC/PICList FAQ: http://www.piclist.com or .org {Original Message removed}

There is (or has been) an AVR list. And a scenix list. And an 8051 list that is a least active if generally boring... For some reason, the PICList is unusually "lively" - even the off-topic emails seem to be more relevant and interesting than those that occur (or have occurred) on other mailing lists. I suspect it has a lot to do with the PIC's broad market "niche" that spans students, hobbyists, small and large businesses. A lot of users of other microcomputer architectures could benefit from the discussions that occur here on algorithms, peripherals, business, manufacturing, and so on... BillW -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! use spamBeGonelistservspamBeGonemitvma.mit.edu?body=SET%20PICList%20DIGEST

> A lot of the guys on this list are subscribed to TakeThisOuTpiclistEraseMEspam_OUTmontanadesign.com > already. But I don't understand WHY have another list for the same processor? Seems like extra work for readers, writers and admins. To what advantage? From a consumer's point of view, having a lot of the brains in one place is a great thing. Yes, there is quite a bit of time spent bickering about protocol on this list, but you'd think that could be solved administratively more easily and effectively than starting new lists everywhere? Bruce Cannon Style Management Systems http://siliconcrucible.com (510) 787-6870 1228 Ceres ST Crockett CA 94525 Remember: electronics is changing your world...for good! -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! use RemoveMElistservTakeThisOuTmitvma.mit.edu?body=SET%20PICList%20DIGEST

Bruce Cannon wrote: > But I don't understand WHY have another list for the same processor? Seems > like extra work for readers, writers and admins. To what advantage? From a > consumer's point of view, having a lot of the brains in one place is a great > thing. Yes, there is quite a bit of time spent bickering about protocol on > this list, but you'd think that could be solved administratively more easily > and effectively than starting new lists everywhere? I agree; When interfacing from a microcontroller to another device (say an I2C or SPI device, a 24LCxx, a 27C256, or a keyswitch), there's very little difference between processors, in what you need the I/O pins to do. Those extra clocks and pull-up resistors and so on are going to be the same, whether you're using a PIC or a Scenix or an FPGA or ??? Also, when debugging any algorithm, the more eyes looking at your code, the shallower the bugs. Mark -- http://www.piclist.com hint: To leave the PICList piclist-unsubscribe-requestEraseME.....mitvma.mit.edu

>Also, when debugging any algorithm, the more eyes looking at your code, >the shallower the bugs. You mean what was one bug turns out to be ten, but more evenly spread ? ;-) The piclist is not going the open source way anytime soon afaik. Most disguised help requests veil the subject so much that extra prodding is required to bring it out so as to be able to answer. Peter -- http://www.piclist.com hint: PICList Posts must start with ONE topic: "[PIC]:" PIC only "[EE]:" engineering "[OT]:" off topic "[AD]:" ad's