Apple II Hi-res 10 PRINT *or* Robin vs. Applesoft BASIC 

Heh I remember when I "upgraded" from my VIC-20 to my Apple //c, I was similarly annoyed at how terrible the BASIC editor was on the Apple. It's so terrible compared to the 1977 Commodore editor! I feel your pain and frankly I feel like I missed out on not having a C64 as a kid!! (Hindsight is 20:20) As for that line draw command, it's doing that two pixel thing because of how Apple color works. You need two pixels next to each other to have white when using artifact color. Otherwise one single pixel will be rendered as green or purple. (Or blue or magenta with the pixel shift enabled) That is why games displaying text on a graphics screen on the Apple II must use double pixel fonts in order to even be somewhat legible on a color screen. I'm not sure why your capture device isn't rendering the artifact color properly.... But the single pixel maze would be all purple and green and not look much like a maze if you hook up a real color CRT.

As someone who started computing on the Apple II series, all of your criticisms of Apple's editor are valid and justified. Luckily, you didn't try to SAVE the program only to discover that since you were on a IIc, you could not only NOT use the disk][ (because you didn't load DOS or ProDOS), but there's not even a cassette available. You'd have had to have a serial connection... The II+ and later had "auto-start" ROM, which looked for a disk][ (or a device that looked like a "disk") and would try booting if it found one. Anything before IIc would just spin the disk forever until you Ctrl-Reset. (Reset by itself worked on early Apple IIs, but Apple added Ctrl when it was discovered that users would accidentally hit Reset. Older IIs had no RESB circuit, so to even get a prompt, you HAD to hit Reset after turning the machine on just to assert RESB on the CPU. IN on Apple II is $200. 256 bytes. (IN on C64 ends at like $259, I think...) Monitor will beep speaker if IN is within 8 chars of being filled, and if you bust the input buffer, it "helpfully" CANCELS your input! Not helping is that you pick up all those spaces when you scroll over the program, and those spaces count on IN (really... FPBASIC should have skipped "pretty" printing on Apple for this reason if they really didn't want to use ROM space to give us a decent editor.) Lucky for you that you had a IIc. Its escape handling used the arrow keys or IJKM (as well as the old ABCD from the original Apple II). On the original non-autostart ROM, you not only had to use (and remember which direction!) ABCD for movement, I think Escape didn't latch like on the IIe or later, so you have to press Escape for EACH cursor movement! Even in the updated escape handling, it was still objectively poor. Back in the day, programs like GPLE were used to get a screen editor that wasn't frustrating. Or you could type the program into Appleworks or AppleWriter, but then you'd have to EXEC the thing back in just to run it. Woz definitely was using NTSC tricks for both hires and getting color out of the Apple II. This is why modern equipment bugs out on that "NTSC" signal (TVs back then were like "close enough", but today, it could go blue-screen for any old reason). Woz definitely had to make engineering tradeoffs to avoid requiring a monitor in 1977 as opposed to just using a TV set.

"Nice beaver!" "I just had it stuffed." The naked gun movies all were classics!

I love your style of presentation, definitely captures the “Jim Butterfield” Bits and Bytes vibe.

I remember in school where we had Apple IIs, the teacher gave us one of these extra-long one-line programs to type in, but he mentioned the problem about the extra space causing it to overflow if you tried to edit the program. The solution is to type POKE 33,33 which disables it from adding the extra spaces at the beginning and end of each line of text in the listing, which count against the line length limit if you cursor over them while editing the program. It will still add extra spaces within the program statements, though. So if your one-line program is too long to re-enter it with those included, the only solution is to type it in again!

Fans of this channel already know this, but I'd like to take a second to appreciate the professional titles of these videos. Some kid, or a lesser RU-vidr, would have titled this video something like "Robin DESTROYS Apple" and the thumbnail would have been him holding his arms in an X while looking angry. And I've never figured out why whenever a video is something like "Seven Reasons why blah blah" the thumbnail is almost always the person holding up 7 fingers, or whatever. Anyway, the professionalism of Robin's videos is appreciated.

The one big error Woz made when defining the "OS" for the Apple II was to document the monitor and the basic down to the call addresses of the different functions. These functions calls would then make modifying the system absolutely impossible as 3rd party software would not work any more if one of these function would have moved even a bit. Commodore was wiser to put most fundamental API function in a jump table at the end of the ROM. That way thay could modify the postions of the ROM routines and needed just to adjust the entry in the table. Applications would not need to be modified.

The beaver footage really shows the understatement of "Beavers cut down trees and build dams". There way more effort than is implied.

Regarding your closing remarks: I am very glad you chose that particular style for your videos, regardless of whether that's inspired by someone or your very own idea. I find your videos perfect they way they are and hope you won't ever change much about them.

I was talking to my TV, "Robin, it is line number 12. Just type 12 ". LOL.

oOOOOoo looking forward to the comments on this one. @25:32 Not sure we've ever heard you sigh in frustration before :D

I started on a Apple II in high school. When I got a C64 it was like a breath of fresh air. lol I'm also amazed at the condescending attitude of all those who are willing to constantly pay the "apple tax" because its "better" but they cant give any tangible reasons why. To each their own I guess.

I can feel your pain, Robin... thanks for powering through!

Some of the weirdness of how the keys worked on an Apple //c (and //e) comes from the fact that the original Apple II only had left and right arrow keys, and no delete key. Also, the cursor flashed whatever character was underneath, so you never lost sight of it like in the //e and //c. You’d think Apple would have updated the ROM on the //e and //c to make better use of the additional keys, but nope!

Around 1988, after I had begged my Mom for a C64 for years, and my teachers had told her I had a gift for computing, she toiled, scrimped and saved, and in 1988, I cam home to see a full Apple //c setup with green monitor.. for me! I had to try so hard to contain my disappointment.. she had spent $1295 on this thing, so it had to be better than that $399 "toy" C64.. right? :''( So I dug in on the Apple.. BBSed on the apple, coded on it, made pixel art in Dazzle Draw, and lamented the poor gaming experience... for years. Until I was old enough to buy a well-used Amiga 500 of my own!

I met Jim and emailed with him a couple of times, I think you're definitely carrying the torch, Robin.

Great video Robin, just confirmed I made the correct choice 40 years ago and loved my 64. Besides all my friends had C64's and we were pleased that our high school was a commodore user as well.

Robin: This is a big reason why I do my deep dive videos. I want people who have been off in one archipelago, to see the others. :)

