Seems the original author is not around. I guess the design was not that expensive. The author is from Russia, where you can hire a free-lance designer for up to a $1k (for a single app).
Just keep in mind that Scala is not Ruby and the learning curve is quite high, which may slow the development down. But anyway, good luck. I also like Play a lot.
side project is actually a nice way to learn things, imho...I'm about to start a scala/play app for my startup-ish idea — killing two birds with one stone
This is an inspirational story! I'm currently working on a Siri-like app and hope I'll have a chance to write similar article :) I also have to say, that this website has amazing content and your article fits great into it! Good luck with the app!
Yup, code is broken. This is what I get —
go run test.go 'date' host1 host2
# command-line-arguments
./test.go:29: cannot assign *ssh.Signature to sig (type []byte) in multiple assignment
./test.go:45: undefined: ssh.ClientAuth
./test.go:56: undefined: ssh.ClientAuthKeyring
./test.go:79: undefined: ssh.ClientAuth
It depends on what you are trying to achieve. You can save the model by calling model.save(), but then you'd probably have to have a field which would point to the right collection.
I second the above: thanks for the article! Andrea, the quote you are citing means that all keys in the left sub-tree are smaller than the root's key and the ones in the right sub-tree larger. I think the sentence order chosen might be a little bit confusing, but it sounds like it matches what I have learned about search trees (not that this isn't arbitrary in the first place and would work just as well the other way around, too).
go run test.go 'date' host1 host2
# command-line-arguments
./test.go:29: cannot assign *ssh.Signature to sig (type []byte) in multiple assignment
./test.go:45: undefined: ssh.ClientAuth
./test.go:56: undefined: ssh.ClientAuthKeyring
./test.go:79: undefined: ssh.ClientAuth
My go version is 1.4rc2