jean-'s comments

Other than the fact that credit card and auto loan numbers are not updating, I like the concept. Not using tabular figures[1] here is really unforgivable, though. Maybe I'm missing a font?

[1]: https://www.fonts.com/content/learning/fontology/level-3/num...

Starting with 1.0.1b5, uMatrix is compatible with the latest Firefox: https://addons.mozilla.org/en-US/firefox/addon/umatrix/versi...

It's a neat idea, but I'm not entirely sold.

How would you implement, amongst others: vectors and matrices, matched auto-sizing delimiters (\left and \right) \operatorname, \limits, \displaystyle, \textstyle? In my line of work, every other line of maths I write requires at least one of these LaTeX features.

Also: \underset / \overset, \underbracket / \overbracket

> Habañero chile

A bit off-topic, but since you mention spelling: "habañero" is one of my favourite hyperforeignisms in the English language. Wikipedia even uses it as an example in the first paragraph here: https://en.wikipedia.org/wiki/Hyperforeignism . Such an interesting linguistic phenomenon!

Good stuff. Would be even nicer if it showed information about optionally self-closing tags, which is one of the main reasons I occasionally need to look at the spec. For instance:

> A p element's end tag may be omitted if the p element is immediately followed by an address, article, aside, blockquote, div, dl, fieldset, footer, form, h1, h2, h3, h4, h5, h6, header, hgroup, hr, main, nav, ol, p, pre, section, table, or ul, element, or if there is no more content in the parent element and the parent element is not an a element.

Links to the relevant parts of the official spec would be nice too, e.g. https://www.w3.org/TR/html5/grouping-content.html#the-p-elem...

If you enjoyed the style of this article, I would also recommend you have a look at the brilliant explanation of Earley parsing by the same author: http://loup-vaillant.fr/tutorials/earley-parsing/

Whoa, I have been working with Rust for a little over a year, and had no idea about the [-] button.

I would echo the suggestions to make that button much more visible. Or perhaps even have the top-level description expanded by default but method/trait descriptions hidden. I can't think of a case where you'd simultaneously want to see every method description.

Very nice! Another saner alternative to YAML which I like is TOML: https://github.com/toml-lang/toml

Brilliant. This just reads like a conversation with Death in a Terry Pratchett novel.

The comment field on arXiv reads:

> This paper has been withdrawn by the author due to lacking of enough experiments

> Leaf with CuDNN v3 is a little slower than Torch with CuDNN v3, yet the bar for leaf is positioned to the left of the one for Torch

I think that's because they're sorting by forward time rather than forward+backward. That would also explain why in the Alexnet benchmark Tensorflow (cuDNN v4) is to the left of Caffe (cuDNN v3) despite having a much taller bar overall.

The atoms are not initially entangled. They become entangled once a photon from one atom travels along the fiber and interacts with the second atom.

I believe that "zoom" means "to travel very quickly" in the sentence you quote.