inline

Having used gopher a bit before the first browser it was inline images that made the web revolutionary imo.

Are browsers intelligent enough to inline the function invocation on each step of a _.times?

If anything is worse than tables for layout it is inline CSS for styling.

With the style.css fully cached, I'm getting ~15ms faster on the sideband approach than with inline styles.

Using it in place of inline-blocks, for example (one of its useful applications), can leave your content very weirdly laid out on older IEs.

Semantics in class-names, the choice of inline styles vs style sheet etc.

With your trick of the inline stylesheet I got a massive speed improvement[0], down from about 100ms to between 60-70ms.

I think the best way is to somehow give context either inline or throughout the resume, because there isn't a standard.

I don't think anybody considers inline styles best practice.

Actually, inline styles are a fad now in React.[1] I've been trying them in my latest project, and am loving it; really solves some of my old pain points with CSS.

Arrow functions are great, but could 1) be implemented in a transpolar, and 2) unfortunately behave different with regard to this and thus make the language even harder to understand (why did all my code break when I switched out the arrow function for a normal inline function?).

You're very heavy on visuals but that's to be expected given the nature of the page and the only things you could do to make it faster are to lose the font and inline the CSS, but likely the gains in your case would be minimal so I'd just leave it as it is.

I'd rather have the text that I want to see inline ("authored PHP plug-in for the HostBill CMS to automate the task of domain registration, validation and domain name changes.

(map somefun mylist), being able to concisely define executable "objects" (closures), inline if necessary, is very useful." It is interesting because this is exactly how C++11 implements lambdas.

I was referring this quote: "being able to concisely define executable "objects" (closures), inline if necessary, is very useful" The fact that you can define inline executable objects is indeed very useful, and C++ does exactly that: an inline mangled class instantiated bounded to one variable.

Inline assembly or heavy intrinsics are more difficult to read than regular C too, so you only use them when you need to.