Mozilla


31
Jul 09

More on Printers, from Bigelow

A couple of days ago, I posted something about how I’m playing around with @font-face (and since then have also been experimenting with TypeKit, which I use for the headlines you see here). Generated a bit of discussion, but one of the things I mentioned at the end of my post was a class I took at Stanford 15 years ago called Concepts of Text, and taught by Charles Bigelow, a well-known font designer — his foundry did the font family Lucida, for example, and the System 7 city fonts, among many, many others.

One of the classes I remember fondly for being a little wacky (and interesting) was when he gave a talk about typographers who were persecuted for the material they were typesetting.

After I posted the other day, Professor Bigelow somehow found the post and gave us a little primer, which I include below because of the high awesomeness quotient. Really made my day – favorite comment ever. :-)

Nice to hear, after all these years, that somebody remembers those classes. :-)

Just in case the names and dates have faded from memory, here’s a brief refresher.

Antoine Augereau, Parisian printer and type designer, reputedly the teacher of Garamond. hanged and burned on Christmas Eve, 1534, on (supposedly trumped up) charges of printing heretical placards.

Etienne Dolet, printer of Lyon and Paris, burned at the stake on August 3, 1546, in Paris, on charges of blasphemy, sedition, and selling prohibited books.

Martin l’Homme, hanged in 1560 for printing a pamphlet against a Cardinal.

That all happened a long time ago, but in the 20th century, Sophie Scholl, among others in the White Rose society, was guillotined on charges of treason, on February 22, 1943, for distributing pamphlets against Nazi genocide on the Eastern Front.

I’m sure that somewhere there is good news about printers, too. :-)


27
Jul 09

Why I’m messing with fonts

If you come to the web-based version of my blog instead of reading it in a feed reader, and you use a modern browser — Firefox and Safari, at least, and maybe some versions of Chrome — you may have noticed I’ve been experimenting with using different fonts.

I’ve been doing this for a couple of reasons, neither of which is particularly related to the readability and aesthetics of the blog.

The first reason, and more important of the two, is that I wanted to experiment with the new @font-face support in Firefox 3.5. I have a strongly held point of view that you don’t really learn about something until you do it — and since I have a bit of an affinity to fonts, I thought I should try @font-face out on my own blog. I discovered a few different things in this process.

First, there are not a lot of really good fonts online that are licensed for use on web sites — either free & open fonts or purchased fonts. I think both categories (free and non-free) will see more & higher quality fonts available soon, since fonts are available now to so many more users than before. (@font-face was not new with Firefox, but obviously Firefox brings a lot of users along.)

Second, you learn a lot about your web server & how quick it can send data, since in addition to your web content now it’s gotta send font files that are 50-100 KB or more. My server, for the record, totally sucked. Now it’s better, but not as quick as I’d really like.

Third, the differences in implementations really become apparent. Safari opts to wait until a font file is loaded before showing any text rendered in that font; Firefox renders the text in already-resident fonts and then sort of “pops” the text into the new font when it downloads. That shows pretty clearly a difference in aesthetic between WebKit and Gecko (and probably the organizations behind them): WebKit (and Apple) prefers a solution to minimize visual divergence — so you never see text in the wrong font. Gecko (and Mozilla) prefers a solution to get people reading content as quickly as they can, even if it means a momentary rendering in sub-optimal font — because a lot of times people want to get to their content as quickly as possible. Anyhow, different decisions that will impact designers and consumers differently.

Finally, it helps us figure out where the bugs are. One of the initial fonts I used didn’t have some ligatures implemented — “ff” in particular — and Firefox handled that by just not showing anything. :-)

[As an aside, I've been tracking TypeKit since before they launched, and am quite optimistic about their prospects. I'll try them out as soon as they open up the beta.]

The second reason I wanted to experiment is that I’m a bit of a font nerd. Have been since my mom got her first Mac in 1985. I really like type and lettering and the way that it affects how people feel and think. One of my favorite classes at Stanford was called “Concepts of Text” and taught by a type designer named Charles Bigelow — among other things, we had a couple of classes about typesetters who were burned at the stake for typesetting heretical documents. Good times.

Anyhow, I like type, and am really excited by the prospect of more sophisticated typography coming to the web. And as much as I like Helvetica — and I do! and you should, too, not to mention you should go see the movie — I feel like on the web today there’s a bit of a Tyranny of Helvetica — it’s somehow viewed as the most appropriate type for, you know, everything.

So I’m experimenting, and will probably do it more. Right now, I’m over-using (not to mention sort of mis-using) 2 fonts on this blog. I’m using Graublau Sans for the headlines — it’s an free/open license font designed for larger display settings. And I’m using Spiekermann’s newer font Axel for the body type — it was really designed for very small type — especially in cells in Excel spreadsheets, for example — but I liked that it has many similarities with his Meta typeface, which happens to be the one we use for the “Mozilla” and “Firefox” and “Thunderbird” wordmarks — but also had a relatively inexpensive (under $100 US) @font-face compatible license available for purchase from FontShop.