34:23 AppleWin developer here. I know a little about NTSC. Some _monitors_ are "finicky" with the NTSC video signal. A more expensive monitor tends to be better at "image stabilization." It could also be your capture device is not correctly focusing? The way color worked on the Apple 2 was *each byte effectively had a high-bit palette flag* that: 1) used blue/orange instead of green/magenta. 2) shifted those 7 bits over *half a pixel*.

27:19 I almost had a heart attack there when you pressed enter..... I was like "nooooooooo it starts with a 0!!!!"

You can further reduce the size by just using HGR. Also you were getting ILLEGAL QUANTITY ERROR because the screen size is 280x192 meaning 0 is a pixel location therefore you can only go up to 279 for X, you got it correct by using 191 for Y. Now you can further reduce it by eliminating -S before the step token in both X and Y for loops.

Editing a BASIC program on an Apple II was painful back in the day. Thanks for the trip down amnesia lane.

The line drawing is not a bug. I think your capture device is somehow removing the color from the pixels, but to produce white on an Apple II you have to have two pixels side by side. Single pixels are suppose to come out in a different colour. This “artifact colour” is a quirk of the Apple II. To draw a green line, for instance, you’ll see the line appears “dotted” because you have to plot every second pixel on a line, to avoid it turning white.

I totally agree about the BASIC editor. It is terrible and I've been saying it since Junior High when I was forced to use it.

