Thanks for the links.
Moving off JDO and Spring MVC (the web framework, not DI) seemed to be
the biggest startup time wins, which is in line with my assertion that
DI itself is not typically the bottleneck.
That being said, the streamhead link:
Was the most interesting because he truly did DI/no-DI comparison
(trusting his approach anyway), and saw base DI adding 1s overhead.
That is more than I would have guessed, but given it's Spring, I guess
I can believe it.
I do enjoy seeing startup time highlighted--way too many pointy haired
managers (or architects) don't think 10s+, 30s+, 60s+ app startups times
affect their developers' productivity. It's terribly frustrating.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to firstname.lastname@example.org.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.