Hello,

> > On Aug 3, 2012, at 11:53 , Michal Suchanek wrote:
> >> Why markdown and not one of the dozens of other wiki syntaxes?

If I understand correctly this question wasn't addressed to me (as a
developer of the markdown-in-fossil code) but I'll try to contribute as
objectively as I can.

As a user, the killer feature I see for markdown is that the
implementation exists (assuming my code is considered worthy, which is
quite a strong assumption, but without it everything else is moot
anyway, so I'll keep the assumption in this e-mail). Code that exists
wins over code that does not. We can discuss for days about the best
markup syntax, it's completely useless when there is nobody to actually
implement it.

Of course, I would welcome other propositions of implementation, and I
would still be glad if my code was rejected in favor of another
implementation (of markdown or of another lightweight markup language
that I prefer to the current wiki syntax).

Now my personal opinion about markdown is probably of no interest to
anybody else, but while I do have strong objections and dislikings
about it, I haven't encountered any other lightweight markup syntax with
which I have more affinity. Useless, isn't it?



on Friday 03 August 2012 at 12:19, Michal Suchanek wrote:
> And it has been said that markdown is out of the scope of Fossil.

I don't know about that. And honestly, I'm glad I don't have to make
that call.

>                                                                   I am
> not to decide that but I have to agree. Once you let in markdown
> people used to some other wiki syntax would argue they have needlessly
> hard time and there would be no end to the stream of requests to
> include yet another.

I think it's very useful to distinguish between requests to write code in
order to include yet another, and requests to officially mirror a branch
containing ready-to-use code that includes yet another.

Surely the stream of the second kind of requests would be much lighter
than the stream of the first kind, wouldn't it?

And as far as requests of the second kind goes, if the code is good
enough and does not bloat the project, why not accept them? (in the
context that assumes markdown has already been let in)



Thanks for your criticism,
Natacha Porté

Attachment: pgpyROnFPGls6.pgp
Description: PGP signature

_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to