Received: by 10.180.101.9 with SMTP id fc9mr555937wib.3.1348945226146; Sat, 29 Sep 2012 12:00:26 -0700 (PDT) MIME-Version: 1.0 Path: q11ni99631245wiw.1!nntp.google.com!goblin1!goblin3!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: comp.lang.forth Subject: Re: If I were a forth programmer, by gavino the unix guru Date: Sat, 29 Sep 2012 15:03:42 -0400 Organization: Aioe.org NNTP Server Lines: 39 Message-ID: References: <2a119528-07c8-4d98-beb4-51f3f1c8b6e0@googlegroups.com> NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org X-Complaints-To: abuse@aioe.org X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.2001 X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Microsoft Outlook Express 6.00.2800.2001 X-Priority: 3 X-MSMail-Priority: Normal "gavino_himself" wrote in message news:2a119528-07c8-4d98-beb4-51f3f1c8b6e0@googlegroups.com... > I think you just throw "forth" into the mix so people won't complain about you being OT (off-topic, i.e., not Forth related). > ok I have my archlinux machine or hek even bsd and > attached is nice 8 disk array in raid 10 software raid > for nice fast access to 1T of disk space. There are 8 gig > of ram and 4 3.8ghz amd64 cpu on the box. I add gforth. LISD - lost in stupid details. I.e., why is any of this relevant? > Now I want to make a dynamic website liek craigslsit but > with a postit board liek live journal and a chat like irc but > done in html. How would a real forth programmer go about > accomplishing this? How would a real unix programmer go about accomplishing this? (I meant you, specifically ... ) In the broader sense, what makes you think the solution would be any different? Yes, the code would be different and the implementation could be different, but the task that must be solved is the same. You'd go about solving the implementation of that task the same way, but with the tools that are available. Of course, the "same way" is not one way, but one of a few methods you might use to solve the problem. Ms. Rather suggested a backfill approach. That approach can result in many lingering compatibility, maintenance, and inefficiency problems. Another method is straight forward all-at-once, from-scratch. That approach takes much longer to implement. Rod Pemberton