You always do a great job, and I love your videos. BTW, I get a bit of a kick when you make a mistake, or when things are not going well, and you do that little 'Oh....' sound. I've heard it so many times that it will make me smile when you do it, and on this video, you really gave us a great one. Normally I smile a bit when you do, but that one you did on this video made me actually laugh out loud! Keep up the good work and keep chugging along. Your fan base will be there for you.

We had a TI-99 4/A and a series of Atari computers while growing up (400, 1200XL, 65XE), and like most American kids, used Apple IIs at school. As a kid, I definitely thought the Atari was the better machine. 256 colors, player missile graphics, decent audio. I didn’t understand why the schools bought the Apples. But as I grew older, I learned to appreciate the things Apple brought to the table. Those expansion slots were definitely under appreciated by my younger self. But it was a huge difference. And while I could tell that the Atari floppy drive was slower than the Apple II drives, I only understood why after digging deeper into what Woz did. The thing is that both the Atari 8-but and Apple II machines were amazing. I’m glad that I was able to grow up at a time where home computers were interesting. Even though I never had a commodore, I would gladly take the opportunity to play around with one today. Even though these machines are less capable than the smart phones we had years ago, they just bring so much joy when playing with them these days. And they keep getting better too.

Haha, I felt almost telepathic for a second! When you said "size of, uh..." over here I jumped to it and filled in saying "16?" and then you said just one number higher, haha!

You made the right choice. The Apple doesn't even have an interrupt timer.

Lol. I started my computer life on an Apple II, moving to a IIe. I loved it then, but moved to a C64 which was awesome. IMO, C64 was waayyyy better than an Apple. Speaking of the way that your Apple user friends and relatives used to dismiss anything that wasn't Apple, I think that hasn't changed in 2024.

The Apple II editor is aweful. I really don't hate Apple computers, but I do hate the media darling Apple is, and the rewriting of history to their benefit that is so common place.

The obvious answer to easy editing is to have each command on its own line, but I wonder if there's a speed benefit to writing everything into one line of code? I fondly recall the 1- and 2 liner code demos on my apple 2 -- amazed by what could be accomplished with such tight code. I certainly learned a lot from them. :)

