risotto

Awesome project.

Browser technology is on a tear recently, and terminals are ripe for innovation. For a newborn project, this is an impressive mashup.

The number of dismissive people in this thread shows how disruptive this idea is!

Full stack web servers like Mongrel or CherryPy.

Server fabrication and automation tools like Chef, Puppet, Fabric.

Process management tools like God.

Parallel worker systems like Resque or Celery.

PHP is great for web apps, but the further I've gone into systems programming, the more I need Python/Perl/Ruby (or C).

Has anyone ever experimented with deleting/disabling features on an Android phone?

I'm always curious what it'd be like to have a "smart" phone with no email or web browser, but still GPS and a camera.

I'd like to work on my nervous habit of taking out my phone and checking HN/email/Twitter, etc all the time.

Hiring only the best is impractical unless you are Google and can pay the best for the best.

A much more practical strategy: hire people that can learn, and train them in best practices.

Food for thought for sure. True, nothing can get better forever...

But do we believe in "economy of scale" for computer and Internet systems in this age? Google, Amazon, Facebook, etc. have already proven to me that they have enough human and financial capital to architect and run systems that show economies of scale.

It's a bit scary to think about what it will mean when this runs out, but for now I personally feel confident that things are getting much better, and will continue to do so.

These outages are very rough. Clearly a lot of the Internet is building out on AWS, and not using multiple zones correctly in the first place. But AWS can have multi-zone problems too as we see here. Nobody is perfect.

But what people forget is: AWS has a world class team of engineers first fixing the problem, and second making sure it will never happen again. Same with Heroku, EngineYard, etc.

Host stuff on dedicated boxes racked up somewhere and you will not go down with everyone else. But my dedicated boxes on ServerBeach go down for the same reasons: hard drive failure, power outages, hurricanes, etc. And I don't have anyone to help me bring them back up, nor the interest or capacity to build out redundant services myself.

My Heroku apps are down, but I can rest easy knowing that they will bring them back up with out an action on my part.

The cloud might not be perfect but the baseline is already very good and should only get better. All without you changing your business applications. Economy of scale is what the cloud is about.

I see your point, but who is uploading videos to Google then deleting the source? These services are for sharing and streaming, not archiving.

I don't work for Google but I do work on large scale data hosting. When you shut a service down you have multiple phases. Step 1, stop capturing new data. Google Video did this years ago and anyone truly invested in the service knew what was up back then. Step 2, pick a date to stop serving existing data. Step 3, wait for a very long time for more requests to get data back. It is crazy how and why these trickle in years after the fact. Step 4, delete data. I bet Google wont actually delete data for a very long time if ever.

Maybe step 2 is aggressive, but in my experience 90 days notice doesn't make a difference. Nobody does anything until the last few days if ever. You just have to draw a line in the sand.

It is very hard to shut a service down with any sort of usage, let alone Google scale usage. But very important to do from time to time. This is what I respect.

There is so much abandoned and bullshit video on there, it couldn't possibly be worth it.

Respect.

Edit: not a good comment for HN. More: it was a great service, and it had a good run. And mad respect for Google for running it well but shutting it down gracefully.

In thinking back, that's exactly why I picked 4.

I just clicked whatever was closest because I wasn't even thinking about the exercise.

No problem. Love the script.

If it's static, serve it directly from S3, and turn on cloudfront for even better delivery.

Congrats! I hope OKCupid still publishes those awesome posts about the statistics of dating, those are fascinating.

Companies reserve the right to fire customers. I respect this attitude.

This looks really great. Kudos to the designers and programmers.