>First, I swear cold viruses must wait to ambush me whenever I come to California in the spring. I’m a walking incubator of germs this morning, so attendees be ware. You may help me kill it by providing lots of beer later in the evening.
Jeff Atwood and Clay Shirkey actually did a very decent keynote. Growing you social community around your project is hard work. There is also no magic silver bullet that one can find. However, what I saw that was common amongst all of the slides and discussion, was the need to be responsive to your community. In order to attract contributors, you need to respond and address their needs. We do a good overall bring in users, and making things they want to use. However, where it is very hit or miss is in the response time and eventual fixing of the bugs that the community raises. If project seems to be unresponsive to it’s communities needs in regards to the bugs they file, or patches they contribute, then I suspect it’s not going to thrive beyond it’s original adopters.
Web Services Tools:
Kathy Chan did a good job of introducing the overall scope for Web Services Tools in the WTP project. She went through the Web Services Explorer, which works well for small web services. However, my experience with the WSE is that it suffers performance wise when dealing with large industry standards and WSDLS that use those standards from STAR, AIAG, HR-XML, and OAGI. WSE is a very cool and useful product, it just needs more tuning when it comes the business-to-business web services. Include Axis 2 generation is also a plus.
The limitations right now for Web Services in eclipse, is that beyond the generics of SOAP and WSDL, there is no plans to support WS-Security, WS-Addressing, etc. However, there is an WTP Incubator project that can allow for XML Security and Digital Signatures to be added and used by the Web Services Tools. Check out the talk today at 10:10.
Removing the Fat Man:
This was a very good talk, that had an overflowing room. The key thing from this talk. Don’t use String + concatenation. Use StringBuffer instead. Also, presize your HashMaps as well. Dynamically creating and resizing the HashMaps is expensive. Also, do not assume you know where the performance or memory bottle necks are. Use a profiling tool to help you figure these items out. Most of the time your performance bottle necks are in different areas than you thought. This was a very good talk that would deserve a Tutorial in the future as well.
Well…it’s starting to look pretty. It’s doing a very good job at building a diverse community of committers. But for a potential 0.9 release….there isn’t much beyond experimentation at this point. Hopefully since it is supposed to be released in 2010, some of the design and framework decisions will solidify. Also, as Ketan showed me, and I agree…E4 you need more unit tests even if it’s prototype code. Because some of that proto-type code is going to become the basis for e4 going forward. Do not repeat the same mistakes that occurred during past eclipse development with very low code coverage in your unit tests.
Ready for Day 3:
Full schedule of XML and Web Tools talks to day, plus I’m going to try to battle the evil forces of the cold virus and beat it back into submission today as well.