Let me just start by saying that I loved this class and that Scott is a true homie. However, that does not mean this class is easy, even if it is an easy A. Let me also preface this with the fact that I had 0 graphics experience before this class.
***
TL;DR: Easy to get an A, but not necessarily an easy class. Not a lot of projects, but projects can take a while depending on how good you are at graphics. Exams are easy. Final project is group project, so either take class with friends or hope the group you get in does their work. You don't need the textbook. Uses Piazza.
***
Grading is broken down into 4 assignments, the final term project, and optional midterm and final exams. The class is graded on a point system, aka you need 950 for an A-, 1000 points to get an A, 1100 for an A+. The four assignments are worth a total of 350 points including 50 points of extra credit (so 300 points without EC). The final project was out of 600 points, and the midterm was 150 points. The final was 140 points. I believe in past quarters you only needed 900 or 950 to get an A, so it's a bit harder to get an A nowadays.
***
The four assignments are broken down as follows:
0. A joke. Literally just make it run and you get a startling total of 0 points. Lol.
1. One of the harder assignments in the sense that you have no idea what you're doing (unless you have previous experience). Looking back, it was a pretty simple project, but at the time I was like wtf how do I render a cube idk man. Once you get "boilerplate" aka "hello world" up, it's smoother sailing from there. This was 100 pts w/ 30 pts EC.
2. Cool planet assignment. TA gave us template code that was useful and made the project much easier. 150 pts, no EC.
3. Simple texturing assignment. Easy. 50 pts, 20 pts EC.
The reason it's easy to get an A is that if you do the assignments and do the exams, you will get the points. It's very clear whether or not you're going to get the points… either you implemented the requirement listed, or you didn't. If you don't do the assignments, then you're not going to get the points and you won't get the grade you want. Easy as that. Scott writes out the point values of each feature you have to implement, so it's really all on you to get the points you need.
***
The midterm and final exams are "optional" in the sense that if you need the points, then take them and get those points. If you don't, don't. If you don't want an A, then you don't need to take the exams. Etc. etc. etc. The midterm was either a paper exam with short answers or a hackathon for up to 4 hours with the theme "data visualization". You could choose either option. The final was 40 MC, 3 points each with 20 pts EC. Both exams were open note.
***
Scott's lectures are more theoretical, but his slides tell you everything you need to know for exams. Starting assignments with just his slides can be more challenging, but TAs in discussion show you some example code and help you get started. Most of the material can be found in the textbook, which is NOT required to get because there is no mandatory reading and it isn't really helpful for the assignments. Discussion is generally a bit of theory and then the TAs show how to implement some feature. Not critical, but helpful for the final project to get special topics implemented.
***
The final project was 600 points, but there were EC points for most impressive and class favorite. Only the projects with the top 3 votes in each category got points, but I think it would have been better if for every vote, the team got like 10 EC points. The group project could be 3-5 people, and more people meant more features you were required to implement. Group members grade each other, too, but otherwise get the same score on the projects. It could basically be any project you want, but you have to submit a proposal to Scott to get confirmed as an acceptable project.
***
I think the class was worth taking, and the final project is definitely something worthy of a resume (unless you don’t put any effort into it). Definitely cool to learn WebGL and once you know how, pretty easy to create something to stick into any website.

In short, this was an easy class, and an easy A.
I was very excited to take this class especially since I thought it would be a great opportunity to mix my passion for art with computer science.
This class used WebGL and was all in Javascript and GLSL. There are 4 HWs, 1 easy midterm, 1 easy final, and 1 group project (can be time consuming & is bulk of grade).
The class is not curved, and is straight point based. If you do all the assignments with the extra credit, and get a higher grade on the final group project, you could honestly not even take the final and still get an A.

Lectures:
2 hours long, and honestly they were not necessary since the slides are always posted. The only reason I would go anyway was because I knew I wouldn't have gone over the slides on my own. Although Friedman knows what he's talking about, the lights were always dimmed and I found myself dozing off most of the time. However, he is always open to questions and answers them well (even if they are off topic). He is not a full time professor, so he only takes appointments for office hours.

Material:
Pretty easy to understand. The concepts are covered in a more high level sense. As long as you understand the basic way that a certain computer graphics technique works, you should be fine (for the midterm and final at least). Typically, Computer Graphics courses are heavily math based, and you need an understanding of linear algebra. In this class though, math was not really needed at all. I never took Math 33a/b and was fine. You just need to know the basics of matrix transformations, and those are not hard to learn as you go.

Assignments:
3 total , 50pts each ( there was a HW #0, but it was 0 pts). They are pretty straight forward, and the instructions are very clear compared to other CS classes I've taken. They're also relatively fun to do. Although we used WebGL, we had a TinyGraphics Library made by one of the TAs, so we never had to code from scratch, just add in snippets of code. We usually had 1-2 weeks to work on hw, and took me 4-6 hours to do. They are all in Javascript, with a few needing GLSL. I had never worked with either languages and caught on very quickly. I had a harder time with GLSL, but there was only one assignment that required us to modify shaders that used the language.
All assignments had extra credit opportunities (most up to 15 pts).

Tests:
All multiple choice and concept based. No coding was required, just need to know the vocabulary. We were allowed 1 page cheat sheet for midterm and 2 pages for the final. They are a smaller part of your grade, so you don't have to worry much about them.

Group Term Project:
Probably the most important part of the class. Friedman is very vague with instructions because he wants us to be creative and make anything we want as long it is a graphics application. Most people make games, but you can create anything. We had to be in groups (min 3, max 5). My group created a game, and we spent about 20-30 hours working on it total (within a span of the 3 weeks we had). It can be hard depending on how extravagant you want your project to be, but the workload was not bad. At the end of the quarter we have a Demo Day where all the groups present their projects in front of the class.

Grading:
3 HWs: 50 pts each (EC available)
Midterm: 100 pts (EC available)
Final: 150pts (EC available)
Term Project: 600pts (450 from professor, 100 from teammate evaluations, 50 from class evaluation)

Final grades: D-: 500+, D: 550+, D+: 600+, C-: 650+, C: 700+,
C+: 750+, B-: 800+, B: 850+, B+: 900+, A-: 950+, A: 1000+, A+: 1100+

Overall, I had fun, and would recommend the class - especially if you want to go into gaming or graphics.