VRvruiz·Jul 8, 2015
changelog: https://tip.golang.org/doc/go1.5
It seems to me like they've included Google's trace viewer[0] into the go tool, nice.
[0]https://github.com/google/trace-viewer
In Go 1.5 Betagoogle
trace-viewer
OPEN SOURCE2014–2015
google / trace-viewer · Archived
trace-viewer
Discover this repository through its Hacker News conversations.
5Distinct people
5Mentions
0Explicit recommenders
488GitHub stars
What to know before exploring
What it is
A public description has not been verified.
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month5 dated mentions
Observed mentions: 2014-10-14 20:01:57 UTC to 2015-07-08 15:32:38 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Oct 2014 | 2014-10-01 00:00:00 UTC | 2014-11-01 00:00:00 UTC | 1 | 0 | 1 |
| Nov 2014 | 2014-11-01 00:00:00 UTC | 2014-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2014 | 2014-12-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2015 | 2015-01-01 00:00:00 UTC | 2015-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2015 | 2015-02-01 00:00:00 UTC | 2015-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2015 | 2015-03-01 00:00:00 UTC | 2015-04-01 00:00:00 UTC | 1 | 0 | 1 |
| Apr 2015 | 2015-04-01 00:00:00 UTC | 2015-05-01 00:00:00 UTC | 1 | 0 | 1 |
| May 2015 | 2015-05-01 00:00:00 UTC | 2015-06-01 00:00:00 UTC | 1 | 0 | 1 |
| Jun 2015 | 2015-06-01 00:00:00 UTC | 2015-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2015 | 2015-07-01 00:00:00 UTC | 2015-08-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
5 sourcesI think the tracing tool [0] isn't go specific but rather just a general tracing tool that's been maturing for a while. The support for outputting compatible traces is new to 1.5 AFAIK but that would explain how they have such a nice looking interface already :)
[0] https://github.com/google/trace-viewer
In The State of GoI agree, and that's what I was saying in the second paragraph (I've edited it a bit to try to make that clearer). This is definitely an improvement from that original language.
But I don't see how the original license was somehow worse than the open source projects that use the MIT or BSD licenses without any patent license, thus potentially allowing the patent owner to use patents against you offensively or defensively. (As far as I know, it is still unresolved whether the MIT or BSD licenses include an implied grant of patent rights, but at the very least there would be serious legal uncertainty.)
For one example, see the license on this Google project: https://github.com/google/trace-viewer/blob/master/LICENSE. No mention of patent rights, and unless you could successfully argue that there was an implied license, Google could sue a use
Read the rest
r for patent infringement for using this software (not that Google has ever used patents offensively, to my knowledge). So it confused me to see a Google employee complaining in the other thread that they weren't allowed to use Facebook open source software due to the limited patent grant. I'd be really interested to know more about this policy.
This is true for some projects, like Chromium and golang, but AFAICT not true for the majority of projects on that page. e.g. the currently most recently updated repo that doesn't have a "mirrored from..." subtitle is [1], and you can go see all the pull request activity on it (though I'm sure there are also lots of code dump repos in that list).
[1] https://github.com/google/trace-viewer
In Bidding farewell to Google Code1) It doesn't "tie" Go to anything - it uses Chrome for visualization purposes. You can write Go fine without ever touching Chrome.
2) Large parts of the trace viewer are separate from Chrome: https://github.com/google/trace-viewer/wiki
3) The event format is documented, so you're free to write an alternate viewer: https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQt...
In Brad Fitzpatrick on the future of Go