Speed or Productivity? Debate Goes On
Developers' tool choices used to be made with a stopwatch, back when compile times were measured in minutes and desktop PC speed was the client's limiting resource.Developers tool choices used to be made with a stopwatch, back when compile times were measured in minutes and desktop PC speed was the clients limiting resource. Todays performance bottlenecks often reside at a distance, whether in network bandwidth limits, in opaque run-time environments or in server-side code. Should developers still use tools that let them write the fastest-possible code, even if that means spending costly programmer hours to enforce good behavior? Or should they take advantage of the higher productivity that comes from Javas elimination of many common sources of programmer error?
Borland Software Corp.s JBuilder (reviewed above) was one of the first developer tools to exploit what could be known about a Java application, parsing code dynamically for feedback during development. Oracle Corp.s JDeveloper now gives JBuilder a run for its money in this regard, but so does Microsoft Corp.s performance-oriented C#. The choice of productivity or performance is no longer a choice between Java and everything else.