thisisblurry

I'm genuinely curious to hear which web developers ignored legacy browser support and got burned. Please divulge.

jQAPI is indeed a much better choice. The jQuery API browser linked to (which is also horribly out of date) has been "superseded" by http://api.jquery.com/

It only applies for new and rewnewing customers.

Other handset manufacturers could license the patent to use it, if Apple allowed it.

I'm surprised PayPal doesn't already do this. (My account is years old, so I don't know their current practices for creating new accounts).

Twitter and Facebook both do.

So ... this means that sites will be punished approximately 15 years from now?

I'm sure that they're shaking in their collective boots.

On a very basic level, he isn't all that different from Warren Buffet, who is widely known to live quite frugally given his worth.

Perhaps to keep themselves busy?

Also worth taking a look at: http://james.padolsey.com/jquery/

It lets you quickly view how a particular jQuery function/method works.

Good luck with that.

Feel free to let the Chrom(e|ium) authors aware of all of these "bugs" and "issues" here: http://code.google.com/p/chromium/issues/list

You might help yourself out if you increase your browser window's width beyond 500px. Sure, you did that for screenshot examples, but that's far from real-world usage (this is coming from someone who shuffles dozens of tabs around all day).

This is a great little project!

Somewhat related: http://html5boilerplate.com/mobile

I was kinda hoping that this would be a Kickstarter project.

Since I live in the US, how about some screenshots?

Google has decided that music in general is still in the beta stage. I don't see them ever removing that label.

Here's the help page that might provide some extra information: http://www.google.com/support/music/

I already requested an invite, but here is what the 'Thank you' page looks like: http://jhn.me/6ckz

There couldn't be four more lists to add?

A-he-he-he-he.

Another similar website was just launched: VHX (http://vhx.tv). It's currently in a closed beta, but they're slowly sending out invites. I've been using it for a few weeks now and it seems really nice, allowing you to choose things to watch later in addition to cataloging every video you watch on the internet (it spans tons of sites, way more than just Vimeo and YouTube).

Fun fact: Former Vimeo developer Casey Pugh is one of the people behind the site.

Monoprice did the same thing when they were hacked last year. Two months after it happened, I got a letter from them with a few papers describing the identity theft monitoring service I would receive for a year.

You can get specific Chromium builds for most platforms here: http://build.chromium.org/f/chromium/snapshots/

The Chromium authors provide information on how to use newer builds here: http://www.chromium.org/getting-involved/dev-channel

There's also an AppleScript to download the latest 'stable' continuous build of Chromium (full disclosure: I wrote/modified parts of it) here: https://gist.github.com/370298

Native push notifications aside, Boxcar (as the post says) does seem to do a pretty good job of picking up the slack while they figure out the best route for them.

Fair enough, I'll keep both of those in mind for future submissions.

I'm shocked that Mozilla not only (seemingly) stores their mailing list passwords unhashed, but that they also email them out to each member every month in a reminder email.

I'm really enjoying seeing more transparency coming from you guys. Not that you weren't before, but this kinda stuff is that much better.

Keep up the great work!

I wonder, should this terrible idea actually move forward, if console.log() would be a viable replacement for using alert().

This would kill two birds with one stone: the first being the annoyance of constant alerts and the second being a faster death to (older versions) of IE since they can't handle console.log without using extra JavaScript.

Hilarious implementation in the link though :)

There are also some excellent ones here: http://www.junauza.com/2010/12/top-50-programming-quotes-of-...

As per the last paragraph of this post: http://blog.chromium.org/2010/07/release-early-release-often...

"Please don’t read too much into the pace of version number changes - they just mean we are moving through release cycles and we are geared up to get fresher releases into your hands!"

I doubt that the Chromium authors are concerned about trying to catch IE by having a larger version number. Their development calendar (https://sites.google.com/a/chromium.org/dev/developers/calen...) looks as though they have a rigid two-month schedule per version number.

I myself am already running version 11 (screenshot: http://jhn.me/4RYO) via their nightly builds.