🚀 go-pugleaf

In article <39340@apple.Apple.COM> mjohnson@Apple.COM (Mark B. Johnson) writes:
>In article <32015@brunix.UUCP> omh@cs.brown.edu (Owen M. Hartnett) writes:
>>
>>Here's another Apple misteak!  Before pulling the plug on good ole
>>Macintalk, Apple should instead be rolling out its replacement.  
>>Apple has been "committed to providing the developer community with
>>an array of speech technologies" for several years now but has done
>>*nothing!*  The fact that this has been cut off without providing for
>>a replacement seems to indicate quite strongly that there is nothing
>>in the channel now and won't be for some time.
>>
>Apple is not "pulling the plug" on MacinTalk--it has not been supported
>for years.  

Au contraire, unsupported is a little different than "broken."

>One must also realize that in order to avoid the same mistake
>that we have in this case, Apple is not just going to provide some interim
>sound solution which will again break after another system software release.
>It is important for Apple, for developers, and most of all the users that
>we provide a SOLUTION to the problem, not just another problem.  Unfortunately,
>that solution takes a little longer than we would all like.

I'll make you a deal: if you can state that Apple has at least one
engineer actively working on a Macintalk replacement (active being 
at least one week out of three months), I'll shuddap.  It doesn't even
have to be a Macintalk replacement, just something that will be a 
functional substitute.  

I'm not asking you for a product announcement, merely if research is
being done in this area.

I realize that it takes long to develop new technologies, and that priorities
have to be made, but, IMHO, valid speech technology is more in keeping
with the original spirit of the Macintosh than many of the features of
System 7.0.

-Owen

Owen Hartnett				omh@cs.brown.edu.CSNET
Brown University Computer Science	omh@cs.brown.edu
					uunet!brunix!omh
"Don't wait up for me tonight because I won't be home for a month."