As a C64 owner, I once had the "joy" of writing a bunch of Apple ][ code for a High School teacher. My experience was just as bad as what I see you having here. Once I was done, I was absolutely sure I had made the correct choice in purchasing my C64.

To me that Apple II aesthetics remember a sort of medical device, it would fit very well in hospitals and clinics (same for the Macs, always remembered me hospital/medical devices to me, on an aesthetics point of view). The C64 brown aesthetics feel more like a wooden piece of fornitures so it fits better in a living room or in a bedroom. Regarding 16 bits, Amiga 500 has some sort of star wars X-wing aesthetics feeling to me, custom chips, multitasking, even a single A500 with 512k was super powerful and could serve a lot of things, the Atari ST was a cheap and bare bones 68000 computer, with its diagonal lines and strange colour tone it was more like a dirt cheap and fragile Tie Fighter. BTW now you could do the same in c128 Basic using draw command (draw color, x, y) Edit: just continuing on aesthetics: Commodore Pets with their black keys and plain white cases, scream 2001 A Space Odissey from every pore, same perhaps with the Vic20 (or perhaps Vic20 is more Buck Rogers in 25th Century, somewhat) Returning to X-Wing vs Tie Fighter comparison, it could be applied also to C64D,C128 vs Spectrum, Plus4 and C16

This is some quality Canadian content!

Oh my heck, having no insert feature and also having to "cursor along" to the end of the line would drive me NUTS!

I was born 1979.. Each of my friends had a different computer. C64, MSX, ZX Spectrum, Amiga, IBM PC (yes, nearly all my friends households had a computer... I know how to pick 'em I guess). We had a TRS-80 model I (already outdated) but we made the quantum leap to an A500. I can't remember ever being talked to in a condescending way, or doing that to my friends though! I had every right to because the Amiga kicked those C64, MSX, IBM PC and ZX Spectrums asses! ;). It was a fun period in home computing with so many different types of computer. Eventually everyone got either an IBM compatible or an Amiga in the early 90ies. I went to a local computer user every month, and there were IBM compatible users and Amiga users. I do remember IBM compatible owners there talking down the Amiga a lot... At first they had no real ammo, but as we neared 1994 they did... Bought a PC soon after, kept the Amiga, sold the Amiga, sold the PC and bought a Mac early 2000, and in recent year bought back 5 Amiga's ;)

I always found Apples to be awkward to use, still do! You are not wrong, I started on a pet 2001, I was spoilt from day one with on screen editing. No other home computer ever improved upon that, I would think...why didn't they do it like the pet!!!

I really enjoy the format and content of your videos, and this was no exception!

When I was a kid in the '80s I would hang around computer stores and I would try the Apple IIs, now I know why I never "got it". The staff weren't inclined to help a kid with no money I guess.

Editing a line would drive me crazy. I moved from a Vic 20 to an Amstrad CPC 464 and that was wierd. It had a similar operation but implemented in a much better way. You moved a copy cursor up to the line you want to edit, but your real cursor remained in place. You then press the copy key and it copies what is under the copy cursor to the real cursor. This ended up being really powerful as you could copy parts from many places on the screen to make your new line. So to edit one value like you were attempting there, you'd move the copy cursor up, hit copy key a bunch of times constructing a version of the characters at the real cursor, then at the point you want a new value, just type it in, move the copy cursor past the old value, then continue pressing copy to copy the rest of the line.

I'm VERY glad I was all Commodore, and school was PETs and BBCs. If we'd had those at school I probably wouldn't have ever got into computers.

Some people in here saying that apple had a terrible editor. It did not have one at all. Do you want it to change a semicolon or edit some text, you had to re-enter the entire line

I enjoyed the B-roll (beaver roll?). I'm glad I learnt BASIC on the C64 with its abbreviations and easier editing! As you were trying it out, I did wonder if changing the size would give you a faster output - 7/8 would be much closer to the original C64 PRINT 10 anyway. The penultimate version of the edited program was over 6 lines/240 characters - so assuming a 255-byte input buffer that could explain the issue you were having. I'm not going to suggest rewriting the credits program in Applesoft BASIC - it's not worth your frustration!

pretty funny having the comments about Jim Butterfield at the end of an Apple video

The sound of the Apple floppy drives still brings back happy memories of typing in programs from Nibble magazine, and playing Lode Runner, Choplifter, and Ultima 3! 😅

The Apple IIc startup is quite user friendly for people not so familiar with computers: most people want to boot up a program from a disk (or at least get to the point where then can run one), and if you forget to close the drive door the system makes it clear that something's gone wrong. This comes at the cost of making it slightly more difficult new users wanting to start up _without_ DOS loaded, but that's a pretty small segment of the user population. The rest of your comments about the Apple II's problems are pretty much fair, though it's worth remembering that this is one of the very first consumer computers ever (and the first with a composite colour display and relatively high resolution graphics), and a machine whose design predates the Commodore 64 by five years. Commodore more or less invented the microcomputer BASIC screen editor in 1977 but released the PET months after the Apple II was released, so unlike other companies Apple wasn't in a position to learn from that. (I suppose Apple could have improved their screen editor along with the release of Applesoft BASIC, but it's also fair to consider that perhaps they didn't want to deal with the BIOS compatibility issues that might bring.) That weird fading you're seeing in your capture is due to issues with where the capture device is sampling the signal and how it's interpreting colour. (Colour and small pixels--more than about 150 to 200 across, aren't actually distinguishable in NTSC.) If you want a nice solid image, try a monochrome capture (one that actually reads it as a black-and-white signal, not one that reads colour and converts). Or just use a monochrome monitor.

