Xref: utzoo comp.windows.ms:9745 comp.windows.ms.programmer:1057
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!zaphod.mps.ohio-state.edu!usc!jarthur!petunia!news
From: kwong@polyslo.CalPoly.EDU (Ka Chin Wong)
Newsgroups: comp.windows.ms,comp.windows.ms.programmer
Subject: Re: SDK vs Actor 3.0
Message-ID: <27cc5b87.6199@petunia.CalPoly.EDU>
Date: 28 Feb 91 01:23:19 GMT
References: <1991Feb27.173751.2152@beau.adp.wisc.edu>
Organization: Cal Poly State Univ,CSC Dept,San Luis Obispo,CA 93407
Lines: 22



By all means choose Actor.  An excellent object oriented programming
language.  With Actor, you don't need SDK to build Windows application.
You learn Actor and at the same time you learn OOP.

In a way, Actor is very similar to Smalltalk (Programming Environment).
Actually, it is like a combination of LISP, Smalltalk, C, and Pascal,
but with a simple, power (and at the same time easy to read) syntax.

The only drawback I can think of is a relative small Actor programming
community.  When you are stuck, you may have a hard time find local help.

The Whitewater group does have a BBS and a forum on Compuserve though.
However, the BBS is more benifical to those who live in Chicago area,
and Compuserve costs.

There isn't a newsgroup like comp.lang.actor there yet; however, if you
have questions that I may know, feel free to drop me a mail.


Rick