[Year 12 Its] Re: Naming Conventions
robertw
robertw at lakessc.vic.edu.au
Thu May 12 09:12:23 EST 2005
<SNIP>
I agree, though I think Sun's original concern with Microsoft adapting it to
the "features" of Windows in such way that it *only* worked in that
environment. I think its main advantage as a "portable" language is the
consistency maintained in the structure of the syntax, if you learn the most
important principles of OOP they will stick by you in whatever direction you
want explore it.
The desire for speed is the reason for particular compilations. To the end
user it does not matter, and the developer does nmind as long as they have a
choice, and it works in a way that the big chunks of the source code are
transferable.
One of my main gripes with pre VB.Net versions, ie VB6 and before was the
feeling it gave you of different parts of it were designed by different
committees and just bolted on as soon as it "worked". Java has similar
areas as well, but was more flexible in over-riding what you did not like,
or even having choices along side each other, eg how you deal with dates or
time.
I am would like to think that VB.Net has allowed this discontinuous feeling
about the VB style to be overcome. Has VB.Net delivered?
RobW
> As Java was designed for "portable" applications (i.e. the Web's
> viewability on multiple platforms), to me it makes sense for it to
> branch into mobiles. To be honest, I thought the idea of Java as a
> general application development environment went totally against the
> principle of Java - if you have to compile it for a platform then it
> loses its purpose as a portable language.
>
> ----------
> B.J. Winzer
> St Columba's College
> Essendon
>
>
> _______________________________________________
> http://www.edulists.com.au
> IT Systems Mailing List kindly supported by
> http://www.vcaa.vic.edu.au - Victorian Curriculum and Assessment Authority and
> http://www.vitta.org.au - VITTA Victorian Information Technology Teachers Association Inc
More information about the is
mailing list