> afford to build ourselves. That limits the use of items beyond HTML and
I would have no objection to robust server-side
"bells and whistles" as long as it doesn't emulate
the "bull in a paint shop" look of so many of today's
websites. We don't want to look like "Just another
dull, stodgy, non-creative developer who uses Ada" 
but even less IMHO do we want to look like all glitz
with nothing inside.
As for "beyond HTML and scripting"--any Java (or even
that does client side processing--should be viewed
on Internet Explorer, Netscape 4.75-4.79, Netscape 6.x,
Opera, OmniWeb, and WebTV or the WebTV emulator on
MacOS 9, Mac OS X, Windows NT/2000, Window 95/98, and
at least one Unix.
When the browser crashes, it doesn't matter that it's
the browser's fault or the operating system's--many users
will blame the web site, and if it's labeled "Ada Inside".....
I also highly recommend at least considering the accessibility
documents at http://www.w3.org
I haven't yet purchased any "parental control" software, so
my sons are never surfing without my knowledge. EVERY time
they get on the net, they crash the computer. Last night,
the eldest REALLY wanted some info, so I pulled the web page
to local disk to extract what he wanted. After I removed
for black text specs--NS 4.78 had no problem showing the actual
content (which was still poorly formatted).
craqsh when Papa is surfing, so as far as they're concerned,
the fault is not with MacOS or Netscape, it's with the websites
they look at. (Frankly, I halfway agree with them!)
 Caption of a colorful poster I got from the A.R.A.