00:00:00 --- log: started retro/10.08.30 00:09:26 --- quit: docl (Ping timeout: 264 seconds) 02:24:23 --- quit: roarde (Quit: Leaving.) 05:19:54 --- join: docl (~luke@97-120-241-117.ptld.qwest.net) joined #retro 07:29:01 --- quit: crc (Ping timeout: 265 seconds) 07:30:33 --- join: crc (~charlesch@184.77.185.20) joined #retro 08:01:02 --- quit: docl (Ping timeout: 264 seconds) 08:37:09 --- join: roarde (~sixforty@pdpc/supporter/active/sixforty) joined #retro 10:18:26 --- join: IdleOrange (~IdleOrang@host217-42-207-150.range217-42.btcentralplus.com) joined #retro 10:18:34 --- part: IdleOrange left #retro 10:51:53 --- join: IdleOrange (~IdleOrang@host217-42-207-150.range217-42.btcentralplus.com) joined #retro 10:51:56 --- part: IdleOrange left #retro 11:19:28 --- nick: roarde -> sixforty 11:19:34 --- nick: sixforty -> roarde 12:13:47 Except for 10.0, which 10.x so far might come to be considered the most historically important? 12:15:13 or relace "historically important" with "canonical" 12:15:32 hrm . . s/relace/replace 12:20:41 what about 10.3.1 for metacompile, or 10.4 for vocab? Or has vocab gone a different direction since .4? 13:16:02 --- nick: roarde -> roarde_ 13:31:46 --- nick: roarde_ -> roarde 13:37:36 vocabs are being completely redone for 10.6 13:43:24 I'd suggest 10.5, which brought networking and file i/o, as well as a new threading model 14:15:39 --- nick: roarde -> roarde_ 14:17:24 didn't notice I was scrolled up. thanks. 14:42:56 --- nick: roarde_ -> roarde 14:45:45 After studying a little more, looks like the best retro for relatively long-term use would probably be a soon-forthcoming 10.6.x, no? 15:39:07 yes 15:39:33 I think the code is stable enough, but haven't had a chance to update docs, libs, etc for the changes 15:40:52 * roarde nods. Timing happens to be about right for me, too. 15:41:16 How will I know when this is ready? 15:41:20 never 15:41:30 crc always changes shit 15:41:33 and breaks old code 15:42:18 :P 15:42:24 yeah, I know never. And I grok breaks old code. I'm contemplating 8-20 months with the same retro, tho. 15:44:00 took me a long time to understand I'm looking at a few guys' (well-done) hobby. I'll deal with it; thanks for providing the view. 15:49:45 retro's still your best bet :) 15:51:39 Yeah, I've discovered that. Still pining for colorforth 'cos I'm interested in the chips. But since it can't be hosted on my machine, I'll have to pine on. 15:52:34 foucist: 10.0 - 10.5 were mostly compatible; 10.6 on the other hand... 15:53:01 roarde: likely mid september. I'll announce here, the mailing list, and freshmeat.net when it's ready 15:53:12 I'd probably like colorforth more, but since I'll probably want help, retro's the better idea anyway. More powerful out-of-the-box. 15:53:39 thanks, crc. 15:55:12 Starting with latest in repo shouldn't cause regrets, then? 15:55:19 not at all 15:55:47 baring any bugs I may find, I consider the version in the repo to be release quality 15:56:27 it's unlikely to see any significant changes before release. 16:18:57 thanks for the info, nite 16:19:08 --- quit: roarde (Quit: Leaving.) 17:39:56 --- join: docl (~luke@97-120-241-117.ptld.qwest.net) joined #retro 17:46:07 docl: http://gist.github.com/556729 is my latest code for parable 18:27:25 --- quit: yiyus_ (Ping timeout: 240 seconds) 18:31:35 --- join: yiyus_ (1242712427@je.je.je) joined #retro 20:12:15 aren't the forthchips cheap? 20:12:18 do you guys have forthchips? 20:12:24 i mean it's for sale right now 21:35:48 --- quit: crc (Ping timeout: 265 seconds) 21:36:37 --- join: crc (~charlesch@184.77.185.20) joined #retro 23:59:59 --- log: ended retro/10.08.30