[JDEV] Regarding The Source Code of the Development Server
mark at mjwilcox.com
mark at mjwilcox.com
Tue Feb 20 12:49:44 CST 2001
Because unfortunately there's an unwritten rule in open-source
development. If you want people to participate in your project you
code it in C. Why? Because it's a language a lot of people know
and people aren't religous about it like they are about every other
language.
For example people don't like Java's control of the language, so
they refuse to develop applications in it. Same with Perl, Python,
etc.
C++ probably isn't chosen very often because there's not as many
people who know it and more importantly the STL for GCC as I
understand it blows. Plus from the C++ code I've seen from most
people, they're just doing C with C++ constructs. In other words
they're not taking advantage of C++ OOP and what you get is a big
mess.
But, Jabber in the end is just a protocol. You could write your own
server in COBOL if it suited you :). Most Internet refernce
applications were originally written in C, but there's countless
variations in other languages. It's just that nobody else has done it
for jabber yet.
Mark
On 20 Feb 01, at 13:37, Michael Wilson wrote:
> Peter Saint-Andre wrote:
> > As discussed here ...
>
> Well, stated anyway. I don't question the decision to implement in C;
> doubtless it made sense given the requirements and skills available.
> Still it would be nice to hear /why/ C was chosen instead of C++ or
> something more RAD-friendly. Since the focus of Jabber is design
> simplicity and functionality rather than raw performance I wouldn't
> have been suprised if it was written in Python ;>
>
> +--
> | Michael Wilson "Smart Applications - Tools for life" |
> Java Developer available @ | Insight ASP LTD
> http://www.myopenapps.com
> +----------------------Open Source Innovation-----------------------
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>
>
Mark Wilcox
mark at mjwilcox.com
Got LDAP?
More information about the JDev
mailing list