Sony Ericsson explains why customers shouldn’t expect them to ready with an ICS update any time soon:

Many operators also want to customise the software according to their requirements, which in turn are based on their market, network, differentiation and business model. We implement all of these customisations and create a variety of software packages and releases for each operator.

This is just insane. It’ll be months before anyone sees ICS updates on their phones.

Sony Ericsson goes to great lengths to explain that they also need to replace the default Android “graphics” with their own. Why bother?

My wife got received a Galaxy Ace on her contract upgrade but was given a Nexus S by a friend. These phones are both made by Samsung. The Nexus S is an “Google-experience phone” which runs a unadulterated build of Android.  The Ace, however, is loaded to the brim with Samsung’s silly “TouchWiz” UI and bloatware applications.

The result is a sub-standard Android experience on non-Google phones. It lowers the tone of the entire platform, and reduces its attractiveness to developers.

This is the fundamental difference in approach between Apple’s iOS and Google’s Android.  Apple doesn’t care about carriers and what they want. Android handset makers survive at the mercy of the carriers.

Am I missing something, or is Twitter testing their web interface on Google AppEngine? I seriously doubt it… I guess this is just some hacked up transparent redirect to twitter.com?

In contrast to a week allegations of “internecine warfare among Microsoft’s established divisions and a dysfunctional corporate culture that squashes innovation” comes yet-another-innovative-Google-product, Google Buzz.  Google Buzz is Mountain View’s first convincing entry into Social Networking, that isn’t limited to merely an API.

Gina Trappani, posting on Smarterware, says it all: “This ain’t no Orkut.”. Google are very serious about taking down Twitter and Facebook.

Jason Calacanis, posting to his email list this morning, made it clear that he sees this as a major challenge to facebook:

1. Google Buzz 1.0 is better than Facebook after six or seven years.

2. Facebook’s history is one filled with stealing other people’s
innovations and doing them better (i.e. Zuckerberg has stolen every
idea Evan Williams and the Twitter team have released). How ironic now
that Google has out “Facebooked” Facebook. Google

3. Google has excellent privacy record and Facebook is a disaster.
Most folks do not trust Zuckerberg and Facebook any more because of
their privacy record (filled with lawsuits) and because they steal
every good idea they see (i.e. Twitter’s innovations and FourSquare’s
checking in).

4. Google Buzz auto generates your network–this is MUCH better
process than Facebook’s.

5. Google Buzz is way faster than the sluggish Facebook–this is a
HUGE advantage.

6. Google Buzz puts relies and updates into your GMAIL as
threads–this is BRILLIANT and a HUGE advantage.

Perhaps Jason is spot on. It certainly does seem that Google has almost everything in place to flip the switch, and take over the Social Networking space.

• Status
  Google: Buzz Status and GTalk Status
  Facebook: Status
• Photos
  Google: Picassa,
  Facebook: Photos
• Videos
  Google: YouTube,
  Facebook: Videos
• Email
  Google: Gmail since 2004
  Facebook: Project Titan (not yet released)
• Instant Messaging
  Google: GTalk with XMPP/Jabber
  Facebook: Facebook Chat (XMPP just released)
• Applications
  Google: Not yet.
  Facebook: Farmville, and a few others.
• Media Sharing
  Google: Google Reader, YouTube
  Facebook: A mix of rss importing tools, and (possibly) the recently purchased FriendFeed.

The only problem, in the words of the imitable Reinhardt Zündorf, is: “This is lame, now I can’t find out which dog I am (via a five bullet questionnaire) and share it with my facebook friends”.

Google is touting its new Go language as a modern systems programming language which is expressive, concurrent, garbage-collected. Go takes the development speed of working in a dynamic language like Python, and combines it with the performance and safety of a compiled language like C or C++.

In its Go FAQ, Google explains the main motivations behind the project:

No major systems language has emerged in over a decade, but over that time the computing landscape has changed tremendously. There are several trends:

• Computers are enormously quicker but software development is not faster.
• Dependency management is a big part of software development today but the “header files” of languages in the C tradition are antithetical to clean dependency analysis—and fast compilation.
• There is a growing rebellion against cumbersome type systems like those of Java and C++, pushing people towards dynamically typed languages such as Python and JavaScript.
• Some fundamental concepts such as garbage collection and parallel computation are not well supported by popular systems languages.
• The emergence of multicore computers has generated worry and confusion.

