Author: Uri Blass
Date: 11:07:38 09/16/05
Go up one level in this thread
On September 16, 2005 at 12:58:33, Fabien Letouzey wrote: > >Hi all, > >The next version of Fruit will be commercial. After the strong performance >in Reykjavik and the good results from the CEGT-testing group, I believe that >there is interest in a near-future release. > >My decisions to close the source code and to go commercial are separate and >based on the following motives: to reduce the risk of clones which might win >important tournaments in the future and to have more time and better equipment >for working on the engine. > >Joachim Rang and I intend to make Fruit WCCC'05 available in a few weeks as >a UCI-only engine without a GUI on our website. Some unresolved issues are >remaining, such as copy/serial protection and some engine features that I >would like to implement prior to release. For this reason, I cannot yet >give an precise date. It is possible that Fruit WCCC'05 or future versions >will be distributed by other companies together with a GUI as well. > >With the UCI release, we want to bring to the computer-chess community an >engine which people can use in their favourite GUI. It is not targeted to >the mass market. > >You can have a look at a preliminary version of the web site: > >http://www.fruitchess.com > >Suggestions are welcome by email: info@fruitchess.com > >Fabien. What about search bugs of Fruit? You mentioned that Fruit2.1 has search bugs that were not fixed in Fruit WCCC. Questions: 1)Are you going to fix them for the commercial version or sell the customers buggy version? I guess that you are going to sell the customers buggy version so we go to the next question based on that assumption 2)Can customers hope to get a free update to fix Fruit's bugs or they will have to pay money to fix the bugs? Note that I plan to buy Fruit regardless of your decision about these questions. uri
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.