thoughts…

rants and bookmarks about programming stuff…

Tag Archives: google


by

Go 1.1 performance improvements

“This is the first in a series of articles analysing the performance improvements in the Go 1.1 release.

It has been reported (here, and here) that performance improvements of 30-40% are available simply by recompiling your code under Go 1.1. For linux/amd64 this holds true for a wide spectrum of benchmarks. For platforms like linux/386 and linux/arm the results are even more impressive, but I’m putting the cart before the horse…”

http://dave.cheney.net/2013/05/21/go-1-1-performance-improvements


by

The Reliability of Go

“As part of the Canonical Cloud Sprint taking place in San Francisco last week I attended Dave Cheney’s talk at the GoSF meetup on the porting and extension of juju. Juju is an open-source cloud management and service orchestration tool that if you haven’t heard of yet, you soon will have.

After the talk an audience member asked if Go was reliable. Having used Go in production for coming up to three years now, without incident, this came as a bit of a surprise to me. Prior to moving to Canonical I worked for one of the UK’s largest market makers. A market maker is basically a wholesaler for institutional share traders and stock brokers. During my time there I replaced several key systems components with Go…”

http://andrewwdeane.blogspot.com.br/2013/05/the-reliability-of-go.html


by

How to Setup Two-Factor Authentication (Google Authenticator) for SSH Logins

“By default, SSH already uses a secure data communication between remote machines, but if you want to add some extra security layer to your SSH connections, you can add a Google Authenticator (two-factor authentication) module that allow you to enter a random one-time password (TOTP) verification code while connecting to SSH servers. You’ll have to enter the verification code from your smartphone or PC when you connect.

The Google Authenticator is an open-source module that includes implementations of one-time passcodes (TOTP) verification token developed by Google. It supports several mobile platforms, as well as PAM (Pluggable Authentication Module). These one-time passcodes are generated using open standards created by the OATH (Initiative for Open Authentication)…”

http://www.tecmint.com/ssh-two-factor-authentication/


by

Gmail and the GC

“Back in 2006 I was working on the Gmail team and we were undertaking a complete rewrite of the frontend code. Gmail’s original web client had strokes of genius in it but was getting really hard to maintain and was limiting new feature development.

The new version had a bunch of enhancements: including a robust request service, using both XHRs and Iframes (for incremental responses); there was an event driven store that abstracted the UI’s data access; we were now using templates that compiled to JS functions; and we were employing many other techniques that are now considered best practice, but at the time were in their infancy…”

https://medium.com/joys-of-javascript/6b1ea3ffca45


by

Thoughts on Go after writing 3 websites

“It’s easy to get excited about new technology like Go. The question is: how does it stand up to scrutiny after daily use?

I’ve written 3 web applications in Go, they’ve been running in production for over a month so I feel justified in publishing my opinion.

In the past I wrote web applications in Perl, PHP, Python (web.py, Tornado, App Engine) so those are the technologies I campare Go to.

Of the 3 websites, AppTranslator, is web service for crowd-sourcing translation for software and was written completely from scratch.

Fofou is a simple forum and is a port of an earlier version I did for App Engine. Finally, this web site is a blog engine (also a port of an earlier App Engine version).

One reason to migrate from App Engine to my own server was to save money. At my levels of traffic (~3 requests per second) I was paying ~$80/month, mostly for the frontend instance hours.

Another reason was to do more complex processing (App Engine is great as long as you don’t have to do something that App Engine doesn’t support).

Finally, I wanted to see how Go will handle a real life project. The best way to test a new technology is on a project with a predictable (and relatively small) scope.

All websites run on the same Kimsufi 24 dedicated server (which is pretty beefy for its $60/month price). I’m using latest Ubuntu for the OS…”

http://blog.kowalczyk.info/article/uvw2/Thoughts-on-Go-after-writing-3-websites.html

Follow

Get every new post delivered to your Inbox.

Join 516 other followers