If I have some time this week I’m going to try to make some of the more egregious readability problems I’ve caused…um, I guess I’ll strive to make them less egregious. But we’ll see.

I do know that it’s fun to experiment with type again.


4
Jun 09

Onward

(photo credit: Jay Goldman)

To tell you the truth, I didn’t know what to expect 4 summers ago when I started at Mozilla. We were in our (extremely small) space on Villa St; Firefox was taking off; I was quickly learning that the Mozilla-style of doing things did not quite match what I expected. I knew that it was an important project; I knew it had smart, unique leaders; I knew that I didn’t understand much about how it could possibly, you know, actually exist.

But it was an undeniably exciting time — tons of people were using and discovering Firefox — there were probably something like 20 million users at that time. Firefox 1.5 was nearly finished; Thunderbird 1.5 was on the way. And it just felt like there was a ton of promise and opportunity on the web that hadn’t been there a year before.

A couple of months after I started we moved into our current offices at 1981 Landings Drive (pictured above), and in the intervening 4 years, tons and tons has happened. Mozilla has grown, of course — into a network of community and contributors around the world that create a product that’s in more than 70 languages and used by more than 300 million people. But the web itself has gone through an enormous explosion of innovation. When we moved into this office in late 2005 was a time before YouTube became huge (they were just 6 months old) — and was really before video on the web was meaningful. It was before Facebook was big — would be another year until they opened up to everyone. And of course it was way before Twitter came on the scene.

And, of course, the world of the browser looks incredibly, impossibly, and wonderfully different today than it did then, with a faster-than-ever Firefox dropping soon, an improved IE8, and Safari, Opera and Chrome each competing and innovating. Oh, and the whole mobile browsing thing happened, too.

In just the four years that we’ve been here — out of the 11 since the Mozilla project started — the web has been transformed, and has itself transformed so much of the way we live our lives. It’s easy to gloss over, since we see the changes every day — and it’s easy to see the road that we’ve traveled on as being inevitable — but it really wasn’t. The reason we have a vibrant, open web today is because of millions of little decisions and contributions made by thousands of people in that timeframe — people who work on browsers, people who build web sites & applications, people who evangelize for standards, people who use the web and ask/demand that it be better.

Leaving this building for our new home at 650 Castro (which, for the eagle-eyed Netscape historian will look familiar) gives me a bit of a chance to reflect on how much our world has changed while we’ve been here, as well as the part Mozilla’s had in effecting that change.

And I have to say that looking forward, I can’t wait to see what the next 4 or 5 years brings, and what we can do from our new home & vantage point. The web continues to be the driver of an unprecedented amount of change, and I don’t see that slowing down any time soon.

So as Mitch likes to say: onward.


17
May 09

The Glass House


A few weeks ago I took a trip to the East Coast — it wasn’t really the best week for me to travel — there was an awful lot going on at work and at home that I needed to attend to — but I went to a little town in Connecticut called New Canaan because I got the opportunity to participate in something unique — a Conversation on Transparency at Philip Johnson’s Glass House. (New Canaan itself is a place with unusual history, worth checking out.)

I didn’t really know much about the Glass House or the event or what I was getting into when I signed up — only that Diego Rodriguez, who I think quite highly of as a design thinker & friend (go read his blog!), strongly recommended that I participate — so I did, and I’m really glad I did. It was a bit of a different world for me, but gave me much to think about in my own contexts.

I think it’s going to take me a few posts to write this up — I’ll need one for the place/context/history and what the National Trust is trying to do; will need one for the people & objectives of the Conversation Series; will probably need another for the ideas that came up. But want to capture some of my thoughts before they flit away, so will start writing. [I started writing this right away, anyway, but now am just getting around to finishing it.]

Philip Johnson was a complex guy, for sure. One of the leading architects of the Modernist movement, he’s built some of the most influential buildings of the 20th century, from his own residence, the Glass House, to the Seagram Building in NYC, to the Crystal Cathedral. What I didn’t know before is that he’s known as much for the people he influenced and mentored — many of whom were probably better architects.

Anyway, he built this house for himself called the Glass House, and it’s exactly what it sounds like — a house that he lived in for more than 50 years with walls made only of glass.

Building a house that’s completely transparent is more than just an architectural statement (and it definitely is a significant architectural statement) — it’s also a personal statement — a statement of values, of ideals. It’s made more interesting by Johnson himself — among other things, a gay man who had voiced support for Nazi Germany in the 30s (although he later clearly & obviously regretted it and couldn’t really even understand it). Think of that. To be a gay man (not openly, but more of an open secret) in mid-20th century America and deciding to build a house that anyone could see right into, and even through. There’s a lot to parse in there by people who know a lot more about the human psyche than I do, but right off the bat you can see any number of ideas: idealism, design, openness, exhibitionism, power — it’s a really complicated mix of things.

