Archive for June, 2012

Go programming language – a first impression – 1

I’ve been feeling I should try a new software development language for a while now, to see what life is like outside C++, C#, Java and Javascript. I had a toss up between Clojure, F# and Go. I discounted Clojure because it compiles to Java byte code and I want to stay out of the Oracle ecosystem. I slipped into Go over F# because I could do the Go example without having to get a Visual Studio add on (I know I could do F# from the command line, but I couldn’t be bothered) and the first example worked first time.

I’ve run though the tour and had a play with a few examples. I’m going to reserve judgement on the language itself until I’ve run though Effective Go and fully understood some of the concepts I think are important. In general the language seems very clean and concise (especially compared to Java). The usual problem exists that the main work would be learning all the new libraries and ways of doing things, if I actually had to do something complex, I’d fall back on a language where I knew where to find things (maybe F# would have been better in this regard) because the risk would be much lower.

Something that I think will limit the adoption of Go is the fact that it’s really hard to search for jobs in it (even on Google). I was having a look to see if there is any uptake of it, but trying to search for “go” on JobServe gets you a load of posts requiring “go getters” which is really not what I’m after. If you use “go language” or even “go programming language” then your targeted as a go getting translator! I don’t know if there’s some code in the industry to get round this, like calling it “Google_go”, but until I find the key, even if it’s ace, I’ll never be able to find a job or hire anyone.

Anyway, next time a real bash at the pros and cons.

Advertisements

A new record (for the Windcheeath)

I took the Windcheetah out round the test loop last night with it’s faring on and managed to get the fastest time on it so far. I’ve updated the ride log page with it and will hopefully add Brompton and RANS Cruz for comparison at some point.

I did have to stop for two “mechanicals” when the faring was starting to detach itself after bumps. I did stop the timer as I was slowing down and made sure I was moving at a decent speed again when I switched it back on, so I doubt it will have affected the average. I also stopped the timer a little early because of roadworks near the house which I ended up having to avoid on the pavement.

I forgot to take my heart rate monitor, so there is no way to see how hard I was trying, but I could hardly walk this morning if that’s anything to go by.

The Windcheetah seem faster down the hills, but about the same on the flat, through somewhat more comfortable than a TT position. It’s slow up the hills, but better recumbent legs would improve that situation.

Post apocalyptic cycling

I have been watching the post apocalyptic film The Road. It’s an allegorical story about a boy and his father trying to reach the coast while witnessing the barren world and humanity. Rather good actually in a depressing sort of way.

I know it’s nothing to do with the point of the story, but these two are walking and pushing their stuff around in an old shopping trolley, which can’t be helpful. If only they had had touring bikes with panniers (maybe even a trailer), they could have gotten to the coast easily (nice empty roads at the end of the world apparently). Also, bikes would have helped outrun the bands of cannibals, unless of course they were caught on a 25% uphill and chopped up looking like tits.

First 200k Audax

Completed my first 200k Audax ride. This is the one that was snowed off. After doing it, I’m glad I didn’t try it in the snow and -10 temperatures after dark on bike or trike.

The garmin report comes out to just under 200k (the route was planned as 210k), but I had technical trouble with GPS just before Cirencester and had to re-start it, but didn’t think to start the timer again until it tried to switch itself off sometime after Cirencester. You can see the straight line and the time vs elapsed time. Fortunately, there’s no quicker way than straight through Cirencester, so hopefully it will be approved.

I was worryingly in pain and exhausted by Oxford, which is less than half way, but a donner kebab seemed to perk me up. By Thornbury, I was terminally and crawled the final 10-15 miles. I didn’t embarrass myself too much against a cyclist on a race bike about 2 miles from the end, so I’m happy.

I find the balance between leg and arm pain difficult to manage. If my legs are tired, I can go for a more aero pose, but then my arms hurt more and vice versa. Think I will put the bars up a little higher, so the TT bar position is more comfortable, yet still pretty effective. I didn’t use the drops much, so having them a little higher will mean I can have some more variation.