Review of C64 by Jeremy
From Maze
(Difference between revisions)
(New page: == OVERVIEW AND RECOMMENDATIONS == The sections of the C64 chapter are all relevant, work as a group, and actually fit together quite logically with natural transitions -- they do not nee...) | |||
| Line 1: | Line 1: | ||
| + | * [[Assembly vs BASIC]] (Ian) | ||
| + | * [[Hidden Code]] (John) | ||
| + | * [[RUN]] (Casey) | ||
| + | |||
== OVERVIEW AND RECOMMENDATIONS == | == OVERVIEW AND RECOMMENDATIONS == | ||
| Line 26: | Line 30: | ||
== INDIVIDUAL DRAFTS == | == INDIVIDUAL DRAFTS == | ||
| − | '''RUN (Casey)''' | + | === RUN (Casey) === |
This section is a great hook for the whole chapter. I suggest that the first few sentences be split off as the introduction, and that a fourth section (or subsection) be inserted. After the line: "Imagine [...] The screen erupts into motion as lines flow onto the screen." I'd suggest inserting a brief section on the C64 as other than a BASIC / assemply platform: as a completely described spectacle, as an assemblage of certain physical components, as a consumer product available for certain prices in certain markets to certain types of consumers, etc. This section might be a paragraph or it might balloon into something quite large, but no matter how large it gets, it can end back at the imagined situation "...when you type RUN. As each row fills with symbols" etc. | This section is a great hook for the whole chapter. I suggest that the first few sentences be split off as the introduction, and that a fourth section (or subsection) be inserted. After the line: "Imagine [...] The screen erupts into motion as lines flow onto the screen." I'd suggest inserting a brief section on the C64 as other than a BASIC / assemply platform: as a completely described spectacle, as an assemblage of certain physical components, as a consumer product available for certain prices in certain markets to certain types of consumers, etc. This section might be a paragraph or it might balloon into something quite large, but no matter how large it gets, it can end back at the imagined situation "...when you type RUN. As each row fills with symbols" etc. | ||
| Line 33: | Line 37: | ||
| − | '''Hidden Code (John)''' | + | === Hidden Code (John) === |
John explicitly suggests that a discussion of character-set / graphics should be prefixed to this section -- I agree, my own section on this should probably be removed from the Maze chapter and moved before this, and mentioned in reference during the Maze chapter. However, given that I wrote that section, I'd like other authors to confirm that they think it is the right fit. | John explicitly suggests that a discussion of character-set / graphics should be prefixed to this section -- I agree, my own section on this should probably be removed from the Maze chapter and moved before this, and mentioned in reference during the Maze chapter. However, given that I wrote that section, I'd like other authors to confirm that they think it is the right fit. | ||
| Line 50: | Line 54: | ||
| − | '''Assembly vs Basic (Ian)''' | + | === Assembly vs Basic (Ian) === |
The transition between this section and the last needs to be made explicit, but this section starts with great context. Whether the low/high discussion is moved up or left here, I think it might be important to make clear that "low/high level" languages are relative -- i.e. BASIC is quite high compared to assembly and machine code, but it is still quite 'low' in comparison to many languages (in fact, today some consider C low). | The transition between this section and the last needs to be made explicit, but this section starts with great context. Whether the low/high discussion is moved up or left here, I think it might be important to make clear that "low/high level" languages are relative -- i.e. BASIC is quite high compared to assembly and machine code, but it is still quite 'low' in comparison to many languages (in fact, today some consider C low). | ||
