djensen47

Here's a screenshot: https://plus.google.com/u/0/photos/photo/1057573952975799919...

It's not impossible to detect passenger vs. driver, it's just not easy. ;-)

Now this looks like a great project worth supporting. C'mon Hacker News folks, let's support this project!

The website says it is "not released yet" but the concept seems quite straightforward. It uses PhantomJS to render the complete page and return it to GoogleBot.

The only issue I could see with this are slow response times because Google penalizes sites for being "slow." But definitely something to keep an eye on and/or contribute to.

And yet so many sites are still not mobile friendly and even some of the ones that are do it all wrong.

- Please don't ask me to install your every time I visit your site on mobile (Yelp's experience on this is actually much better than average).

- Please do not automatically redirect me to the App Store.

- Please do provide all the content available on the desktop version otherwise I'm just going to have to go there anyway.

- When I click a Goole result for a page, I expect to land on that page or a mobile version of that page. Please do not send me to a mobile landing page where I can't get the info I originally wanted.

The demos are super slick and make it seem like a huge productivity saver. When I first looked at it, I had to dismiss it on the sole reason that it could not be crawled by Google and therefore not SEO friendly. However with Meteor 0.3.9 (back in August) that problem was solved.

Looks like a great tool to add to your continuous integration pipeline.

What do you do when you're trying to explain a technical issue that can't be explained in 500 chars or requires code snippets? Maybe move to a different medium? A different email address?

A codepaste might work for snippets as long as it's not sensitive. You still might need a way to explain how to reproduce a problem.

Maybe these are all just add-ons for such a service.

I'm surprised this hasn't already been posted here. The article is a bit ranty (and humorous) at times but I think it makes a good case for why you should start your next project with Node.js instead of Rails.

Though I'm sure there's a lot in this presentation that was missed without the speaker but it was still a good read nonetheless.