The Apple II never ceases to amaze me. If you've ever tried doing graphics routines in assembly on it you'd know how insane the video memory addressing is (in high res mode anyway.) Yet you can easily get BASIC to calculate sine waves on a machine that has no floating point CPU

44:45 - It's 2024, where is our super advanced version of Smell-O-Vision? I want that burning electronics smell when a RIFA capacitor explodes, gosh darn it! Also, I feel so spoiled thanks to the Commodore screen editor. #ThankYouCommodoreEngineers

We used to have a beaver on the back 80 of our farm. He built a huge lodge. Look just like you would see in the movies etc. all the tree stumps looked like they were chopped down with a hatchet.

The first few minutes played like a modern/weird "Hinterland Who's Who" short/PSA. 😁

Actually you *can* insert text. The trick is to cursor right over the initial text as you've done so far. But when you reach the point where you want to add anything, hit Escape, then move the cursor somewhere else on the screen (above, below, doesn't matter.) At this point hit the space bar to exit Escape mode, type what you want, then hit Escape again. Move the cursor back to where you were in the code, hit the space bar to exit Escape mode, cursor right over everything else.

I was white knuckle afraid the whole time seeing so many things stuffed into a single line. New line numbers for almost everything here. Maybe two variables assigned together, or two print statements if I intended a double space. That way when (not if) I made a mistake it was easier to retype the offending line. I knew about the escape and cursor thing but I retyped anyway to be sure.

12:57 The spaces are added only in front and at the end of a token. Tokens are the BASIC keywords and the operators +,-,*,/,^. No space s are added at punctuations :,()[] and names (variable, functions). It is a very simple scheme and very consistent. It is annoyingly simple. What's even more annoying is that it adds 4 spaces on each line break if the window size id wider than 33 characters. This adds so many blanks that a BASIC line might exceed the size of the input buffer (255 bytes) and it adds these blanks even if the line break hapeen inside a string litteral. So if you copy to the buffer with -> you will add these lanks into the litteral. Solution POKE33,33 to reduce the width of the input window so that LIST does not add these blanks.

Well, this is why normally each statement would be on its own line, and if you numbered your lines by 10s there'd be room to add additional lines in between them. Still pretty neat for a computer designed in 1977.

Nice intro, had to watch it twice

Best day was when I showed my Apple friends digitized music/speech on my 64. Hated Apple basic so much I refused to use it in the one and only computer class I took in HS, turned in my printouts in C64 basic, the teacher was not pleased. Apples back in the day were just like trying to use Macs with only one mouse button. Super annoying and unintuitive.

Another great video! Thanks.

That glitching looks like compression artifacts from your capture device. The Apple //c's video could be a contributing cause. Your Apple //c is probably working correctly. The video output from the Apple II series can jitter at times, and while the Apple //c is less prone to jittering than say the Apple ][ Plus, it can still do it. (This jittering may be more apparent now that we're using devices with digital input stages, compared to back in the day when we used analog CRTs.)

The lack of a backspace key on even modern Macs still drives me bonkers whenever I have to use one.

Also, one note: once I learned about EXEC I stopped using the applesoft editor and used instead ProTERM as my text editor text files, which made it a code -> run option that didn't suck. It wasn't ideal but it worked OK enough back then. We are so spoiled now! No disk swapping or rebooting to compile anything and run anything. Just instant.

Came for the apple, stayed for the beaver

I think Woz was used to using terminals or teleprinters, and he was stuck in the "I have to do it the old way" mentality. Either that, or Woz was so good that he always typed everything correctly the first time, so he saw no need for an editor.

I never used Applesoft's Basic, and I guess I was lucky. That abysmally bad editor would drive me crazy.

