🚀 go-pugleaf

Rick DeNatale wrote:
> 
> It doesn't bode well for the ultimate fate of a language when important
> things that people want to do with the language aren't provided in
> standard ways in the language. This is one of the reasons that we don't
> have Pascal to kick around much anymore, one of the reasons that C took
> over Pascal's predominant place as a personal computer programming
> language is that Pascal left any kind of reasonable I/O as an exercise to
> the reader, and there was no common way of doing it, while C's (actually
> Unix's) stdio package was easily supported on most of the common operating
> systems.

I tend to feel this way about the AWT portion of Java: one week into the
language and you get the urge to toss out AWT and roll your own UI
classes. (Don't do it!! pester the Javasoft people to fix AWT quickly!)

One thing nice in the language is the easy TCP/IP hooks already there!
Since the base library set already includes "easy" TCP/IP support, java
just might live up to the title of king of the "networking" languages..

As for non-networked tasks, Java really needs work to compete with the
established languages (tools, Standard libs etc).


Gord Wait 	S-MOS Systems Vancouver Design Centre
                (B.C. Canada eh!)
gord@vdc.smos.com

---------------
This sig is under constru