Chrome and Emoji

Simple question:

what's the actual reason that chrome on os x doesn't render emoji?

— Isaac Hepworth (@isaach) October 30, 2014

It's a well known limitation but the reason for it is, surprisingly, not common knowledge. Maybe it's a licensing issue?

@isaach licensing is the last reason i heard

— Juanted House (@capotej) October 30, 2014

Maybe a strategy tax?

@isaach I guess they are pushing their own chrome emoticons?

— ☢ Bernardamus ☮ (@Bernardamus) October 30, 2014

Maybe something darker?

@isaach PRISM can't process them yet. Available shortly.

— David E (@Eastmad) October 30, 2014

When you think about it, Chrome would need to render Emoji one of two ways: either (a) bundle a set of Emoji with the browser; or (b) use the system set. It's likely true that licensing constraints make (a) difficult. But what about (b)? Apple introduced Emoji to OS X with 10.7 Lion in Summer 2011. Why can't Chrome just render those?

The answer lies in a Chromium bug report from 2010, in which we discover that Apple's Emoji live in a 32-bit (RGBA) bitmapped font… and Chrome's graphics engine doesn't support such things.

A recent comment on the issue from a Chromium developer notes "The priority over the last year has been DirectWrite and Android, but I'll be getting to this soon".

current status https://t.co/RKLjXocY9Lpic.twitter.com/mYEiJF02LM

— Isaac Hepworth (@isaach) October 30, 2014

UPDATE 12/15/2014: the fix is in, and should be arriving in Chrome soon.

In which I get started with a quadcopter drone

It started with this:

Dolores Park, Twin Peaks, Golden Gate Bridge. pic.twitter.com/CO9Emg3KWy

— David Chen (@chenosaurus) March 31, 2014

and then this:

Coit from above. pic.twitter.com/Mq6rFy5VQh

— David Chen (@chenosaurus) April 4, 2014

and my attention was grabbed.

It was @stammy's seminal write-up on the subject of drone photography, though, which pushed me fully over the edge—and I had to get one. And here's what our new Boulder hood looks like from a drone:

and in motion:

To do this stuff, here's what you'll need:

• a drone
• a gimbal (think of this as a stabilizing camera mount)
• a camera

You can build this all yourself, of course, and many do, but I took the easy way out and bought finished items:

• $959 for a Phantom 2 Quadcopter bundled with a Zenmuse H3-3D Gimbal
• $400 for a GoPro HERO3+ Black Edition camera

