Review of BASIC by John

Legacy: Tracks where the language has gone since its heyday at the dawn of home computing. VB is strongly mentioned (along with a discussion of introducing objects, visual IDEs, etc.) but put into contrast with Mono and various niche implementations to pose the question of which version is the true legacy of C64 era BASIC usage and ethos. Suggests another type of successor in learning languages like Scratch, but also talks about the difference in using a language to learn programming and learning programming by using a language (ie, learning with intent vs. learning due to hands on use because the user wants to run a program).

Legacy: Tracks where the language has gone since its heyday at the dawn of home computing. VB is strongly mentioned (along with a discussion of introducing objects, visual IDEs, etc.) but put into contrast with Mono and various niche implementations to pose the question of which version is the true legacy of C64 era BASIC usage and ethos. Suggests another type of successor in learning languages like Scratch, but also talks about the difference in using a language to learn programming and learning programming by using a language (ie, learning with intent vs. learning due to hands on use because the user wants to run a program).

== General Comments ==

== General Comments ==

I'm not clear on the connection between the two sections that would put them in the same chapter. What is the overall structure/goal? One seems like a sort of evolutionary history that explains how the language developed, and the other seems like a discussion on a historic means of implementation. While I can see the two co-existing, I don't have any clear picture of what the intent is here. Both sections need to have some sort of common thread introduced that can run throughout if they are to stay together, but I might move the Typography section to be a sidebar in the Token-by-Token Explanation and leave this chapter to expand on the 10 Print in Memory ideas.

I'm not clear on the connection between the two sections that would put them in the same chapter. What is the overall structure/goal? One seems like a sort of evolutionary history that explains how the language developed, and the other seems like a discussion on a historic means of implementation. While I can see the two co-existing, I don't have any clear picture of what the intent is here. Both sections need to have some sort of common thread introduced that can run throughout if they are to stay together, but I might move the Typography section to be a sidebar in the Token-by-Token Explanation and leave this chapter to expand on the 10 Print in Memory ideas.

== 10 Print in Memory ==

== 10 Print in Memory ==