Due: Tuesday, June 28 11:50 PM

(25 points)

Answer the following questions about Douglas Crockford's JavaScript the Good Parts Google lecture. Some questions require more discussion than others, but you will most likely be unable to receive full marks for one-sentence answers.

You may collaborate with other students to come up with answers, but you must write the final responses on your own. Be sure to note anyone you collaborated with in the refrences file.

1. What's a "cut-and-paster"?
2. Crockford mentions the "DOM API"? What do you think that is?
3. What languages influenced JavaScript?
4. What did each language contribute to JavaScript's design?
5. What is the worst part of JavaScript?
6. What is the most misused feature of the language?
7. What is a "bottom" value?
8. Why should you always use the === operator and not the == operator?
9. What are the four good parts?
10. Do your best to describe what a JavaScript Closure is?
11. What example does Crockford use to show where semicolon insertion breaks seemingly good code?
12. What is JSLint?
13. What is Crockford's problem with HTML5?

What to submit

In addition to the files required by the parts above (at least one txt file), submit a text file named references.txt. In this file, provide a citation for each resource you used (excluding class notes, and assigned readings, but including other students) to complete the assignment. For example, if you found a Stack Overflow answer helpful, provide a link to it. Additionally, provide a brief description of how the resource helped you. Your file should look something akin to:

Also provide a readme.txt file that includes your UVA computing ID and directions identifying which files are associated with each part of the assignment.

Your readme should have a format similar to:

Make a zip archive named with your UVA computing ID and "hw4" that includes all of the required files (zip -r [zipfile.zip] [directory_to_zip]). Upload this to the submission website.

Remember, you may upload your submission multiple times. Try this before the deadline so that there is time to recover from any technical difficulties.