Waiting for a build ... - Slashdot

Follow Slashdot blog updates by subscribing to our blog RSS feed

×

Journal alien_blueprint's Journal: Waiting for a build ... 6

Journal by alien_blueprint on Wednesday May 12, 2004 @04:29AM

I haven't done that since about 1998 :) So, yes I'm posting on /. from work and I'm proud of it!

I remarked to some team-mates the other day that we know Java has finally come of age and is ready for large scale serious computing etc ... because the build times are getting up there with what C++ build times used to be.

It's an exaggeration, of course. It's only half an hour to build our entire code base, and the C++ code base I'm thinking of took 3-4 hours back in 1996. Still, this whole "waiting for a build" thing is bringing those memories flooding back ...

All we need to make Java build times "enterprise level" (ie. totally unbearable) would be templates (those could take hours to build, I would watch them slowly being compiled individually), and they are coming in Java 1.5. Hooray!

This discussion has been archived. No new comments can be posted.

Waiting for a build ...

Load All Comments

Search 6 Comments Log In/Create an Account

Comments Filter:

heh. (Score:2)

by The Fink ( 300855 ) writes:

The app I work on apparently takes the better part of one day to compile, using some form of distributed compilation across 16 CPUs (eight two-way boxen).
I say "apparently" because I haven't seen it, and have no way of seeing it.
- Re:heh. (Score:2)
  
  by alien_blueprint ( 681111 ) writes:
  
  What language is this, by the way?
  
  Huge build times are common for large projects in my experience. The answer, I've found, is not to do large projects! :)
  - Re:heh. (Score:2)
    
    by The Fink ( 300855 ) writes:
    
    Java 2, SE, 1.2. :)
    - Re:heh. (Score:2)
      
      by alien_blueprint ( 681111 ) writes:
      
      Wow, that's impressive. Java (I've found) suffers less from this due to the lack of the header files as found in C and C++. Basically, the contents of the header files are being compiled over, and over, and over, for each file they are being included in, and worse, for every *include* file that they are included in, which creates an O(n^2) effect that kills the build time. Even with the standard include guards wrapping the contents of each header file, the simple act of opening the file, failing the include
      - Re:heh. (Score:2)
        
        by The Fink ( 300855 ) writes:
        
        Approximately four to five million, I believe - roughly. Works out to be 700MB of class files, either way.
        
        Re:heh. (Score:2)
        
        by alien_blueprint ( 681111 ) writes:
        
        That explains that then :)

There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.

I've noticed several design suggestions in your code.