Coding Train Live: Riding the Oregon Trail 1

0:00 Waiting to Start
6:36 Hello everyone!
23:50 Recent announcements in Discord
25:17 New shorts
30:41 Passengers Showcases
35:03 Design System International Coding Train website case study
45:58 Apple ][ 3D cube challenge
51:43 Comments on Apple ][ 3D cube challenge
1:02:26 My Nebula class What is Code?
1:04:15 CuriosityStream + Nebula bundle
1:27:49 Play The Oregon Trail game
2:05:25 Oh No!
2:08:47 Congratulations! You have made it to Oregon

Links Discussed:
New Shorts
Featured Showcases:
Coding Train website case study:

#p5js #oregontrail #game

[therexbellator]

I'm a little younger than Daniel but I envy the pure joy and nonstop excitement he exudes as he's streaming or in his instructional videos. He seems like a happy man. We should all be so lucky!

[eugenetswong]

Everybody, thank you for your contributions in the comment section!

Dan, thank you for your videos.

[doug]

I am definitely entertained by you and your videos! You do amazing work.

[CriticalMonkey]

Oooh, I've been watching for years but have never actually watched a full livestream. I love the calm and comfy energy you bring, and it's great to see you so excited to be streaming again. I've got the followup stream queued up, can't wait to see your recreation.

[andrewdunbar]

Rotating from the previously rotated version will not speed it up but it will accumulate floating point error. I did all this in BASIC on the ZX Spectrum 35+ years ago.

It might be faster in Integer BASIC than in AppleSoft BASIC.

Instead of using 360 degrees I used to use Radians. I probably didn't even know it was called radians at the time. I divided PI (or maybe it was 2PI or PI/2) into 256 subdivisons in a lookup table. 256 is closeish to 360 and is the number of distinct integers a byte can hold so efficient on 8-bit computers and even moreso in assembly.

Of course if you do an assembly version and draw the lines using your own code rather than calling into the ROM or BASIC routines you have to dive by 7 because of the strange Apple ][ display memory layout. That's slower than dividing by 8 that would be necessary on most old machines which you can do by right-shifting 3 bits. Then again you can do division by seven with a lookup table too keeping in mind that you only need to perform it on a restricted range of input integer values.

[Tentin.Quarantino]

1:36:38

Feels like an Eminem rap.

Weather’s cool, health good, pace is steady
Rations filling, heart is willing and he’s armed and ready, to ride on.

[bokkenka]

“This, milord, is my family's axe. We have owned it for almost nine hundred years, see. Of course, sometimes it needed a new blade. And sometimes it has required a new handle, new designs on the metalwork, a little refreshing of the ornamentation . . . but is this not the nine hundred-year-old axe of my family? And because it has changed gently over time, it is still a pretty good axe, y'know. Pretty good.” --The Low King, 'The Fifth Elephant' by Terry Pratchett

[nelbr]

the reason your simpler example is changing colors (58:35) is because in HGR, the only way to get white is to draw 2 adjacent pixels on the same line. Otherwise, the actual color is given by the x position (odd is green and even is magenta). Which is why basic only plots green on odd coordinates when using hcolor=1 and magenta on even coordinates when using hcolor=2. If you use hcolor=3, which is supposed to be white, it will plot on both odd and even coordinates, but you only get white if you have 2 adjacent pixels. Otherwise you get either green or magenta according to the x coordinate, which is what you see in your code.

[dinyodonchev]

Every single video is like the best of two worlds: coding and subconscious, hardly intentional, "can't help but laugh while talking" stand up comedy thing :D