Fully agreed - I think the main problem of NoFlo is that I'm not sure who they're trying to get on board. Developers will be put off by the appeal for "popular" platforms and the dumbing down. But I'm not sure who else but developers is supposed to care about this stuff?
That's why I highlighted the "jargon" bit in my other reply - It seems like they have identified "people who manage or contract developers" as one (or maybe even "the") target audience.
I think that's worrying - at least if it is carried out in this tone. A good developer shouldn't need fancy flow charts to convey to you that she can or does deliver what you pay her to do. It might be what people want to have - "If only somebody would solve this problem that I cannot understand developers and they're always misleading me" - but that doesn't mean that you should pander to it. Because at its worst, you're simply giving out fancier tools for misleading clients.
That's why I highlighted the "jargon" bit in my other reply - It seems like they have identified "people who manage or contract developers" as one (or maybe even "the") target audience.
I think that's worrying - at least if it is carried out in this tone. A good developer shouldn't need fancy flow charts to convey to you that she can or does deliver what you pay her to do. It might be what people want to have - "If only somebody would solve this problem that I cannot understand developers and they're always misleading me" - but that doesn't mean that you should pander to it. Because at its worst, you're simply giving out fancier tools for misleading clients.