Great video. I had a IIc back when they were new and I currently have one, but not the same one. I'm still looking for a Koala pad w/software for it. Thanks for all your work you put into your videos. You are one of the best.

LOL about that mysterious line 12 you had there for a minute! 😅

All those old machines worked differently with different quirks so there's nothing surprising for me. The base default was BASIC with a few OS-ish commands. Whether or not they had anything like an "editor" for BASIC, and if they did, how it works, varied all over the place. My first Commodore machine was the Amiga 1000. Before that I used earlier Apple 2s, TRS-80 Model 1 & Model 3, and original ZX Spectrum. Occasionally something rare and exotic, but never any PET, VIC-20, or C64.

Uhh, this Apple editor is really a pain in the a**. I now like my C64 editor much more. Thank you. 😊 And about your journey, I like your videos and the way you present very much. Please keep it. 😊

The TI-99 owners were jealous; the Apple owners were snobs.

Awesome video 🎉

Makes me appreciate the nice screen editor on my 8-bit Atari computer.

The confusing bit about the editing within Applesoft BASIC is that it involves two different modes -- input mode and cursor movement. The addition of spaces in listing can be a blessing and curse -- as you discovered, when you have program lines that are near the limit it's a curse (to work with these, you'll have to keep toggling between cursor move and edit mode). Inserting text could be handled by toggling to cursor move to move cursor elsewhere (possibly even text that you might want to copy), switch to enter mode to type or cursor past text you want to copy, then toggle to cursor move mode to position to continue, toggle back to enter mode to scan past the rest of the line. Blanks are ignored (unless part of a string constant or REM) -- so you can enter "P R I N T" and still end up with "PRINT" (assuming that there wasn't text prior to it that might affect the parser. This also meant you can't use space to indent code. It also means you can't use space to affect the parsing -- for example if you try to enter "IF A THEN PRINT A" you don't get the expected result -- you end up with "IF AT HEN PRINT A". To get the intended result you have to enter it as "IF(A)THEN PRINT A"

I found this video very fun. All your videos are. I love beavers too. I’m a PC guy. But my stepfather have been using a Mac since the late 80’s. I’ve been using iPhone since 2010 though. I’m watching this video on one

Last time I saw a Beaver like Wood in media was at least 20 years ago... ... lol. So what you're saying is that BASIC on a 1 line calculator is easier to control, lol. Though it was lacking a lot of features, VIC20/C64 BASIC were a lot easier to control compared to some other brands.

HPLOT can draw lines as well as plot points. e.g HPLOT x,y TO x1, y1 HPLOT has another variant HPLOT TO x,y that plots a line from the previous plotted point to specified point. you can significantly speed it up by plotting lines rather than points.

I think the reason for the thick lines drawn by HPLOT is the "artifact" color that Apple used. Single pixel diagonal lines would appear as alternating colors on a real CRT. It looks like your capture device is interpreting the signal as monochrome, so it's not apparent here. Try your program with HCOLOR = 1 or 2 or 5 or 6 to see a real mess. HGR in color is really only 140 x 192.

My first computer was the TI-994/a. Now get off my lawn!!

One of the reasons I didn't care for Apple machines back in the day was because they DID feel professional. I know that sounds weird, but the Apple II's at every school I went to felt clunky and limited, like they were only capable of the kind of boring educational shit your parents and teachers wanted you to do. They didn't feel hackable. And although I never owned one, I have the distinct feeling that if I did, it wouldn't have felt like it was mine. My C64 WAS mine, and I knew it. It booted right up into Commodore Basic, one of the most hackable environments ever to run on a personal computer. I could do pretty much anything I wanted with it. It actually FELT like a home computer, not some beige box in a computer lab at school. Using an Apple II for gaming felt like drag-racing a minivan: even if it sort of worked, it just didn't seem that much fun. Now I am not claiming that any of this is fact. I know people played games on the Apple IIe, and not just Oregon Trail (which I am aware was very popular) and other edutainment-type stuff. I know people had them in their homes and loved them. They just personally were not a pleasant experience for me.

To be negative in the retro computing and gaming world just seems so unnecessary. Thanks for your videos and what you contribute to the community.

OK, but B-roll is really just good when it's related to what you're talking about.

I read the title as "hires" as in "gave someone a job" instead of short hand for high resolution. "I wonder how much Apple II is paying 10 Print?"

10:15 To add a nicer way to get back to text mode add an ONERR to trap Control-C

Heheh, I liked your segment about Jim and making your style of videoing yourself as somewhat of an homage to him. Also, cool that you released this on Independence Day here in the USA (though I understand if you really gave no thought of that, ha).

43:58 The commodore demo at the end had thick lines in the maze (because they were characters and not drawn lines)... so it would be totally ok to use the hplot on the //c which produces a thick line as well....

Your one line maze program runs perfectly on the Atari. I only had to change the character codes.

as a kid I had a TI994/a and was super jealous of my neighbors who had Commodore64's

Thank you for this great video where I discover how to edit a BASIC program on an Apple //. Accustomed since my childhood to using the full-page editor of the Commodore 8bits, I would have been unable to get by on this machine. But in fact, this program is not really a one-liner! On the other hand, this 10 PRINT in high resolution graphics mode actually did it on a Commodore C128D (international AZERTY version) because on the 80col display, it does not take up more than one line (a line 10): 10 GRAPHIC1:DO:CHAR1,40*RND(1),25*RND(1),CHR$(205+2*(RND(1)

I sympathise with the editing - it's one of the few nicer features of the C64's OS and BASIC. the Acorn machines do not do full screen editing - but I think they're an improvement on the Apple - instead they have a copy key with duplicates whatever is under the cursor into the present input line - so to edit a line you copy it into the active line, then edit it there. Still a bit unwieldy but not actually confusing like this.

I appreciate that the Apple II was not cheaper than the C64, otherwise I could have owned one and never learned programming.

Please note..the fact you noted the beaver has been noted. As the saying goes ..the Apple II succeeded despite Jobs' tireless efforts.

Have you ever used a BBC Micro? They have odd line editing, using a _copy_ key and the cursor keys to copy parts of code and modify it. At least with that, it’s possible to insert code.

Hmm, you know, I wonder where the original Commodore company would be with their product lines nowadays if they had stayed in business long and strong. Dang, I miss them!

Also the way that the graphics work in the apple is that sections of the screen are split apart in memory for some reason. I tried figuring out how to do high resolution Graphics in assembly and simply gave up because I couldn't figure out how to calculate where to put stuff in memory just to do a single line

8:12 Yes, 150 characters.

I like everything about this video

16:50 as said POKE 33,33 will avoid most of the added whitspaces that where added.

I remember how people would hate others that had different computers. I got an Apple II clone and was hated by everyone. Lol!! I didn't care, and the strangeness of the editor, you just got used to it. I collect many different computers and like each one for different reasons. I'm a hardware guy since the start, that's why I got the Apple as it was easy to get inside and make your own designs. Thanks for sharing

Was the apple IIc sold in Europe? Having a hard time finding one.

Nooo. That's crazy! I don't remember navigating that BS back in the day...

That music bed for the Jim Butterfield tape audio at the end is one of those weird coincidences in life for me. In the late 1990s, I worked at a local TV station that used the music package that song was part of as their news branding, and that particular song was our primary sports music at the time

To optimize the program you could try to move as much calculations outside R -loop as possible. Something like this: D=RND(1) < .5 (D is 0 or 1) Z=D * S + Y (Z is Y if D is 0; otherwise S + Y) D= -(D * 2 - 1) (D is -1 or 1) FOR R=0 TO S-1 HPLOT X + R,Z + D * R NEXT This should speed up the execution at least with larger values of S. DISCLAIMER: hope I got the sign of D right.