Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
trailfox
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
121.
▲
by
trailfox
13y ago
Why not "Ivory Coast Bus Routes Redrawn using Cell-Phone Data" ? As someone living in an African country I find this headline beyond ridiculous. If this was in Lebanon would we be reading "Asian Bus Routes Redrawn using Cell-Phone Data"?
122.
▲
by
trailfox
13y ago
> Wouldn't you want to use a language that is familiar in a competition? If Ruby is your forte, surely you should use it? If you're familiar with knives why not bring a knife to a gun fight? If knives are your forte, surely you should
123.
▲
by
trailfox
13y ago
From the post... Running time: Ruby: 3180 seconds Ruby (profiled and optimized): 342 seconds Go (first attempt): 0.7 seconds
124.
▲
by
trailfox
13y ago
Bingo :)
125.
▲
by
trailfox
13y ago
I consider myself very fortunate to be coding in Scala. I know of many Java developers who code Java at work and wish that they could land a Scala job.
126.
▲
by
trailfox
13y ago
Wow. Wish I could deploy this sort of tooling behind a firewall.
127.
▲
by
trailfox
13y ago
Mostly because the Java syntax has remained (mostly) unchanged since September 2004. Java 8 will change that, but it's still a far cry from what's available in Scala.
128.
▲
by
trailfox
14y ago
Curious. I wonder how far back it goes.
129.
▲
by
trailfox
14y ago
Go typically requires 2-4 times less code to do the same thing: http://benchmarksgame.alioth.debian.org/u32/benchmark.php?te...
130.
▲
by
trailfox
14y ago
I think the part you are missing and what Whatsapp's engineers are referring to is Google storing all your private conversations and data mining them for information to target you with ads. Whatsapp does not store your messages.
131.
▲
by
trailfox
14y ago
Why would anyone want to use gtalk over whatsapp? Unlike GTalk whatsapp doesn't store and data mine my conversations for targeted advertising. Source: http://www.whatsapp.com/faq/en/general/21864047 "We do not store your chat history on
132.
▲
by
trailfox
14y ago
No ads.
133.
▲
by
trailfox
14y ago
Robert Griesemer http://research.google.com/pubs/author96.html
134.
▲
by
trailfox
14y ago
Thanks, the 32 bit results on quad core are Go 1.1 beta: http://benchmarksgame.alioth.debian.org/u32q/benchmark.php?t...
135.
▲
by
trailfox
14y ago
Good point. It turns out that the quad core benchmarks on 32bit which I linked to are already using Go 1.1beta, so any speed gains for Go 1.1 are already factored in: http://benchmarksgame.alioth.debian.org/u32q/benchmark.php?t... The 64
136.
▲
by
trailfox
14y ago
I've seen posts where "it's from Google" is cited as sufficient explanation for taking an interest in the language. If Go was a random project on GitHub there is very little chance that I would have given it a second look, let alone learnin
137.
▲
by
trailfox
14y ago
Those serious about Go are running (production?) systems using pre-release builds? Is that a common practice?
138.
▲
by
trailfox
14y ago
The quad core results indicate the exact opposite in terms of performance with the JVM clearly ahead: http://benchmarksgame.alioth.debian.org/u32q/benchmark.php?t... Go uses less memory than Java 7, but then again so does Java 1.1
139.
▲
by
trailfox
14y ago
I agree that his comment need to provide more data. I also find that HN in general is very quick to downvote comments critical of Go, even well reasoned ones with sources. In terms of performance data check out quad core results for Go 1 (g
140.
▲
by
trailfox
14y ago
For most applications the startup time is irrelevant. The startup time of a server app which runs for months is not an interesting data point. The throughput in requests per second is far more important and this is where the JVM has been ve
141.
▲
by
trailfox
14y ago
Thanks for the explanation. In most cases cleanup is handled in finally blocks and the unit of work fails if any of N calls fails, in most case it makes no difference which one failed. Where the difference does matter it's probably in a dif
142.
▲
by
trailfox
14y ago
Thanks, I've added the link now.
143.
▲
by
trailfox
14y ago
It seems silly to have to check the error return code with an if for every method I call. Surely a try { } catch around a block makes more sense than littering my code with if (errorHappened) in every second line.
144.
▲
by
trailfox
14y ago
Curious downvote for a factually accurate post... source: http://benchmarksgame.alioth.debian.org/u32q/benchmark.php?t...
145.
▲
by
trailfox
14y ago
So if I'm reading from a file I should use panic recover and not return code checking?? That's not what I've seen in the docs.
146.
▲
by
trailfox
14y ago
Interesting, I hadn't heard of it before: http://nimrod-code.org/
147.
▲
by
trailfox
14y ago
I'm interested to see if it is still going to be clobbered by Java and Scala the way Go 1 was.
148.
▲
by
trailfox
14y ago
Lack of exception handling is the biggest reason I haven't used Go for much. The other reasons are that it's just so plain/boring (yes, I know that's subjective), nothing about the syntax is interesting. Learning go is like eating cardboard
149.
▲
by
trailfox
14y ago
Javac also takes longer than Turbo Pascal to compile...
150.
▲
by
trailfox
14y ago
Netty has become the standard library for NIO on the JVM and is used widely by programmers in various JVM languages. It's also refreshing to see high performance NIO systems written without using Netty for a change.
More ›