Xref: utzoo comp.windows.ms:9762 comp.windows.ms.programmer:1069
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!spool.mu.edu!samsung!rex!rouge!basin04.cacs.usl.edu
From: pcb@basin04.cacs.usl.edu (Peter C. Bahrs)
Newsgroups: comp.windows.ms,comp.windows.ms.programmer
Subject: Re: SDK vs Actor 3.0
Message-ID: <26043@rouge.usl.edu>
Date: 28 Feb 91 17:11:54 GMT
References: <1991Feb27.173751.2152@beau.adp.wisc.edu> <27cc5b87.6199@petunia.CalPoly.EDU>
Sender: anon@rouge.usl.edu
Followup-To: comp.windows.ms
Organization: The Center for Advanced Computer Studies
Lines: 24

In article <27cc5b87.6199@petunia.CalPoly.EDU> kwong@polyslo.CalPoly.EDU (Ka Chin Wong) writes:
>
>
>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.
>
>

I use actor as much as C/SDK and love it. I like the design principles and 
benefits of OO development.  From a theoretical and instructional viewpoint
get it, learn it, and use it. 

But I would not develop a commercial application in actor,yet (my opinion).  
If you are working on prototypes or university assignments, 
fine. There are still some irritating problems when the system encounters
windows errors (what windows app does not crash anyway?).  
And little things like 'a method size is limited'.
Also there is the whole mess about sealing off an application. You need
2 256K files, minimum, for every stand alone application. uggggh.

However, I heard a new release is due out soon!