as well as a 64Gb microSDXC card for the camera and propeller guards for the drone (you'll want these).

What you have now is an amazing flying machine with a camera. Here's what you need to know:

• is it hard to fly?
  Surprisingly not. This thing has a built in GPS, compass, gyroscope, inertial sensors, and a sophisticated flight computer which measures these inputs (along with the inputs from the control transmitter) and can quite capably keep itself hovering in place in a 20mph wind.
• what's the range?
  Radio range is around 3,000 feet radially. You probably want to check your local FAA regulations if you want to fly more than 400 feet above ground level, though.
• can I see what the drone's seeing?
  Not with this equipment. To do that you'd need to upgrade with parts for "FPV"; it's covered in @stammy's post.
• how long does the battery last?
  About 25 minutes' flying time. You can buy extra batteries for about $130 each.
• can I control the camera while flying?
  The gimbal will keep the camera perfectly level with respect to the horizon. Remotely you'll be able to control whether it faces directly forward or straight down, or any point in between.
• so how can I trigger photos?
  With this equipment you can't; you'll set the GoPro to record before the drone takes off, and it'll do its thing. I use a mode where it takes 1080p video continuously and grabs a high-res photo every five seconds. When the thing lands you can review what it's captured.

Some things which have surprised me:

• the ease of flying; seriously, the flight computer does most of the work
• the effectiveness of the gimbal; it's just unreal how smooth the video is, even flying choppily
• the noise; i can see why people get annoyed by these things flying nearby or overhead. Be considerate!

Number one top tip: don't descend too fast. Vortex ring state, where your drone becomes engulfed in its own downwash, is real—and you will plummet out of the sky like a stone. The worst crashes I've had have been a result of this.

Otherwise—enjoy!

Moving to Boulder, epilogue

On the fifth day of our trip we drove 42 miles in a perfectly straight line.

It made me wonder about the longest perfectly straight section of road in the US; where it would be and how long. I asked on Twitter, and so far nobody's come up with anything longer than this:

"119 miles on Highway 46 in North Dakota" says @bjppic.twitter.com/lXSbs0xoHW

— Isaac Hepworth (@isaach) August 9, 2014

If you know of anything longer, holler.

Moving to Boulder, day 9

15 July 2014: early start in Glenwood Springs; Wendy and I had decided that the best strategy to conclude our journey to Boulder was to carry sleeping kids to the car at the crack of dawn and get going—maybe breakfast in Vail as we traveled down from the mountains.

And so it was, at maybe 6.30am in the hotel parking lot, sleepy and not concentrating, on the very last day of our trip, I lifted the U-Haul trailer to hitch it to the car… and completely fucked my back up.

Onward, though. I cranked the heated car seat to maximum, sweet relief!, and all other parts of the plan went great: calm kids, no traffic, easy trip down to Boulder. We arrived about lunchtime, and here's the overgrown garden:

Here's Wendy outside the new place:

Here's Lux, still in her PJs, enjoying the garden:

Here's Cecilia, also in pajamas, clutching a find from the playhouse:

and here's everyone munching raspberries from the bush in the back yard

We had lunch, and I went to work at @TwitterBoulder—for the first time as a Colorado resident.

A month on my back is still a mess, but it's great here.

Moving to Boulder, day 8

14 July 2014: we woke up in Glenwood Springs, CO, voted in 2011 the "Most Fun Town in America" by Rand McNally and USA Today. It's perfectly nice but in my limited experience I'd say that designation probably goes too far. Our hotel was also overrated; "Feel The Wonder" says its homepage, whereas all we really felt was cramped in a tiny room and frustrated with elevators which didn't work properly.

Onwards nonetheless. We headed out for breakfast and to buy hats and sunglasses for the kids. Lux's choice:

and Cecilia's:

I got sunglasses too; I lived in San Francisco nine years without feeling the need, but within a day of arriving in Colorado knew I couldn't last without any.

We took the cable car up the mountain; Lux was unsure at first

but quickly got into the spirit. The view from the top was pretty lovely

and the 15° drop in temperature was very welcome.

That night we went out for our final road trip dinner. After a week on the road the kids were clearly on their last legs.

Tomorrow we'd arrive in Boulder.

Moving to Boulder, day 7

13 July 2014: we woke up in Moab and it was hot. And not just "gosh isn't it warm outside" hot, but "oh look parts of the car are shutting down" hot:

We figured we'd splash in the pool for the morning, grab some lunch and then get out (here's Lux at lunch having arranged the sugar packets just perfectly):

Our next stop was Glenwood Springs, but we had a brief pause for dessert in Grand Junction. Wendy with the ice cream sandwich:

Lux with a popsicle:

and Cecilia too:

It's a spectacular drive into Colorado, and my phone doesn't do it justice… but it's all I have:

We arrive in Glenwood Springs and checked into our hotel. Cecilia found God in the top drawer

and we all went swimming.

Tomorrow would be the last full day of our road trip.

Moving to Boulder, day 6

12 July 2014: we woke up in an Airbnb in Mapleton, UT. This seemingly unassuming place, under $150 for the night, turned out to be our most lavish accommodation of the entire journey. You read "basement apartment" and you don't necessarily think of a lush 3,000sqft palace underneath a 10,000sqft house, with a 70" plasma TV and a fitness room. And yet here we were.

It was also filled with kids stuff, and had a trampoline on the ample grounds, so we figured we'd stick around for a while in the morning. Let's make a pot of coff… oh, wait.

Utah.

