ForthNet@willett.UUCP (ForthNet articles from GEnie) (01/05/90)
Category 2, Topic 4 Message 20 Sat Dec 30, 1989 F.SERGEANT [Frank] at 15:45 CST MB> Several attempts have been made to build the "computer MB> running Forth" that you describe: The Jupiter Ace, MB> the Epson Valdocs system, and the Canon Cat. All failed ... If I had no other exposure to Forth than working with ValDocs and knowing it was written in Forth, I would RANT against Forth. I would badmouth Forth every chance I got. If I were a project manager it would be my POLICY never to use Forth under any circumstances. I think ValDocs did a great deal of harm to Forth, and hopefully to Epson as well. -- Frank ----- This message came from GEnie via willett through a semi-automated program. Report problems to: 'uunet!willett!dwp' or 'willett!dwp@gateway.sei.cmu.edu'
ForthNet@willett.UUCP (ForthNet articles from GEnie) (01/07/90)
Category 2, Topic 4 Message 22 Sat Jan 06, 1990 GARY-S at 10:46 EST FF>to use Forth under any circumstances. I think ValDocs did a great deal of FF>harm to Forth, and hopefully to Epson as well. -- Frank If Ron Braithwaite is still connected and reading these messages, I would like to recommend you post a message similar to the one you and Bill posted to BIX a cupla years ago. I will not presume to recreate that message, but all who blame ValDocs and Rising Star for anti-Forthism really need an insiders perspective. I first talked to Ron when he was associated with Rising Star, and knew there were problems. Not till I later read the aforementioned article(s) on BIX did I realize how deep those problems ran. I will just say this - Forth was not the root cause of ValDocs abyssmal performance, and neither were the dedicated (and professional) programmers working on the project. That doesn't leave many places to look... but you need a view from within. ----- This message came from GEnie via willett through a semi-automated program. Report problems to: 'uunet!willett!dwp' or 'willett!dwp@gateway.sei.cmu.edu'