Article View: net.lang.ada
Article #896Commercial Liability of export controls
From: rcd
Date: Fri, 18 Jul 1986 08:11
Date: Fri, 18 Jul 1986 08:11
21 lines
1608 bytes
1608 bytes
In the discussion of whether Ada "technology" (compilers? tools? etc.) can
be exported, and what controls apply, I haven't yet seen much on how this
could apply to the commercial world. The issue that I see is that if there
is ANY chance that using Ada is going to make it more difficult to export
products, the commercial world is going to avoid Ada like the plague--and
rightly so!
Anything that could wrap more red tape around the export of a product can
kill you in the marketplace. So even if 90% of your market is domestic,
you've got to consider your foreign market. If DoD considers stringent
export controls necessary, I guess that's their call, but the Ada community
should realize that this is going to have a chilling effect on use of the
language, even for mostly domestic work.
It would be particularly helpful to have very solid, clearcut guidelines
about what is and isn't exportable--because if you're making a business
judgment, "I don't know" or "It's not clear" or "We'll have to see" are all
equivalent to "No".
--
Dick Dunn {hao,ucbvax,allegra}!nbires!rcd (303)444-5710 x3086
...At last it's the real thing...or close enough to pretend.
Technical Details
Message-ID:
<468@opus.nbires.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utcs!mnetor!seismo!nbires!rcdShow Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!utcs!mnetor!seismo!nbires!rcd From: rcd@nbires.UUCP Newsgroups: net.lang.ada Subject: Commercial Liability of export controls Message-ID: <468@opus.nbires.UUCP> Date: Fri, 18-Jul-86 04:11:51 EDT Article-I.D.: opus.468 Posted: Fri Jul 18 04:11:51 1986 Date-Received: Fri, 18-Jul-86 23:46:40 EDT Organization: NBI,Inc, Boulder CO Lines: 21