|
Re: How important is Linux?
I just want to add a few words to this conversation.
I agree with all the comments on this topic regarding having an RTOS on a new controller that hail the benefits of being able to write higher level and complex code with less effort. Having well-defined high-level APIs for programming a system are an absolute must. Why should I have to know how to make the microcontroller do backflips in order to do something that any RTOS would provide to me by default? I'm all for learning about what makes the box tick, but in 6 weeks I refuse to perform open-heart surgery every time I want to do something new.
Does Linux have to be that RTOS? Well, we should definitely have an RTOS that is suited to a particular hardware controller, and have good APIs for working with the hardware from the native development environments. I honestly don't care what RTOS is on the controller, so long as it's fairly well documented and supported - If I can't get an answer on why X does Y when I do Z in 48 hours or less, then it's junk to me. I do expect some growing pains during the first year while we're all trying to learn the new system, but a bank of somewhat-experts would be nice to consult with if such a group could be assembled.
I am probably biased since I work on an RTOS for a living, but if *I* had to know everything about the hardware I am writing my RTOS for in 6 weeks then I'd be in a heap of trouble - I couldn't do it. Once you move away from hobby components and into more cutting-edge technology, you just can't know everything you need to know to perform direct programming NOR SHOULD YOU HAVE TO.
-Danny
__________________
Danny Diaz
Former Lead Technical Mentor, FRC 418
|