On Friday 30 November 2007 11:59:45 Hrvoje Niksic wrote: > Mauro Tortonesi <[EMAIL PROTECTED]> writes: > >> I vote we stick with C. Java is slower and more prone to environmental > >> problems. > > > > not really. because of its JIT compiler, Java is often as fast as > > C/C++, and sometimes even significantly faster. > > Not if you count startup time, which is crucial for a program like > Wget. Memory use is also incomparable.
right. i was not suggesting to implement wget2 in Java, anyway ;-) but we could definitely make good use of dynamic languages such as Ruby (my personal favorite) or Python, at least for rapid prototyping purposes. both Ruby and Python support event-driven I/O (http://rubyeventmachine.com for Ruby, and http://code.google.com/p/pyevent/ for Python) and asynch DNS (http://cares.rubyforge.org/ for Ruby and http://code.google.com/p/adns-python/ for Python) and both are relatively easy to interface with C code. writing a small prototype for wget2 in Ruby or Python at first, and then incrementally rewrite it in C would save us a lot of development time, IMVHO. what do you think? -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi http://www.tortonesi.com University of Ferrara - Dept. of Eng. http://www.ing.unife.it GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget Deep Space 6 - IPv6 for Linux http://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
