links
300 Images From 1800 Sites
Punctuated Productivity
ascii table
brainjar.com: css positioning
Catman's Reference Guide to XHTML 1.1
Catman's XHTML 1.1 Elements and Attributes Reference Guide
citeseer
Color Scheme Generator
common errors in english
cool images
Copying music between authorized computers with iTunes for Windows
css layout-o-matic
daypop
del.icio.us
elegant hack
emacs wiki
floatutorial
imho...
keystroke shortcuts for windows xp
mozilla keyboard shortcuts
NameVoyager
perldoc.com
programming language popularity
regular expression tester
selectoracle
short url services
simple urls for search engines
the unix acronym list
yahoo dictionary

permalink

why do Java developers like to make things so hard

In TURNER’S VIEWPOINT: Why Do Java Developers Like to Make Things So Hard?, James Turner takes a stab at what’s wrong with java.

The LunchWaitress takes your order, brings over your food, but there’s no plates to put it on because you forgot to get a CutleryFactory and invoke getPlates, so the Waitress throws a null pointer exception and you get thrown out of the place.

I agree, but there’s more to it than that…

Share this article on post this at del.icio.us post this at Digg post this at Reddit

* * *

  1. there may be a chief chef TRYing to overlook the tables and chairs and ensuring that plates are there on the tables….that everything is in order….else the waitress will have to CATCH hold of the chef to make sure that plates are ordered and are there on the table….. but because she is on the RUN TIME with the dishes in her hand…. she fails to grab the chef’s attention…and dumps the food on the table…the person fills the complaint book with a big trace…and the owner of the restaurant has to debug his systems to find the potential null objects..and tries to do some work code optimization….
    — Venkat    Mar 2, 07:52 AM    #
  2. article mentioned above was purely from the point of view of the complexity involved in coding and understanding polymorphism in java. in other words, macroscopic and microscopic views..coding polymorphism in java may be abstruse but alongwith it brings about scalability and re-usability et al instead of re-inventing the wheel everytime had it been programming in perl..there has to be trade-off to obtain a plus… java sure is slow but the foundation of java is write once, run anywhere…had it not been for java, there would have been 64-processors computers in plenty…by this time…
    — V    Mar 3, 07:44 AM    #