9 comments

[ 2.8 ms ] story [ 28.8 ms ] thread
Pointless, time waste, unnecessary.

I love it!

Me too, all the while knowing that Retro Computing may give TFW "Your friend goes steampunk"--carrying a thing too far.

I can't seem to find an NRuby repo. I suppose the 256 object limit was too impractical, even given the impractical premise. There is one for the presenter app[0] in 6502 assembly.

[0] https://github.com/justcolin/fruity_asm_presenter

I suppose coincidentally I just got my old IIc from my dad. Pretty fun. Just kind of working out how best to backup the disks I got, so the journey is just beginning.

Maybe eventually I'll get around to making a game or doing something weird like this. Great talk.

Design a byte code like Sweet 16 or UCSD Pascal, and compile Ruby to that.

It would certainly be more space/time efficient than Manx Aztec C, which was terrible.

https://en.wikipedia.org/wiki/Aztec_C

Hilarious discussion on the talk page -- I used Aztec C but I have not vanished yet:

https://en.wikipedia.org/wiki/Talk:Aztec_C#WHO_vanished%3F

I had a Legend Industries 128KDE memory expansion card on my Apple ][+ -- that would help!

Washington Apple PI, January 1982, p. 12, "I CAN'T REMEMBER HOW MUCH MEMORY I HAVE" by David Morganstein:

https://www.wap.org/journal/showcase/washingtonapplepijourna...

.NET/MSIL is actually somewhat reasonable. I'm working on a loader+interpreter for the //e right now.
This is very cool. I wonder how much of Ruby was actually implemented. Obviously a few things work, but I'm pretty sure you'd never get regex and hashtables and all the other piles of complex stuff in the standard lib working under those constraints.