Nothing in the cupboards, and even driving around the area we couldn't find anywhere which sold coffee. Wendy and I looked at each other, held hands, and tried not to panic. We left around lunchtime.

By late afternoon we were in Moab, UT. Our hotel had a pool, so we did some more splashing when we arrived; it's seriously *amazing* what endless joy and fascination the kids find in water. In the evening we went to a cliff-top place to watch the sunset. It did not disappoint.

Tomorrow we'd cross the border into Colorado.

Moving to Boulder, day 5

11 July 2014: we wake up in Elko, NV, with a target of Mapleton, UT. That's 280 miles, with 42 of them in a perfectly straight line. The kids both love swimming right now, and the hotel in Elko has a pool, so the first thing we do after a hotel breakfast is splash about for an hour or so.

After that it's on the road, and more of the same:

and then

and then

After miles and miles of this we decide to stop at a park in Salt Lake City on our way through—to let the kids run around and let off some steam. Liberty Park turned out to be perfect for this, and we ended up staying a couple of hours enjoying the late sunshine:

At Wendy's request we then drove just a few blocks to the Old Spaghetti Factory, a staple of family road trips from her own childhood.

With our dawdling—and a critical closed road on the way to Mapleton—we ended up not arriving at our Airbnb until 11pm. We also didn't yet fully appreciate what being in suburban Utah meant.

Moving to Boulder, day 4

10 July 2014: Thursday morning we wake up in Tahoe City, CA, with our next night's lodging in Elko, NV. That's a 350 mile journey: in England terms Southampton to Newcastle; basically most of the length of the country. I've been in the States over ten years now so UK comparisons are mostly moot, but for me growing up this was an inconceivable distance for a day's drive—you'd get the train if anything, probably.

While we're on these comparisons, though, it's worth noting that Elko—a town of fewer than 50,000 people—is the largest town for 130 miles in any direction. There isn't a single town like that in England. It's on drives like this when the vast scale of the US (again, relative to where I grew up) becomes most apparent.

Roads like this:

and this:

and this:

go on and on and on (the video covers ~16 miles).

In the UK or the US or probably anywhere else in the world, 350 miles is a long drive relative to the patience of a 2-year-old and a 4-year-old. The kids were pretty fed up by the time we got to Elko, but enjoyed reading Frederick on the iPad at bedtime:

and sharing a bed in the hotel

(in fact so much that we ended up having to separate them).

Tomorrow, onwards from Nevada into Utah.

Moving to Boulder, day 3

9 July 2014: it's nice to wake up in Tahoe. We went for breakfast in Tahoe City, with a lovely view of the lake

After breakfast we grabbed towels from the house and went to the beach for a while.

Wendy stayed mostly dry but Lux, Cecilia and I all went swimming. "Bracing" is directionally correct but really doesn't even come close to describing the temperature of the water. We dried off in the sunshine on a wooden jetty.

We had a quiet dinner that evening, in the back yard of our place. Hungry Cecilia:

Happy Lux:

Tomorrow we'll be leaving California.

Moving to Boulder, day 2

8 July 2014: Wendy and Cecilia wake up in Colorado. Lux and I wake up in California for her last day at pre-school. Here she is waiting to be picked up to be taken there by a friend

The conversation in the car on the way to pre-school, from what I'm told:

