Advocating Niggle

This essay is a work in progress. Check back later.

In this essay, I will make the following daring assumptions:

• You have tried Niggle, gone through the examples, and maybe even built a small prototype on top of it.
• You like it! You like the approach and you want to use it.
• You have to overcome skepticism in your organization that Niggle is an appropriate tool for them to be using.

In other words, I assume that you yourself are sold on using Niggle, but now need to sell other people on it.

Well, this is a sales job, and I am not a great salesperson. I can nonetheless think about what the possible objections that people will have and what arguments you can use to counter them. Of course, that you have all kinds of rational, well-reasoned arguments in your favor is no guarantee that you will carry the day. Note that I am very very interested in getting feedback from people who have advocated using Niggle in their organizations, so that I can make this essay as effective as possible.

Possible Objections

In all likelihood, people will not object to Niggle per se. As of this writing, Niggle is not sufficiently well known for people to have preconceived ideas about it one way or the other. It is really the category of things that Niggle belongs to -- free, open-source software written in Java -- to which people will have objections. So, there are objections related to using Java at all, as opposed to other server-side solutions. Also, there will be uncertainties about using free, open-source solutions rather than proprietary products.

Besides its java-ness and its open-source-ness, you may meet the objection that there is no need for a 3-tiered application framework of this sort.