Profile cover photo
Profile photo
Evan Farrer
142 followers
142 followers
About
Evan's posts

Post has shared content
This is great news. This is why we need more than one viable browser. Competition is good for the consumer.
One of the big complaints about Chrome currently is that it's a battery hog, especially on Mac where Safari seems to do better.

The team has been working on addressing this; here are some cases that have recently been improved on trunk:

http://crbug.com/460102

Before: Renderers for background tabs had the same priority as for foreground tabs.
Now: Renderers for background tabs get a lower priority, reducing idle wakeups on various perf test, in some cases by significant amounts (e.g. 50% on one test).

http://crbug.com/485371

Before: On a Google search results page, using Safari's user agent to get the same content that Safari would, Chrome incurs ~390 wakes over 30s and 0.3% CPU usage vs. Safari’s 120 wakes over 30s and 0.1% CPU usage.
Now: 66% reduction in both timer firings and CPU use. Chrome is now incurring ~120 wakes over 30s and 0.1% CPU use, on par with Safari.

http://crbug.com/489936

Before: On capitalone.com, Chromium incurs ~1010 wakeups over 30s vs. Safari's ~490 wakes.
Now: ~30% reduction in timer firings. Chrome is now incurring ~721 wakeups over 30s.

http://crbug.com/493350

Before: On amazon.com, Chromium incurs 768 wakups over 30s and consumes ~0.7% CPU vs. Safari's 312 wakes over 30s and ~0.1% CPU.
Now: ~59% reduction in timer firings and ~70% reduction in CPU use. Chrome is now incurring ~316 wakeups over 30s, and 0.2% CPU use, on par with Safari at 312 wakes, and 0.1% CPU use.

The Chrome team has no intention of sitting idly by (pun intended) when our users are suffering.  You should expect us to continually improve in this area.

Post has attachment
If you've ever complained about error handling in golang this is the article for you. In many cases error handling in golang may appear cumbersome simply because you are not thinking like a golang developer.

Post has attachment
When I first started using Go I was mainly using C/C++. Now I use Python for my day job. Some observations on using Go for a "scratch an itch" project now that I'm accustomed to Python. I'd be interested in hearing others observations on going from Python to Go.

The observations:
http://evanfarrer.blogspot.com/2014/12/scratching-itch-with-golang.html

The project:
https://github.com/efarrer/adhoccasts

#Golang #Python

Post has attachment
Please add your name, or hire a lobbyist.

Post has attachment
Here's a fun little site that my friend started for people that could use a few more pleasant surprises in their lives. It seems like a great gift idea. https://www.sendmeasurprise.com/

Android app wish.

One of the annoying things about app slow rollouts is that you have no idea how long it will take for your device to get the update. While it makes a lot of sense for a developer to slow rollout an update, it would be nice as a user to at least know how far along in the slow rollout process an update is. It would be nice to have an app that would gather the OS version number along with the version numbers of all of your apps and then compare those versions with all others that are using that app on the same device and report back what percentage of devices are on a newer version. In other words I want a slow rollout progress bar for Android updates. It could also report back the location of devices, models and show a history of how long other slow rollouts have taken.

There have been conflicting reports on whether you need the updated Chromecast app for casting a screen. I haven't received the update yet but I was able to cast the screen from my Nexus4 from the settings menu. Just drag it down and select the "CAST SCREEN" icon and you're done. It works really well. I thought the performance would be worst than the OK performance of chrome tab casting, but it's much better. I even tried watching a Netflix video using the screen casting instead of the built in casting support and it works just fine.

Post has shared content

Post has attachment
T-Mobile and Net-neutrality

I love T-Mobile and how they're forcing change in how cell phone carriers operate. Getting rid of contracts, roaming charges, offering free data plans for tablets, no overage charges are all wonderful. I am, however, very concerned about their latest offering to allow you to stream music without having it count against your data usage. With this latest offering T-Mobile has moved against net-neutrality. The whole idea behind net-neutrality is that the network is dumb and treats all bits the same whether they come from Netflix, Vimeo or YouTube. This fosters competition by allowing customers to have equal access to all services and it allows services to compete based upon their service not upon whether they've struck a special deal with a carrier. T-Mobile has now chosen a favorite music streaming service Rhapsody, and several 2nd tier music services. If your not on that list you are at a competitive disadvantage to reach T-Mobile customers. The short terms gains of streaming music for free will result in the long term loss of competition. I ask all T-Mobile customers to join me in petitioning T-Mobile to roll back this plan and to fully support net-neutrality.

http://recode.net/2014/06/18/t-mobile-offers-music-streaming-free-of-data-charges/

http://en.wikipedia.org/wiki/Net_neutrality

Post has shared content
This is great. It won't be long before people realize they can draw more attention to the misdeeds of their ex's, political foes, etc. by filing a "Right to Be Forgotten" request with google. The media will pick up on it and wonder what someone is trying to hide and everyone will head over to google.com to see what's so shameful, that it must be hidden.
Just a little update on the EU Right to Be Forgotten ruling -- and why it's doomed to Streisand Effect glory!

Google has an "application" form up for EU residents who want to apply to have a search result removed. Using this form definitely does not guarantee that results will be removed, particularly if there is any public interest in those results. But here's the best part. Results will only be removed for the EU versions of Google. They will (of course, the EU doesn't rule the world!) not be removed from google.com. Additionally, when results are removed from EU versions, the associated results pages will reportedly contain a notice to EU users that results were removed (similar to the way copyright takedowns are handled now), and Chilling Effects-type reports will also apparently be made.

The implications of this gladden my "right to be forgotten" hating heart. If you're an EU user searching for Joe Blow, and the EU has forced removal of a search result related to him on, say, google.fr, the warning notice that results have been removed for that search give you an immediate cue that you might want to head over to google.com to see what the EU censorship bureaucrats deemed unfit for your eyes. In essence, it's a built in Streisand Effect! Before this, you might not even have noticed the result in question among other results. 

Censorship in the Internet age is a hopeless endeavor, as the EU is about to discover.

(I'm a consultant to Google, but I'm speaking for myself, not for them.)
Wait while more posts are being loaded