I think the answers you're getting here will make more sense if you re-
read John Gruber's description of Markdown's history and purpose, at
daringfireball.net.
On 21 Jul 2008, at 6:32 AM, Jurgens du Toit wrote:
I mean that "difficulty to test" must not impair the development
process.
Yes, sure, don't roll out software that hasn't been tested, but, as
Markdown
is issued under an open source license, there's who knows how many
people
who might want the untested functionality, and who will be willing
to test
it, and probably improve on it as well. Me included.
J
On Mon, Jul 21, 2008 at 12:00 PM, Aristotle Pagaltzis <[EMAIL PROTECTED]
>
wrote:
* Jurgens du Toit <[EMAIL PROTECTED]> [2008-07-21 09:05]:
I don't think that if something is difficult to test, it
shouldn't be implemented.
You mean it's fine for people to give you software that might or
might not work, and they don't know which? What happens if you
report a bug and they can't test whether their bugfix breaks
previously working stuff?
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
_______________________________________________
Markdown-Discuss mailing list
[email protected]
http://six.pairlist.net/mailman/listinfo/markdown-discuss
--
Jurgens du Toit
Cell: +27 83 511 7932
Fax: +27 86 503 2637
Website: www.jrgns.net
If people never did silly things, nothing intelligent would ever get
done.
- Ludwig Wittgenstein
_______________________________________________
Markdown-Discuss mailing list
[email protected]
http://six.pairlist.net/mailman/listinfo/markdown-discuss
_______________________________________________
Markdown-Discuss mailing list
[email protected]
http://six.pairlist.net/mailman/listinfo/markdown-discuss
