home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!destroyer!gatech!pitt!willett!ForthNet
- From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
- Newsgroups: comp.lang.forth
- Subject: Forth Taught at Schools/Universities
- Message-ID: <4013.UUL1.3#5129@willett.pgh.pa.us>
- Date: 26 Aug 92 11:51:33 GMT
- Organization: EIEI-U
- Lines: 29
-
- Category 2, Topic 2
- Message 123 Mon Aug 24, 1992
- E.RATHER [Elizabeth] at 21:41 EDT
-
- Chris Waters writes:
-
- >You need both users and vendors on standards committees.
-
- Users alone could come up with all sorts of blue-sky nice-to-have.s,
-
- but have a hard time finding a vendor to implement them.
-
- Vendors alone would stick with what's easiest for them. I agree that a TC
- needs both users and vendors, and I'm happy to report X3J14 has good
- representation of both. But I take exception to the notion that Vendors
- "stick with what's easiest for them." This may be true of PD implementors,
- who are after all volunteer labor. But vendors stick with *what sells,*
- because if they don't they're out of business. The thing I find characterizes
- vendor attitudes (my own and others on the TC) is the realization that they
- have a significant customer base who have heavy investments in the current
- product. We are always interested in benefitting them or attracting new
- customers, but are very reluctant to approve anything that will cause that
- current customer base to find their existing code invalidated in ways that
- will be expensive or difficult to fix.
- -----
- This message came from GEnie via willett. You *cannot* reply to the author
- using e-mail. Please post a follow-up article, or use any instructions
- the author may have included (USMail addresses, telephone #, etc.).
- Report problems to: dwp@willett.pgh.pa.us
-