On Friday, 13 January 2017 19:22:13 UTC+11, Aymeric Augustin wrote:
>
> I agree that this setting has become less useful now that
> has won.
>
> It made more sense when it wasn’t clear whether XHTML1.1 would take over
> HTML4.
>
> I’d be interested to hear about use cases, if someone still uses
On Sat, Feb 11, 2017 at 08:15:08PM +, Adam Johnson wrote:
> I can see the advantage from an operational perspective with files matching
> byte-for-byte. I know many API's do the same with sorting the keys in their
> JSON output for the same reason.
> I should think the performance impact isn'
If anyone is still following this thread... =)
I've just updated the Google sheet above with significant changes. I was
using the wrong values for PBKDF2-HMAC-SHA256 hash performance. I now have
up-to-date hw costs and new evidence in play. Definitely worth having a
look at the latest version.
Ok, looks like the second version (conditionally sorting) is the most
sensible to go with.
On 12 February 2017 at 16:27, Georg Sauthoff wrote:
> On Sat, Feb 11, 2017 at 08:15:08PM +, Adam Johnson wrote:
> > I can see the advantage from an operational perspective with files
> matching
> > byt
>
> Would Django hard code "text/html" as the default?
Yes, that's exactly what would happen.
Thanks for the bump up, finally added a ticket:
https://code.djangoproject.com/ticket/27829
On 12 February 2017 at 07:28, Brian May
wrote:
> On Friday, 13 January 2017 19:22:13 UTC+11, Aymeric August