And it’s made more complicated by the fact that the Glass House isn’t really a glass house — or rather, that particular building is made of glass and transparent, but it’s situated in a much larger context — 47 acres of extremely maintained landscape, and something like 19 total buildings that make up, really, a house turned inside out. And the Glass House itself is the only building made of any significant amount of glass. (with the exception of the ceiling of the sculpture museum)

So there’s the Glass House, with a living room, kitchen (although minimal — they called it more of a martini bar), dining area, bathroom (in the brick column), plus some walnut cabinets in the middle. Made of steel & glass, with a red brick floor.

And the Brick House, made up of a small guest room, bathroom & library — purposely built to be a little uncomfortable, because he didn’t like his friends like Andy Warhol staying for more than a couple of days, as he said “guests are like fish, they should only last three days at most.” (Same basic dimensions as the Glass House opposite, same elevation & length, but half the width. (There’s definitely an optical illusion going on there — they look roughly similar.) The irony/symmetry/connection/whatever of the Brick House being opposite the Glass House is incredibly compelling.

And the art gallery, buried under a mound, as an homage to an Egyptian tomb for someone who’s name I now can’t remember. The point that Dorothy Dunn, our guide, made is that it’s a great irony for an art collector to build a house where the walls are glass — no place to hang art! So they built this underground bunker sort of thing, and it can hold a LOT of art for the space — the works are on a sort of giant rolodex system, so you can rotate in whatever art you want to look at. Mix & match. It was fun to get to look at all the things on the wheels behind the works that were showing.

The sculpture gallery, which is built sort of like a hothouse with a glass ceiling — and one of the guys who maintains it confirmed that it often feels like a hothouse — that it’s hotter than hell in the summertime. The space of the sculpture gallery is a little difficult to show with 2 dimensional pictures, so I’ll include a few, as well a bronze cast that is  outside the front door called Ozymandias. I’ll let you draw your own conclusions on that particular statement.


One of my favorite buildings is his library — easily 100-200 yards away from the main house — and with a funny sort of shape. But it must have been a cozy place to read and work.

Right near the library, there’s the Ghost House — a primitive archetype of a house, really — I don’t know what it’s really for other than just, you know, looking like a house.

Out on the grounds there are a number of other things — at the front gate, there’s a place for receiving people that we didn’t spend much time near.

And there’s a little man-made lake with a sort of terrace — hard to really make sense of this, since it seems to have been built on a smaller scale, for effect — but you can see from my pictures that if you’re at all taller than me, you had to duck down a bit to be inside.

And a cinder block statue that didn’t make a ton of sense to me — except that it made sense when viewed from the Glass House itself, which I think is part of the point — a lot of the space was designed for experiencing from particular points of view, with the inside of the house being the most important one.

Even the grounds themselves were very manicured and varied, with streams, lots of different textures of foliage, etc.

Make no mistake: this is a beautiful & wondrous place. It’s not remotely like any other place I’ve been or heard of, and it’s amazing. I felt lucky to get a chance to go (tours are booked a year or so in advance, but the access that we got was more than a tour — it was total access, really). I also felt very lucky to get a chance to participate in the discussion on transparency — more on that, plus some more interior (such as it is) photos when I get a few more minutes to write.


1
May 09

Poetry & Pragmatics: Mozilla All Hands 2009

This week we had about 250 employees & contractors from across Mozilla-land out to Mountain View for an all hands meeting. It was a great week, full of interesting conversations with people who are really dedicated to changing the world and making the web a better place. Super generative; sometimes contentious; always earnest & dedicated & thoughtful.

I gave a talk & had a conversation to start the week off — I wanted to talk about some of the context that we find ourselves in now and how we can think about becoming a longer term organization, now that Mozilla’s first 11 years are behind us. I focused on the tension between what I’ve come to call Poetry & Pragmatics. The pragmatics of an organization are how you do things; the poetry of an organization is why you do them.

There’s a big difference; they’re both important, and sometimes they amplify each other, sometimes they conflict. Getting the balance right, from day to day, from year to year — that’s the thing that great organizations do over time, and it’s what we need to always think about how to do better.

I also talked a bit about how we’re going to need to change going forward, adjust to new circumstances, avoid holding onto outdated ways of thinking, try new things.

In that spirit, I’ll attach my slides from that talk here — it’s a bit of an experiment for me to post what’s essentially an internal talk — lots of context missing, lots to misconstrue — but I really believe in the content and so figured I’d try sharing. :-) See what you think.