On Jul 26, 6:32 pm, Reinier Zwitserloot <reini...@gmail.com> wrote: > Java isn't designed for efficient compile/link? > > Lies.
Yeah, I've never statically linked a java program together, I've just archived the classes into a .jar and then let class loader resolve inter-class references at runtime. One thing about old fashioned static linking ala Go is that you get just the code necessary for your program to execute. That's not to say that runtime class loading is necessarily bad - its a basis for building plugin frameworks in the manner of Eclipse plugins, Java app servers that load EJBs, web server servlets, etc. Indeed, Go is going to eventually address runtime loading of code modules too. Their first target, though, is the conventional monolithic compiled app where the executable image has been statically linked. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
