got an a job with embedded C programming first week, see that most stuff closed to us, we are dependent on external libraries/companies and they are buggy, call them every time and ask a fixed binary
is this same on everywhere?
It seems most embedded vendors deal exclusively in closed binaries. This seems to be down to both the fear of their shit being "stolen" and to cover up how simple and poor quality it is.
>>5
Yeah, it looks like a big waste of time in our company. A bug on a closed library? call vendors and ask them to fix it. And as far as I know, their shit is really poor quality.
>>1
I would like to try this embedded thing, because I can't understand your point (as a hobbyist, I always use cheap avr or pic µCs to interface the devices/sensors and do everything without external libraries).
>>8 Our chip suppliers are Chinese however.
Talk about setting yourself up for fail. The libraries are probably butchered GPL libs, not that it helps you any.