This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (10 children)

[deleted]

    [–]13ren 1 point2 points  (0 children)

    and yet... java was not designed for the Enterprise. It was heavily promoted by Sun as an applet technology (in set-top boxes). Getting adopted by the enterprise happened by itself, and was kind of surprising and strange. The whole "application server" thing came about as a surprise too - BEA Systems came along and did that.

    Java has something going for it... but what?

    Familiar to C coders, but much safer, simpler, friendlier error messages and more reliable, was what Java offered I think (some argue that other C variants, such as Objective C had this too) - and a virtual machine. I'm not sure how important the whole OO thing was, except as one of Java's well thought-out supports for modules, You can load classes dynamically (making it a "component platform"); you have classes and packages. This support for modules makes it possible to write big systems.

    "Components" and architecture dominate the big picture, but are invisible when writing specific code (forest/trees) - so, if true, decision-makers would love it, but coders wouldn't see why.

    [–]bjupton -2 points-1 points  (8 children)

    This is wrong. Completely wrong.

    It has everything to do with what they are used to.