🚀 go-pugleaf

In article <1195@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes:
>
>>In article <3916@ece-csc.UUCP> jnh@ece-csc.UUCP (Joseph Nathan Hall) writes:
>	
>	[Various complaints about the THINK C editor...]
>
>The decision to use a given piece of software is purely your choice. If you
>find you've made a bad decision, it is your prerogative to go out and find
>a tool which best suits your needs.
>
>		--Rich

It seems that you're missing the point of this forum - the open
exchange of information and ideas.  This type of blind defensiveness
for Symantec products is neither productive for the exchange of ideas
on this network nor as a public relations perspective for Symantec.  I
don't see a disclaimer, but, I doubt this is Symantec's official
policy for responding to product criticisms.  Admittedly, some of the
criticisms are rather *blunt* but, as a Symantec representative, a lot
could be gained by a more positive attitude in answering these
criticisms.  For example, you could have discussed the following:

	- the economical reasons for not developing a more powerful editor
	- market studies that show most users are satisfied with the editor
	- plans to enhance the editor
	...

The LSC environment is great, but, it is not perfect.  The editor is
one of its shortcomings.  Even the debugger could stand a bit of
improvement:

	- the ability to save window references and locations
	- the ability to save breakpoints
	- the ability to conditionally break on variable values
	- the ability to break on variable changes
	...

These criticisms/suggestions don't mean that I want to change
environments.  I love LSC, but, I'd be happier it were improved.  Take
these discussions to the appropriate people at Symantec and give us
feedback and we'll all benefit.

>Rich Siegel
>Staff Software Developer
>THINK Technologies Division, Symantec Corp.
>Internet: siegel@endor.harvard.edu
>UUCP: ..harvard!endor!siegel
>Phone: (617) 275-4800 x305

Fred Hollander
Computer Science Center
Texas Instruments, Inc.
hollander@ti.com

The above statements are my own and not representative of Texas Instruments.