So I've never been thrilled about people using Arduinos in production,=20
because the culture is generally that of hammer it out as brute force=20
and bloated as possible, as long as it works for a few seconds, and this=20
has given me a lot of distrust in the libraries etc.  Add that it's not=20
easy to do write protection, change oscillator modes, etc.

But I recently started looking into PIC32's again, and thought I'd use a=20
Chipkit that I have here as a dev board (without the Chipkit software=20
and bootloader, so I would use MPLAB etc).  But as Chipkit, Teensy, and=20
others are becoming more and more popular, and the *duino IDEs are=20
getting mature, it's becoming very tempting to take advantage of the=20
ease of development and just go with the MPIDE/UECIDE and associated=20
libraries, especially as I'm looking into using WiFi, Bluetooth, SD=20
cards, etc.  And let's be realistic -- Microchip's libraries aren't=20
perfect anyway.

So what's the general feeling on this?  Is there a compelling reason to=20
go or not-go this way?  What about the license -- I've not read the=20
license yet but do I need to make my code open source?  I'm assuming I=20
can set the code protection bits with MPLAB IPE, etc.

Cheers.

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