csswizardry

Ohh wow. That’s night and day. Thanks for the feedback. I’m on it.

It’s all paranoia all the way down, I’m sure. There can be no other explanation for such convoluted implementations.

That said, I do sympathise. If your entire business/career/life is fonts, and all of a sudden they’re one ‘right click » Save as…’ away, I’d be panicking, too.

You’re not the first person to mention this—I’m sorry. Does font-weight: 400; on the body copy help? (Sorry to make you do the legwork but for me the type is perfectly legible as it is, so I need someone else to verify.)

Neat, huh? :D

Thanks, Harry!

s/acceptable/an enormous improvement

From the article, wihch presumably you read:

> Yes, we do have a FOFT, but we are getting text in front of the reader much, much sooner—this is an enormous improvement.

Emphasis mine.

~~Hey! OP here. I’m currently sat on a flight so I’ll try my best to push it back live. N.B. At some point, my client will de-whitelist my csswizardry.dev domain from their Cloud.typography account and these demos will stop working.~~

UPDATE: I’ve had to go the opposite way and pull the whole lot. It outs my client and I really don’t want their name against anything. Email me and I’ll fire you a private demo.

Hah. This is the only company that has ever f—ked me over. I’m a self-employed consultant who flew out to SF to work with them and was told the gig was off the working-day before we were set to begin. My lawyer said I absolutely had a case but I’d need to be prepared to open an international lawsuit against them (I’m UK-based) and I just couldn’t muster the effort. They got away with it.

They also quite cheerfully asked me ‘Hey! Next time you’re in the area we’d love to look at working together?’ Classy.

I had this exact thing happen to me: https://mobile.twitter.com/csswizardry/status/10812788212806...

Verdict: we need to do better.

You can pretty-print the file through the Sources panel.

Had someone on Twitter suggest `git who` which I think also strikes a great balance.

OP here.

> That is actually an SVNism.

Yep. From the article:

> Taking the lead from SVN, I alias praise onto blame…

:)

Hey! OP here.

> Are we really that afraid of hurting someone’s feelings…

I don’t do it to save peoples’ feelings: I do it because there are two separate use cases for determining the author of something—sometimes I really do not want to blame[1] someone.

1. blame — verb: feel or declare that (someone or something) is responsible for a fault or wrong.

The UK’s second biggest district by population[1], Leeds is also home to the world’s first ever moving image[2]!

1. http://www.bbc.co.uk/news/entertainment-arts-33198686

2. https://en.m.wikipedia.org/wiki/List_of_English_districts_by...

LBA: Leeds Bradford, UK

HTTP/2 is allowed to work over insecure connections as per the spec, but all browser vendors have decided that their browsers will not support unencrypted H/2 (no browser at all currently allows H/2 over HTTP). This means that in theory H/2 can run insecurely, but in practice it cannot.

https://http2.github.io/faq/#does-http2-require-encryption

My best friend @wengerstoybus[1] made this! Fun fact, he actually manually illustrated each animal in Illustrator, and then exported them to images that he loaded up in the browser. He then wrote some really quick ’n dirty JS so that he could click each of the points in the image, and he’d get their coordinates fed back to him once he’d completed a whole shape. He could then just plug these coords into the CSS etc voila!

1. https://twitter.com/wengerstoybus

This literally just turned on for me seconds ago. I noticed it because nearly all of my Notifications timeline now lacks clear context.

Related: https://twitter.com/csswizardry/status/843040649666596865

I had quite an insightful conversation with a Nepalese developer on Twitter recently: https://twitter.com/csswizardry/status/832903820539748352

Literally just received an unsolicited LinkedIn email as I was reading your comment :(

Hah, this is getting interesting. Would be more fun doing this over a beer, but…

> Let's assume a reasonable 8mbit connection and 50ms RTT.

This is a huge assumption; you’ll be neglecting almost all of your mobile users there. But! Optimise for your use-case, of course.

If you’re self hosting your fonts I would leave them external, `preload` them, and use the preferred `font-display` mechanism to deal with (or elimiante) FOUT and/or FOIT. That’s your extra connections taken care of, and we’ve moved fonts back off of the critical path :)

I think what we’ve both hit upon here is the fact that browsers need to decide on a standard way of handling FOUT/FOIT. Leaving pages blank for up to 3s (or in Safari’s case, indefinitely) would completely eliminate the need to try and circumvent it by base64 inlining :(

If you’re talking about https://theandrewbailey.com/blog/ then your CSS with and without the base64 encoding looks like this:

  101K  9 Dec 18:30 with.css
   99K  9 Dec 18:31 with.min.css
   73K  9 Dec 18:31 with.min.css.gz
  6.8K  9 Dec 18:30 without.css
  5.2K  9 Dec 18:31 without.min.css
  1.8K  9 Dec 18:31 without.min.css.gz

Although this might be true:

> …72k, which is not much bigger than the CSS without the fonts + the fonts separately.

The issue here is that CSS is a render-blocking resource and fonts are not; ergo you’ve increased render-blocking assets from 1.8K to 73K, meaning the user has to download 4056% more bytes before they get to see anything at all. Base64 encoding assets is usually a huge anti-pattern. You’d be better off moving those fonts back out into separate requests.

I hope this comment is taken in the spirit it’s intended: I like making the internet fast :)

Have a great weekend!

(If you’re interested in further reading, look up anything to do with the critical rendering path.)

You can actually enable a CSS-only hack[1] to avoid using the comments.

Using `display: inline-block;` allows you to manipulate grids with text-level properties (e.g. `text-align: center;` to cause grid items to fill out from the center of the row), and also allows you to use `vertical-align: [top|middle|bottom];` to cause columns to start from different, well, alignments.

[1] https://github.com/csswizardry/csswizardry-grids/blob/master...

I came up with this (in relation to Bootstrap) in 2011: http://csswizardry.com/2011/08/building-better-grid-systems/

This then became the basis for CSS Wizardry Grids: http://csswizardry.com/2013/02/introducing-csswizardry-grids...

I’ve been using Finch for quite a while now, and I absolutely love it. As a lot of people have pointed out, there are several alternatives and/or competitors. But, as @lachgr points out, Finch is very user-friendly, which—to a designery type like me—is invaluable.

They’re headquartered in Amsterdam, not SF, but Booking.com are probably worth a mention. (They have offices globally.)

I was invited over to their HQ to give a talk late last year and wow. An amazing company, every employee has a huge smile and nothing but great things to say, they have a really great culture, are a very wealthy company, and engineers are given a lot of freedom. Had I not just started working for myself, I would have taken them up on the full-time jobs they offered me!

Relevant: Amazon’s $23,698,655.93 book about flies -- http://www.michaeleisen.org/blog/?p=358

Hi!

> I enjoyed your talk on abstracting the grid into it's own layer by adding extra markup.

Thank you very much!

> I was wondering if you've read Grid Systems in Graphic Design?

I haven’t actually, but I’ve always fancied myself a copy. Recommended?

> Another recurrent problem is that links cannot be nested.

This bit piqued my interest, so I made this: https://bitly.com/13F3dIy