<div class="gmail_quote">2009/5/25 Remco <span dir="ltr"><<a href="mailto:remco47@gmail.com">remco47@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Oh great, now there is poison on slashdot:<br>
<br>
<a href="http://tech.slashdot.org/article.pl?sid=09/05/24/2044239" target="_blank">http://tech.slashdot.org/article.pl?sid=09/05/24/2044239</a><br>
<br>
Let's not fork, shall we?<br>
<font color="#888888"><br>
Remco<br>
<br>
<br>
</font></blockquote></div>Well, this is awkward.<br><br>For the record: I didn't intend to ambush anyone on here<br>with my frustrations, and I certainly wouldn't have chosen to<br>publicise them via Slashdot. Such is the nature of public<br>
discourse, eh.<br><br>I don't think forking's the answer (and I'm certainly not putting<br>myself forward for that!) That said, there's only so long that <br>the issues of a proper DIB engine can go unadressed, and<br>
I mean, it hasn't been addressed for some time, despite <br>the efforts of several people, latterly Massimo, to provide <br>at least proof of concept solutions. All that's really been <br>agreed upon is that what's there now can't be tweaked over<br>
time to become the "right solution", but at the same time, <br>it can't be replaced wholesale as that might cause regression.<br>This would seem to be a logical impasse, and that's why<br>it needs a decision made, I think.<br>
<br>No one developer is going to be able to come out and write<br>the roadmap for it, because it needs broad input from a <br>lot of people, not just Alexandre. But certainly, as a starting<br>point, if it's so trivial to reject something on the grounds that<br>
the architecture is WRONG it suggests that there is a <br>solution out there that's RIGHT, it just needs to be documented.<br><br>My intention was not to whine, (except that it's heartbreaking<br>to see good code go to waste over and over again) nor was it<br>
my aim to throw stones, but to try and stimulate the required <br>discussion. If this list isn't the place for that,<br>then perhaps a section of the Wiki? Even just a timetable<br>for when it might be discussed? (As in, by release x.x.x, the<br>
roadmap needs to have been agreed upon).<br><br>--<br>Chris<br>