The weird thing is specifically the horizontal scroll bars.
This is an interesting, but not a show stopper. I hope that Jeff addresses it.
Yes. This I don't agree. At all. I'll try and give you 10 reasons why:
Markdown is easy to parse for humans, which is something I'd like over something that is easy to parse for computers. Programming is hard lets go yadda yadda yadda.
This is not a bug with Markdown per se, but with the implementation of the diff system.
This is not a showstopper bug, so making such a big implementation change to another templating system for this one bug
Can you imagine what the change would entail? There is already an enormous body of data in Markdown. What do you propose? Keeping both backends meaning double the code for no real gain? Change the existing data to be able to parse it with the new backend, potentially loosing information in a non easely recoverable way?
Seriously? A ribbon interface? Even ignoring the fact that some (many?) people, including me don't like/hate the ribbon interface, we'd like the site to be kept simple. This is unnecessary complexity.
We are developers. We should be able to understand Markdown rules to use it effectively and fall back to HTML when needed.
WikiText has a lot of features that make it incredibly more complex than Markdown. Although we are smart enough to learn it, learning something new is a burden, in this case for no real gain. Also, it sets the bar to entry higher. If you are going to propose a Rich Text Editor, see 7.
This site is done in C#, not PHP. You are asking the team to reimplement another parser?
Why do you think that there would be no problems with a different parser?
Do you really need all the power of WikiText?
The last one is free.
Huh... Looks like the diff tool forgets to close
<pre> blocks. So every time a new code block appears in the change, it nests.
Haven't been able to reproduce it though. It's not just
<pre> blocks, or
<pre> blocks in lists...
We have improved the revision diff algorithm.
We're currently testing it here on Meta; once we're certain there are no problems, it will go out to the other sites as well. Your example was one of those I tested, and it is handled correctly by the new version.