-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The only real restriction for developing Java apps was that how that
language worked was a secret.  But how to use the language has always
been public knowledge.  It's the same type of issue with the .net
framework.  The API is available to be used, but what's happening under
the hood is not.

This leads to some intangible restrictions.  For instance with .net, we
really have no guarantee that the next version won't break something
we've done, or the API could change, or... well basically the control of
the language is retained by a single corporate entity who is looking out
for their bottom line, not necessarily the developer's needs.

Opening Java allows us to see under the hood, tweak it, and basically
apply the many eyes concept to how Java works.  This leads to greater
trust and confidence in the language.

(On the other hand, I find that anytime I start using Java, I get a new
appreciation for higher level scripting languages like PHP, Python, etc.)

My thoughts.

Shawn

shane wrote:
> *Oh, that "hoochie scoochie" ;-)
> I was wondering about open source development in Java, working around
> some restrictions.
> 
> S.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFW07E2B6Swl9qN24RAhIxAJ9QmrYZHyyjvvDWeRwjcVpaoScwgwCeKsPk
N6P/ebItO/KkAveewXqYsZM=
=Hjxt
-----END PGP SIGNATURE-----


_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to