A propitious beginning. You'll need xorg-dev, libgl1-mesa-dev, and go-gl/glfw to install. Getting can't find "Arial.ttf" panics? But looks quite nice, though windows take some time to build. Here is a screenshot of "polygons" sample:
I'd love to see this evolve into something production worthy, even if it can't be done in idiomatic go style. A good cross platform GUI library is, to my mind at least, the largest void in an otherwise excellent standard library.
"..we need your permission to use and distribute your code. We also need to be sure of various other things—for instance that you'll tell us if you know that your code infringes on other people's patents.."
How can I know that my code doesn't infringes any other people's patents?does it apply if you are not is USA ?
That is a weird statement they make there, especially since the actual CLA as far as I understand it doesn't talk about that, it just includes provisions that you grant a license to all of your patents that the contribution would infringe.
[...] You hereby grant to Google and to recipients of software distributed by Google a [...] patent license [to use and distribute] the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted.
You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.
It doesn't require you to know if your code infringes patents, it just requires that IF you know, you disclose it.
This go submitted 19 hours ago https://news.ycombinator.com/item?id=9222587 and got no attention. It's now number #1 on github/trending. I believe it was not realized that this is coming directly from google.
Would be nice to know the background of the project.
Writing a UI library is not an easy thing.
Was it written from scratch, or some existing library was used as a reference? Had the authors had any background in developing UI engines? How long it took them to write this?
google hype tactics : "This is just an experiment to test concept feasibility", "This is unfinished, please consider that.", "This isn't a product, it's an experiment.", "Oh, it's just a side project of some employees, ignore that google owns it."
Seems entirely reasonable for these disclaimers to exist given that while Go is a legitimately open source project separate from Google, it is still strongly associated with Google in people's minds (not too surprisingly considering how many of the core Go team work at Google) and thus it wouldn't be hard to imagine some people getting the wrong idea of this somehow being Google's (or the Go team's) "official" answer to UIs in Go.
It did before, that was my bad. For me it makes a difference, even if they decline responsibility. Maybe they put it in the official account just to test the reception, and I for one would welcome an officially backed IU Go library with open arms.
http://imgur.com/9xyfaEd