Tessa (Lux's best friend): this is our last day together we should hold hands the whole way, I love you
Lux: I love you too Tessa

It breaks your heart.

Later, picking Lux up from school, there were fond goodbyes with favorite teachers:

By 5pm the truck's filling up

By 7pm we're headed out of town:

We grab dinner in Emeryville and arrive in Tahoe City a little before midnight. The Airbnb we're staying at has a dog barking machine; it scares the crap out of me.

Onwards.

Moving to Boulder, day 1

7 July 2014: Before we know it: first thing, early, Wendy's flying to Colorado with Cecilia and Chaucer. Lux and I took them to the airport, Chaucer crying in his carrier the whole way.

Back from SFO I take Lux to school and await the movers:

waiting for people to come and pack the house up. remarkable peace ahead of a storm of domestic chaos pic.twitter.com/yPaejwwYRR

— Isaac Hepworth (@isaach) July 7, 2014

This one dude arrives and starts putting things in boxes kind of desultorily. Helpers are arriving soon, I'm told, and I make myself scarce.

By the end of the day we've got a smattering of boxes

and a relaxed Lux

but wow there's a lot still to go.

Moving to Boulder

Things moved quickly after that date night at the top of Bernal:

• April 16, Twitter announced that it was acquiring Gnip, a longstanding partner and company of maybe 85 people—based in Boulder;
• a couple of weeks later the acquisition closed;
• May 13, I accepted Twitter's offer of a transfer to a new Colorado-based role working with the Gnip team;
• May 23, we were under contract on a house a couple of miles from the Gnip—now Twitter Boulder—office;
• May 31, I brought the whole family to Colorado to check out our new place; and
• by the end of June we'd closed on the new house and bought a car in which to drive from San Francisco to Boulder.

And so the move began.

Date Night

Wendy and I moved from Denver to San Francisco in 2005. Unmarried, childless, we found a little place for rent in the Mission, rented it and moved in.

In 2006 I started working for Google. In 2007 Wendy and I got married. In 2008 we took our honeymoon. In 2009 we got pregnant. In 2010 I started working for Twitter and we welcomed Lux. In 2011 we bought our first home, and in 2012 we had another kid.

We instituted weekly date night in 2012 too.

Each week we'd usually meet at Blondie's after work, and after a drink or two go either to a movie or to dinner. 2 April 2014 was different, though: after the bar we grabbed a slice of pizza across the street, some dodgy liquor from a corner store, and headed up to the top of Bernal hill:

date night pic.twitter.com/HCAShFYsOH

— Isaac Hepworth (@isaach) April 3, 2014

On a beautiful evening, overlooking our beautiful city, I said to Wendy: "you know what we should do? We should move to Boulder".

Dropbox and Google Drive

UPDATED 4/21: update below from Scott Johnston, Product lead for Google Drive.

I figured it was time to move from Dropbox to Google Drive. On the face of it, it's deceptively easy

just like that pic.twitter.com/wcLnMRE1Qy

— Isaac Hepworth (@isaach) April 14, 2014

I have a little over 100Gb sync'd with Dropbox across three Macs. I figured it'd be a simple matter of

1. ensure all three machines are fully sync'd with Dropbox
2. quit the Dropbox app on each
3. on Mac #1, copy the Dropbox folder to the Google Drive folder
4. on Mac #1, fire up the Google Drive client, and sync (ie. upload the 100Gb)
5. on Mac #2, copy the Dropbox folder to the Google Drive folder
6. on Mac #2, fire up the Google Drive client, and sync (which should be a no-op)

and then the same for Mac #3.

Everything was looking good to begin with. Even step 4, which some had said would be troublesome, worked just fine in practice—speedy upload, no problem. The real surprise was step 6:

jfc @googledrive#weeppic.twitter.com/2FNTwLBK7f

— Isaac Hepworth (@isaach) April 18, 2014

because Google Drive was downloading an entire duplicate copy of everything, not noticing that I already had a complete copy in the local folder already.

Obviously this is fucked up. It's also, apparently, a known issue. And while I can probably live with the lack of LAN Sync, and the general unpolishedness of the Google Drive client, basic functional brokenness like this is a deal-breaker.

From a number of people I've heard great things about the Insync client for Google Drive—including its support for multiple Google Accounts. For now, though, I'm heading back to Dropbox.

…and five days later, switching back to dropbox. seriously surprised at some fundamental @googledrive limitations.

— Isaac Hepworth (@isaach) April 20, 2014

UPDATE: To my surprise the Google Drive Product lead tweeted an acknowledgment of the issue. Sounds like a fix is in the works.

@isaach Well dammit. Sorry you ran into this issue. Work in progress to fix. I'll ping this thread once it is rolled out.

— Scott Johnston (@happyinwater) April 21, 2014