This post by me was originally posted in the wrong place ... Propeller 2 Specs
... moving it to a better place.
Some very kind people already replied to the original posting, so you may have some related material there
Thanks for some really informative replies.
Please let me know if I am posting in the wrong place and I will move the topic accordingly.
So, in a nutshell, it sounds like:
* C libraries consume excessive RAM on a P1
* on a P1, Spin + Propeller Assembler is generally advised/preferred
* there are, however, optimized C libraries provided by Parallax which reduce the overhead (are they pre-loaded in the firmware ?)
* Spin byte-codes are especially compact (I assume like in java byte-code ops, there is a seek nature to the instruction set allowing smaller chunks to be loaded)
I have read this document:
* I am less comfortable playing with registers than I am with traditional object modelling and encapsulation (C++/Java where the metal is far far away)
* I have only rudimentary Assembler experience and would be significantly less productive there ... BUT if the potential win is significantly greater than choosing alternative paths, I would still adopt it
* C is fine (if I have good debugging tools with which I am proficient)
Spin sounds excellent from the perspectives of lower entry barriers and thinking-in-object-land.
Questions I have:
* Is Spin a language that you people feel has led you to obtain better results (quality/productivity) ?
* Is Spin a language that will be offered on the P2 ?
Otherwise, I am off to try and learn how to put my first project together
.... and I am happy to hear anything you guys have to say
Once again, thanks for reading !