SmileyKeith

Yea that one is fine and well covered in the blog post, and pretty easy to spot in light testing. I'm much more worried about the ones that are harder to spot until you have a false negative that turns into a real bug which would be caught by 1 tool and not another.

Can you add some examples of the things users care about that aren't well covered by this? I empathize with everyone who wants a feature comparison chart so they can be confident switching without unknowingly losing important safety checks.

That has been there for a while so I think it's still an open question of if this change of strategy applies to that repo too

This isn't the primary part of this conversation but I found this quote pretty interesting:

> Now, we are starting to work on Safari again but look at Chrome. They put out releases at least every month while we basically do it once a year.

Even though this was in 2013 nothing about the release cycle (still only major changes with the major OS release versions). I wonder if some of the other emails have more context on this.

I've had similar problems contributing to bazel (Google's open source build tool) for the past few years. I've found contributing only goes smoothly if there is a single Googler working in your area who cares about open source. Otherwise everything is very Google centric and the open source community is definitely a secondary concern (which is of course their right!)

FYI your website's CSS on mobile causes unexpected horizontal scrolling issues

Daily. I find it a great way to follow many low frequency blogs without having to fill my twitter feed or email with them.

> Github seems to be primarily focused on becoming a social network

I never hit the GitHub.com homepage so I never see any of this work. I always start directly on a repo, notifications, or search.