Some of Huntbach's commentary about the current state of Java caught my eye:
However, these days when I look at the Java section in the bookshop, there is little I understand. There are huge numbers of add-on libraries, each of which has its justification but which have been developed on a learning curve and so haven’t got it quite right. Even the core APIs are bloated, since backwards compatibility means one cannot throw away one’s first solution to a problem once it has become an integral part of the language, even if developing and using it has led to a better solution. It seems to be inevitable that once a language becomes widely used as a general purpose language, it is pushed in directions it isn’t suited to, builds up unnecessary complexity through accretions, and the urge to throw it away and start again becomes stronger. A bit like any large software system which has served its time.
I'm getting to the point where I find things like this screamingly funny...
Use JAVA! It will save costs by encouraging code reuse!
Now let's throw that code away and re-write it all in the next language that will encourage code-reuse.
And using an out-dated language like perl is obviously pointless (it's more fun to re-write everything from scratch than download a solution from CPAN).
(I sometimes wonder how "Computer Scientists" call themselves "Scientists" with a straight face...)
In reply to code reuse?
by doom
in thread Interesting read: "Why I use perl and still hate dynamic language weenies too"
by ghenry
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |