RE: [Owasp-input-api-developers] language choice, design doc

[Christopher T. <ch...@ch...>]

Matt,

> Perl or PHP, if we want to take a "popular" route.  IMO PHP developers
> are in much more need of this -- at least the perl developers have -t.
>
> That being said, I think the PHP version will be good for gauging how
> well the generally [security] clueless majority will accept this.
>
> As far as C, I agree with Nik that its not used very much and it will be
> a lot more difficult to implement.  Personally, I feel anyone still
> using C, at least for frontends, is a masochist.  No reason for that
> kind of power (and danger!) to be used for a web app.
>
> Python itself should be an easy jump from the Java, perl or python
> routes -- I don't think it will be very difficult to implement it in
> python.

All good points.  I agree about Python and C.  I originally voted for Perl,
but PHP should work just as well for testing the cross-language development
waters.

Chris