Re: Is beagle completely dead now?
Ronald Liebman <[email protected]> Sat, 12 Feb 2011 16:12:06 -0600
| Newsgroups | gmane.comp.gnome.dashboard.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============0982167773== Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> <font size="-1"><font face="Helvetica, Arial, sans-serif">Brian,<br> <br> This strikes me as a "Betamax" defense. The world is full of technologically superior products that failed for lack of some critical non-technical component. Beagle hasn't had any significant support in over a year, and is becoming increasingly incompatible with other applications that continue to evolve. Recoll is soundly engineered, is true to its own design criteria, and is dedicated to supporting its end-users. Perhaps we can all get behind contributing to the next generation product.<br> <br> Ron<br> </font></font><br> <span> <blockquote type="cite" style="font-family: Arial,Helvetica,sans-serif; font-size: small; padding-left: 0.5em; margin-bottom: -2.8em;">----- Original Message ----- <div><b>From:</b> "Brian J. Murrell" <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a></div> <div><b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a></div> <div><b>Sent:</b> 02/12/2011 3:09:22 PM -0600</div> <div><b>Subject:</b> Is beagle completely dead now?<br> <br> </div> </blockquote> </span><br> <blockquote cite="mid:1297544962.17475.14.camel@pc" type="cite"> <pre wrap="">On Sat, 2011-02-12 at 18:02 +0100, Jérôme wrote: </pre> <blockquote type="cite"> <pre wrap="">Recoll is a really better alternative remplacement of beagle. </pre> </blockquote> <pre wrap=""><!----> I don't want to start a holy war, but no it's not. It doesn't index instantly for one thing and it hammers the disk with periodic (i.e. from cron) scans of entire filesystems just in case there is a change in one or two files that need re-indexing. Beagle would have the kernel tell it when a file was modified and therefor only operated on files that were actually changed, when they were changed, providing instantaneous search match results. </pre> <blockquote type="cite"> <pre wrap="">You can index only with a cron </pre> </blockquote> <pre wrap=""><!----> Right. This is better than beagle? </pre> <blockquote type="cite"> <pre wrap="">or manually (like "locate"), so you don't waste disk i/o </pre> </blockquote> <pre wrap=""><!----> Or you could just do what Beagle did and get notifications of files that were changed and have the best of both worlds. </pre> <blockquote type="cite"> <pre wrap="">Also, Recoll index djvu documents (the best for scan archives, up to 10x lighter than PDF scans), tracker not. </pre> </blockquote> <pre wrap=""><!----> How about evolution? Does it do that? I don't think it does. Seriously, from what I have read about Recoll, it doesn't even compare to Beagle. b. </pre> <pre wrap=""> <hr size="4" width="90%"> _______________________________________________ dashboard-hackers mailing list <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-freetext" href="http://mail.gnome.org/mailman/listinfo/dashboard-hackers">http://mail.gnome.org/mailman/listinfo/dashboard-hackers</a> </pre> </blockquote> </body> </html> --===============0982167773== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dashboard-hackers mailing list [email protected] http://mail.gnome.org/mailman/listinfo/dashboard-hackers --===============0982167773==--