5 ms·

I see anything that ties Go to a specific browser as a bad thing. Surely they should be browser agnostic if they want to encourage universal adoption of their l

by SeanDav 12y ago

I see anything that ties Go to a specific browser as a bad thing. Surely they should be browser agnostic if they want to encourage universal adoption of their language (or perhaps they don't really care about this)?

sqs 12y ago
It's just a tool that you can use to visualize Go internals. Nothing is tying Go to any browser.
groby_b 12y ago
1) 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 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-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/edit https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQt...