> The tasks of crawling, indexing etc. etc. just do not fit in the > browser.
It's also useful to do these tasks when not running the browser, or from machines where browsers aren't useful (e.g. servers with better network connections). > P.S. The one thing I don't like about YaCy is it is written in Java. I > think this makes software slow. But if it becomes popular I bet someone > will write C or at least C++ libraries, crawlers, indexers, clients etc. > etc. that use the protocol. Java is the slowest way to write a true(1)-compatible program known to me, it's probably similar for typical quick programs for use in shell scripts; it's faster for long-running programs if using a supported architecture (not my MIPS64-like laptop). For me the problems with Java are that it makes source longer, easier to make some bugs, and more difficult to use some nice ways of designing programs than e.g. Python or Haskell, it also uses more memory than C, requires huge JDK package, and programs using it are distributed in a way unfriendly to GNU/Linux distros (e.g. with dependencies bundled). I don't know if any of these arguments apply to this case.
pgpel3AFJYcic.pgp
Description: PGP signature
