Subject:
|
Re: What I would do (2)
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Tue, 31 Jan 2006 22:32:38 GMT
|
Viewed:
|
1861 times
|
| |
|
|
In lugnet.robotics, John Hansen wrote:
> In lugnet.robotics, Tim Byrne wrote:
> > Hopefully I can keep the number of Mindstorms languages I need to be proficient
> > with down to 2 regardless of what brick I am using. NQC when the standard
> > firmware is enough, and BrickOS when more flexibility is needed.
>
> I like this concept, but what if in the case of NQC the new firmware turns out
> to be such a radically different design that it makes it extremely difficult, if
> not impossible, to carry over very much of the rather large API built into NQC
> to the new brick.
>
> Would you prefer that NQC work miracles (at the expense of performance) to keep
> the NXT API as much as possible directly compatible with the RCX2 API or would
> you prefer that NQC work as close to the metal as possible at the expense of API
> compatibility? By "work miracles" I mean something along the lines of "generate
> lots of extra code behind the scenes as needed, including such things as hidden
> tasks and subroutines which act as helpers to the NXT version of the NQC API".
>
> I'm not saying that this will turn out to be the case, but it could. And in the
> unlikely event that it does I am seeking NQC user feedback. Which is more
> important: API compatibility or Performance?
Oh, performance!
NXT NQC should match the NXT brick's capabilities.
How many people have such sophisticated programs that they need to port from the
RCX to the NXT to realisically demand compatibility?
I mean this a robot hobby tool. Half the reason we're here is to have fun
building robots and writing programs for them to make them go!
I really really want the richness of motors with built in position sensors and
bluetooth modules to zip messages to other NXTs to be right there, ready to play
with!
JB
|
|
Message is in Reply To:
 | | Re: What I would do (2)
|
| (...) I like this concept, but what if in the case of NQC the new firmware turns out to be such a radically different design that it makes it extremely difficult, if not impossible, to carry over very much of the rather large API built into NQC to (...) (19 years ago, 31-Jan-06, to lugnet.robotics)
|
24 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
