<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 5, 2013 at 1:01 AM, Alp Toker <span dir="ltr"><<a href="mailto:alp@nuanti.com" target="_blank">alp@nuanti.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><div>On 05/12/2013 08:43, Richard Smith
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">On Thu, Dec 5, 2013 at 12:23 AM, Alp Toker <span dir="ltr"><<a href="mailto:alp@nuanti.com" target="_blank">alp@nuanti.com</a>></span>
wrote:<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Richard,<br>
<br>
Think it'd make sense to reverse the order of the status
page to put newer standards at the top?<br>
<br>
Right now you have to do a lot of scrolling to get to
anything interesting. Search engines also seem to be
focusing on C++98 for the search results summary.<br>
</blockquote>
<div><br>
</div>
<div>Yes, the page is definitely getting unwieldy. Perhaps
adding a table of contents at the top of the page would
help more than reordering the sections? I would guess
people are hitting this page for C++11 as much as they are
for C++14.</div>
</div>
</div>
</div>
</blockquote>
<br></div>
Well, I'd go for new features on the top based on the assumption
that someone looking for C++11 is still going to find the C++14
status more informative than paging through historic standards.</blockquote></div><br>Just my 2 cents but I'd keep it ordered as is.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I expect that at some point, we'll condense the C++11 stuff to the same amount of detail we provide for C++98 now. ;] And so on. So that the baseline is at the top, and everything else are deltas.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">This isn't new though, that's how we handled C++98: per-feature check boxes until we were done and satisfied, then a simple statement.</div></div>