from Hacker News

Apple II graphics: More than you wanted to know

by GavinAnderegg on 6/28/24, 1:14 PM with 66 comments

• by thought_alarm on 6/28/24, 5:09 PM

  > "Randomly reading from various memory addresses might give the modern programmer some concern about security holes, maybe somehow reading leftover data on the bus an application shouldn't be able to see. On the Apple II, there is no protected memory at all though, so don't worry about it!"

  Funnily enough, protected memory (sort of) arrived with the Apple III a couple of years later in 1980 and it was met with complete disdain from the developer community ("Stop trying to control my life, Apple!").

  Apple III ROM, hardware, and kernel memory wasn't meant to be directly accessible from the application's address space. The purpose was to increase system stability and to provide a backward-compatible path for future hardware upgrades, but most users and developers didn't see the point and found ways around the restrictions.

  Later, more-successful systems used a kinder, gentler approach (please use the provided firmware/bios interfaces please).

• by PaulHoule on 6/28/24, 3:40 PM

  The first generation of home computers used discrete components for the display controller which is crazy expensive because you need lots of counters, comparators, wide data paths, etc which adds up to a lot of parts.

  Second generation machines line the VIC-20 and TRS-80 Color Computer used ASICs for the display controller. Apple though the ][ was on borrowed time and has no idea how long it would last so they were slow to come out with the ][e which was cost-reduced.

• by deater on 6/28/24, 4:31 PM

  the discrete hardware part of the Apple II is fascinating window into 1970s hobbyist electronics sometimes. In the flashing text mode, you might think the flashing text (also used for the cursor) is done in software or something. But no, it's a 555 timer gating off the video signal for that particular character.

• by robterrell on 6/28/24, 4:24 PM

  This might be a good moment to drop a thing I made last year but never shared the link for. It's a bitmap editor that outputs Apple ][ shape tables.

  https://robterrell.github.io/shape_table_maker/shape_draw.ht...

  Apple ][ shape tables were a rarely-used vector drawing technique -- rarely used because they were fairly slow to render and there wasn't great tooling for making them. High level of difficulty plus poor results... it was almost as easy to write blitting code, even with the odd Apple ][ video memory layout, so most games ended up doing that instead.

  Anyway, if you are curious about shape tables, here's a thing for you.

• by TMWNN on 6/28/24, 10:02 PM

  Woz is one of the greatest engineers of the 20th century, and the Apple II demonstrates his talent. But his brilliance at simplifying things always straddles the line between optimized and overoptimized. The Disk II might be his greatest feat at doing more with less, while the video circuitry falls just into overoptimization, given the color fringing, NTSC dependence for color, and lack of lowercase. Integer BASIC is somewhere in the middle; great performance (especially given (or maybe because) Woz knew nothing about mainstream BASIC), but the code is so tightly written that it was easier for Apple to license Microsoft BASIC than to add floating-point code to Woz's work.

• by deater on 6/28/24, 3:50 PM

  if you're excited about Apple II graphics, and also about the new Riven remake, but you don't have the VR hardware for Riven, you can try out the recently released Riven-for-Apple-II subset: http://deater.net/weave/vmwprod/riven/

• by whoopdedo on 6/28/24, 3:51 PM

  > I'm going to break with my usual habit of ][ and use "Apple II" for the rest of the post.

  It very slightly bothered me that "][plus" was typeset before this, but it was "IIe" and not "//e".

• by ffhhj on 6/29/24, 3:37 AM

  > Many vintage computers are defined by their fonts.

  But the article doesn't mention my favorite ASCII table ever, known as the "running man character set":

  http://www.lazilong.com/apple_ii/a2font/readme.html

  It includes open and closed apples, sand clock, and elements to build GUI's: windows, tabs, scrollbars, and even a pointer!

• by PaulHoule on 6/28/24, 6:10 PM

  It hurts so much to see how slow that dragon head is animated in that Ultima intro. I remember a lot of really slow updating in games for the ][.

• by Bluecobra on 6/28/24, 9:47 PM

  > Unfortunately, the Apple II doesn’t give the programmer any ability to know where in its cycle the video scanner is at any given time.

  So there is no way to race the beam on an Apple II like an Atari 2600/VCS can?

• by Dwedit on 6/28/24, 6:42 PM

  Glorious 7-bit graphics.

• by pazimzadeh on 6/28/24, 5:14 PM

  Relevant:

  How Steve Wozniak Brought Color to Personal Computers https://www.youtube.com/watch?v=uCRijF7lxzI

• by pavlov on 6/28/24, 4:13 PM

  > "Randomly reading from various memory addresses might give the modern programmer some concern about security holes, maybe somehow reading leftover data on the bus an application shouldn't be able to see. On the Apple II, there is no protected memory at all though, so don't worry about it! Loosen up! The hacker doesn't need a security hole if there's no security."

  I miss computers that didn't have the capability to send all my important data to an unknown address in Belarus in the blink of an eye.

  Maybe someone could design a modern desktop operating system whose outgoing network requests are batched and processed once a day, so you can look through the batch before letting it out. This would of course mean that applications must be designed to be extremely thrifty about what data they want to send, or users would simply ban them for making large opaque requests. No more telemetry, no more ad profile updates, etc.