Appraising Wealth, Effort, Legacy, and Markets

Late last night, after I posted new content on the java.net home page, I was wandering the corridors of the java.net projects space. On the one hand, I was looking for tools that I might be able to bring into an experimental project I've been considering, a kind of reinvention of the financial mathematical modeling that has occupied varying amounts of my spare time since 1986. I'd build the reinvention by integrating old (and, ultimately, new) mathematical/analytic formulas with important Java/JVM technologies that are present in java.net projects, that could be useful in my project. Then, I'd also write blogs and articles about how I used the technologies, adding to the wealth of available documentation. I've done this before -- see Porting a Project from Visual Studio .NET to Mono and Analyzing Statistics with GNU R, for example. But, as I did this wandering, I was struck by the complexity of some of the larger projects and tools -- for example Hudson, Jersey, Shoal, Grizzly. By complexity, I don't necessarily mean that implementing and using these projects is difficult. I don't mean that at all. What I'm referring to is the breadth and scope of the problems that the projects undertake to solve, and their success at addressing the multitude of situations that an enterprise-level application must successfully address. For example, look at the Jersey 1.1.5 User Guide. I look at that, and what...

Date: January, 27 2010
Url: http://www.java.net/blog/editor/archive/2010/01/27/appraising-wealth-effort-legacy-and-markets

Others News