Unless you provide explanation I ( and some other guys) will see your efforts as wastedMy bad, this really sends out signals that you like the project. I do aplogise.If this turns out to be "yet another container with JMC, Message Beans etc", tell me then why that is bad? I think competition is good. If JBoss and JOnAS gets better because there is an alternative out there - great.
>>If this turns out to be "yet another container with JMC, Message Beans etc", tell me then why that is bad?
Why everybody screams b-a-a-a-d? Is it a sign that on subconscious level people know that wheel reinvention is pointless?
But really it is not what I am saying. Wheel reinvention might be good there are many companies that produce auto tires, so what.
Consider this: I have already invested my time into mastering of certain tools and frameworks. Now I am the comfort zone and consider my tools to be good enough. Of course there are few annoyances here and there but overall it is good enough.
Now I see some announcement of a new tool that competes with one in my toolbag. As pragmatic programmer (http://www.pragmaticprogrammer.com/index.html
great book btw) I am interested in improving my toolset and sharpening my skills and I would like to evaluate the new offering.
- I have limited time to evaluate, so the request for providing hints about what is really differentiates this product for similar ones;
- There is nothing wrong with implementing the same API again, you might have easies configuration, smaller implementation, quicker development loop ( autodeploy vc 14 mouseclicks), less issues with classloaders, tons of things. All of them far from being apparent from declaration like: we implemented XXX standard; - just emphasize those things.
Murphy law: Every problem has at least one absolutely obvious but wrong solution.
I used to be young and enthusiastic, but now I am very skeptical: many projects pop up just because somebody pursuing that obvious solution without true understanding of the problem area. Well I am nice enough to admit that new and better solution is possible :) but do not really believe that this is IT.
- Those Who Do Not Learn From Past Mistakes Are Doomed To Repeat Them;
I look references and comparison to other similar products and implementations as a proof of intelligence, their lack indicates ignorance (or some hidden agenda, which is a red flag too).
PS: IMO - any reasons for starting yet another project are fine as long as they explained: language barriers, uncooperativeness of a team in another project, dislike of coding standards, procedures, architecture, dependencies, whatever! - simply make them clear an there sure will be followers. Of course there will be shouts about validity of provided reasons: that is a whole different matter.
I simply want to know reasons that will help me (and others) enormously to make (personal) judgment about a project and will help project developers to find true followers.
Ideal project introduction IMO is here: http://supervision.tigris.org/
See Motivation and Reinventing the wheel? parts.