luigi

It's rather clear through their actions and words that the organizers didn't have the goal of diversity when choosing the speakers. That was their mistake.

No, that doesn't make them sexist pigs. But that's a pretty serious oversight to make for the people who are curating a Ruby conference for England in the year 2012. Their sponsors are right to pull out for such an error.

Nope, not annoying either.

I've owned a Kindle 2 (returned it within 30 days), Nook Touch (sold it), Kindle Touch (soon to sell it), and now the Kindle Paperwhite.

The Paperwhite is clearly superior to all of them. Gruber's points are all extremely nitpicky.

(1) It's not a big deal to move your thumb an inch to tap the screen. The device is so light that I suspect it would be hard to make a button with just the right resistance so that it could be easily pressed while holding it in one hand. But seriously, moving your thumb isn't hard. Gruber also harps on not being able to operate large screen Android phones with one hand. Just use both hands for crying out loud.

(2) The default Caecilia font is great. I think it's beautiful. Gruber loved picking on Droid Sans, but I think that's a great font too.

It's a worthy upgrade to any of the previous e-ink Kindles.

There's also the Bootstrapper Guild:

http://bootstrapperguild.com/faq/

There's Sole Flounder, run by Maciej of Pinboard:

https://groups.google.com/forum/?fromgroups=#!forum/sole-flo...

Not much activity though.

Semaphore is great -- the first hosted CI I've tried that actually works well.

We do have paying customers.

Here's a thread with the bad experiences other HNers have had:

http://news.ycombinator.com/item?id=3856004

I launched a startup in late March, using Cloudflare, and had many similar thoughts. But it was an awful experience.

Because Cloudflare acts as a proxy, it gets in your way in subtle but devastating ways. First, the SSL support wasn't stable and I turned it off a few days into launch. That probably killed some traffic.

Then, I realized that caching was an all-or-nothing proposition. You can have Cloudflare cache your assets, but it doesn't seem to respect expires headers. You can set a cache time in the web interface, but the minimum is 2 hours! So you end up creating a rule to have it cache no assets, at which point you might as well use AWS Cloudfront for a CDN.

I advise you not to use Cloudflare. It's a great idea, but the execution just isn't there.

It should be noted that the software running Data.gov itself has not been made open source. This is a project of the American and Indian governments to produce an open-source version of Data.gov to be shared with other governments.

Here's an open-source government data catalog originally made for the City of Philadelphia, built on Django:

http://civiccommons.org/apps/open-data-catalog

Both Amazon and Google applied for .dev.

Sorry Pow users!

I thought the article was suggesting that step #1 is part of UCB1?

Sorry I wasn't clear. I meant run #1 first, then run #2. I didn't mean them as different options.

So am I getting this right?

(Edit) So the two steps to run are:

1. Run a traditional A/B test until 95% confidence is reached. This is full exploration.

2. Then, switch to the MAB after that, showing the better performing variant most of the time. As time increases, the display of the worse performing variants decreases.

Marketing it as a viable alternative seems right to me:

http://www.10gen.com/why-mongodb

I just donated $17.99 so that they can buy Crockford's JavaScript: The Good Parts.

Ah, so it is. Then I'm disturbed that browsers render a tab as 8 spaces.

They have to accurately disclose itemized contributions to the FEC, but a public website counter ain't the FEC.

I find the 8 space indentation most disturbing.

Caching is your friend:

http://wordpress.org/extend/plugins/wp-super-cache/

Andreessen Horowitz is a GitHubber!

I'm not defending it, I'm explaining it.

Google has created an open ecosystem, and these are the natural consequences. Google can't "do something about it" because of the open terms of their licensing.

Right, the problem is with the Google Market, Amazon Market, et. al. It's not with Android as a platform (or operating system).

The problem is that Google copied the "App Store" idea for software distribution that Apple created for their iPhone. Instead, they should have gone with the same idea that Linux distros use: The product vendor is responsible for distributing the software for the product. That would look completely different from what we have now, but it would be a more natural fit to what Android really is.

Also, you could have made your point just as well without the ad hominem.

It seems to me that the best way to think of Android is to compare it to the world of Linux distros. (I believe Dan Benjamin of 5by5 pointed this out on one of his podcasts.) Yes, there's Linux, but there's no one Linux. There's Android, but there's no one Android.

So while Android is technically an operating system, it's really an open platform on which to build mobile devices on top of. So the Android device I buy is that vendor's take on the hardware and the software. Google has its own take, as does Amazon, as does Samsung.

When viewed in that frame, it's not so frustrating or confusing, or even an actual problem. Fragmentation can be viewed as a natural consequence of the open Android ecosystem.

Termtter has been around for years. It does bad ass things like automate the Twitter OAuth process, stream live updates, and it has terminal colors:

https://github.com/termtter/termtter

Also:

https://github.com/jugyo/earthquake

Now it's pretty obvious what everyone going to Google I/O will get...

I used it for my low traffic personal site and thought it was great. But then one my posts got on the front page of HN and the traffic triggered CAPTCHAs for everyone. I dialed down the security settings and the CAPTCHAs went away, but still, that was annoying. And tech support wouldn't own up to their software thinking an HN spike was an attack.

Then I used it for my startup, which was using an SSL cert, and it had major problems on launch day because of that (ugh). It continued to have SSL compatibility issues for a week, so I've only been using it as a DNS since. As a test, I enabled it on staging and have left it off on production. To their credit, it seems like the SSL downtime issues have gone away.

It's been fine as a DNS, but I don't really have any desire to enable the CloudFlare features again. I love the idea of it keeping me safe from spambots and DDOS. At the same time, it really is a single point of failure, and it's failed more than any other technology in my stack. And the caching layer is way too brittle. I've set up rules to turn it off in staging.

I know. I meant that Node.js itself wasn't the fundamental leap that this is. And previous frameworks based on Node haven't attained "The One" status either.

This feels to me a lot like how Rails felt back in 2005. A fundamental leap forward and an understanding of where web technology is going.

I haven't felt that way about Node.js or even its higher-level frameworks like Express or Batman. This feels like "The One", even though I've been absorbing the docs and screencasts only for the last 20 minutes.

The vast majority of my iPad apps had an update today. It's actually likely that Apple fast tracked all submissions made recently.

And there's quite a difference between fast tracked for approval and no approval process. The former requires the developer to the submit to a black box process, the latter provides instant feedback and full control.