Bold words from Google, especially considering the number of new languages which have come and gone over the years. Surely its too risky to put the corporate name behind the project? Not once you hear who’s on the team.

The project is being staffed by some serious Computer Science heavyweights: Robert Griesemer, Rob Pike (Unix Team, Plan 9 OS, UTF-8, Inferno), Ken Thompson (inventor of B – forerunner of C, UTF-8, shepherd Unix and Plan 9), Ian Taylor, Russ Cox, Jini Kim and Adam Langley.

Coming from a C/C++ background during my university days, my first Go experience felt quite nostalgic. I grabbed the source via Mercurial, compiled it in the Terminal, and configured some shell environment variables. What I was left with was a native Go compiler for my x64 architecture (6g) and a Go linker (6l). These are the recommended compilation tools until the GCC-based (gccgo) version catches up.

Installation on Snow Leopard

Before you follow these steps, you should have XTools installed. You should also be running Snow Leopard as your OS. These instructions should also work for 10.5 Leopard, but you may have to use GOARCH=386.

Environment

Go needs a couple of shell/environment parameters to be set prior to installation.

Add the following lines to your ~/.bashrc file:

export GOROOT=\$HOME/Go
export GOOS=darwin
export GOARCH=amd64
export GOBIN=\$HOME/bin

Now use the source command to apply those changes:

source ~/.bashrc

Next we need to add the bin directory for Go, and map it on the system path:

mkdir -p $HOME/bin
echo "$HOME/bin" > go
sudo mv go /etc/paths.d/
eval `/usr/libexec/path_helper -s`

Source Code

The Go team are currently using Mercurial to handle the source code. If you don’t already have it installed, you can install it quickly and easily with the following command:

sudo easy_install mercurial

I encountered an issue whereby UTF-8 was not set as my locale language type. While some will not experience this, I had to force this by adding the following lines to your ~/.profile file:

export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

Adjust according to your locale, if neccesary. Big thanks to ricafeal for this.

This will use the Python easy_install tool to install the mercurial package on your system. Once complete, its time to checkout a copy of the Go source code:

hg clone -r release https://go.googlecode.com/hg/ $GOROOT

This will place a full directory of Go source in the directory defined in ~/.bashrc as $GOROOT

Installation

All the Mac OS X particulars are done and you can follow the standard installation procedure. That includes:

cd $GOROOT/src
./all.bash

If you get a message stating…

--- cd ../test
N known bugs; 0 unexpected bugs

… you should be good to go (oh the puns).

Hello World

package main
import "fmt"
func main() {
fmt.Printf("hello, world\n")
}

To compile:

$ 6g hello.go
$ 6l hello.6

To execute:

$ ./6.out
hello, world

You may also want to check out Jeremy’s great little script which lets you compiler (6g) and ink (6l) in one, well, go.

More Go later this week!

Historically, I’ve kept my feeds in Apple’s Mail.app. However, I’ve recently found myself wanting to catch up on RSS when I’m in the car or at the gym. I needed a way to move from Mail to Google Reader.

The trouble is, Apple doesn’t have a way for you to export your RSS links our of Mail (as text or OPML). Thus, I turned to the Google, and found a fairly simple solution:

1. Export the RSS feeds as URL links in plain text (Mac OSX Leopard-only). This bash link places the export on your desktop.
   

   IFS=$'\n';for i in $(find ~/Library/Mail/RSS/ -name "Info.plist");

   do grep "http://" $i | sed "s/.*\(http[^<]*\).*/\1/" >> ~/Desktop/Mail\ Feeds.txt;done

2. Convert to from Plain Text to OPML. I used the excellent converter at http://unold.dk/code/opmlgen/ (Dead-link, update thanks to commenter Tom: http://reader.feedshow.com/goodies/opml/OPMLBuilder-create-opml-from-rss-list.php)
3. Import into GoogleReader!

Simple. I know have all my feeds in GoogleReader, and can access them whereever I am.

gDAY with MATE – Not bad
http://www.google.com.au/intl/en/gday/index.html

Gmail CustomTime – Quite Funny
http://mail.google.com/mail/help/customtime/index.html

Virgle – Clever, clever, clever!
http://www.google.com/virgle/index.html and http://www.youtube.com/user/projectvirgle

-Tim