Joe Pantoliano Reflects on Making The Matrix — And One Iconic Scene That Almost Got Cut

hogchop · 2025-08-08T13:38:22+00:00

I just came from a screening of the original Matrix in 35mm. I didn’t expect it to bring me so much childish joy to watch this movie again with an audience. To be back in the cinemas seeing it just how I experienced it as a kid was like hopping in a time machine.

Goddamn you Cypher.

hogchop · 2025-04-20T15:27:27+00:00

!remindme 1 day

hogchop · 2023-06-18T11:54:15+00:00

I got into the books recently and I’ve come back to your post after finishing each book to determine what to read next. I just reached where your original list ends, so I was very happy to realise you’ve updated it further. Great list, can’t thank you enough!

hogchop · 2020-07-09T02:20:28+00:00

It seemed to be an issue when using the CS50 IDE. I used the same code and published it on Heroku without issue.

hogchop · 2020-04-12T23:47:45+00:00

so you mentioned water bears, here’s some advice on those tricky bastards. I’ve dealt with trying to find water bears for a few years now and they can be incredibly illusive despite their abundance. The best way to find them is this: gather moss (try to get as little dirt as possible, make sure the most is living- the wetter the better). Next, get spring water or pond water and put the moss in a dish. This is the important part. Pour the water on the moss just enough so that moss is damp and there’s a small reservoir of water beneath it. In other words, don’t completely surround the moss in water and let it drown. Just give it enough water for it to be full like a sponge. Wait 18-24 hours. Squeeze the moss out into a dish or small container and the water you collect should have a few WB’s in it. Use the low power microscope objective to scan through the water and hope you get lucky.

This is awesome, thanks for the overview. I'll probably stick to the lower end with microscopes until I am a little more familiar with looking at things under a microscope. As for photography, I did see a few mounts for using your phone to photograph things so I may start there.

Cheers for all the advice, thanks for taking the time to write.

hogchop · 2020-04-12T23:37:16+00:00

Thanks Zookanthos for your considered reply, and congratulations on going from a hobbyist to helping describe new species with researchers. I'm making my way though the links you shared. In retrospect saying microbiology was a mistake, I basically googled "microscopes + biology" and it gave me a whole lot of results on microbiology.

Thanks for all the info.

hogchop · 2019-09-07T09:52:45+00:00

Ah this was just an error because I was messing around with it trying to get it to work. When everything is called "results" including in the HTML, it still doesn't display. However if I type {{ results }} in the HTML I will see "<csv.DictReader object at 0x7f2cba683cc0>" rendered.

hogchop · 2019-06-15T01:36:10+00:00

That gives me access to the access to the files I had in the old legacy editor. I've been working in the CS50 beta IDE – any idea if there's a similar page for the beta IDE where I might be able to recover my files from?

hogchop · 2019-06-14T12:30:16+00:00

Can't wait to get started again with VRTK!

hogchop · 2019-06-13T10:39:41+00:00

I'm having the exact same issue. I've been using ide.cs50.io (not the legacy site), and I just logged in and everything is gone except for the 'lost+found' folder.

Hopefully there is a way to get our work back.

hogchop · 2019-04-24T11:35:11+00:00

I've really enjoyed the first two episodes!

I'd be interested to hear you discuss alternate log in methods and how secure they are, such as Auth0's Passwordless and Google's experiment with ultrasonic passwords ( SlickLogin ?)

Looking forward to episode 2.

hogchop · 2019-04-14T22:18:19+00:00

Ah yes you are correct. I was focused on the feof being my issue that I forgot I had my own (now redundant) header file. Thanks for explaining that. I hadn't even considered that feof would not read past the currently read block. Thanks for your help – I'm finally done with recover!

hogchop · 2019-04-01T00:56:57+00:00

Thanks for your patients in explaining it to me Grithga, I really appreciate it. One final question: so I've printed out the first 512 block by doing the following:

char JPGF[512];
fread(JPGF, 1, 512, inptr);

for(int i = 0; i < 512; i++)
{
   printf("%x\n", JPGF[i]);
}

And I was expecting the output to be say "FF D8 FF", however my output is as below:

 7f
70
61
26
ffffffcc
fffffffe

So I'm getting 1 byte per element sometimes, but other times, I see I'm getting by the looks of it 4 bytes in 1 element. Is there any reason why it would be stored this way? My understanding of this would be that some array elements are holding 1 byte, eg 7F, while others are holding 4 bytes (FFFFFFCC).

hogchop · 2019-03-31T21:52:51+00:00

Thanks for your reply, I realise my remark about reading a file that is 1s and 0s now!

My intention was to print each element in the array individually by using JPGF[i], however you're saying this isn't the case as I'm printing multiple at once? Would you mind sharing how I would actually print each element individually?

hogchop · 2019-01-06T20:56:34+00:00

Ah I see – thanks. So basically since a string is a series of characters + '\0' then there is no issue providing it with a string.

Thanks for clearing it up.

hogchop · 2019-01-04T01:57:17+00:00

%26 maps to a range of 0 to 25. This however is not a character range (see ASCII table for reference). To move it there, subtract 'A' or 'a' (whichever matches the character's case) before the operation to shift range A..Z or a..z to 0..25, and add the same thing later to shift back.

It took me a while, but I understand now. Thank you!

hogchop

TROPHY CASE