New Nagios implementation proposal

[Holger Weiß]

* Andreas Ericsson <ae at op5.se> [2009-12-18 10:49]:
> On 12/18/2009 08:55 AM, nap wrote:
> > On Thu, Dec 17, 2009 at 10:32 PM, William Leibzon<william at leibzon.org>  wrote:
> >> And while its faster to do a script or prototype in Perl or Python
> >> because of features like named arrays, built-in regex expressions and
> >> because debugging interpreted language is much easier, for large
> >> project these are not necessarily an improvement
> >
> > Not an improvement to allow easy portability?
>
> It's not hard to write portable C-code.

Indeed.  Also note that C is much more portable than Python (given the
current Python implementation); and that any portability issues which
show up in your own C code can simply be fixed, while you'd depend on
the Python maintainers for committing fixes for the portability issues
of the Python interpreter.  (Yes, the latter issue is a problem in
practice.)

And yes, I'm aware that many people are only interested in supporting
the three or four most common operating systems on x86/x64 hardware¹ (if
at all), and that these platforms are very well supported by the Python
interpreter, too.  But please don't give the impression that portability
would be a reason for choosing Python instead of C, as the opposite is
true.

Holger

² I'd call this the "Java notion of portability" :-)

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev