Dmitri Shuralyov

To update this issue with the latest PR status: the comment above is resolved in https://github.com/golang/freetype/pull/86#issuecomment-970275372.

Sorry for off-topic post, but I just really want to say this! @siongui, your blog and all the GopherJS-tagged posts are really really awesome! Nice work! I'll be sure to...

@siongui, is it okay with you if I add your GopherJS blog posts to a new "Tutorials and Blogs" section in the [GopherJS wiki](https://github.com/gopherjs/gopherjs/wiki)? You have the first one that...

Adding a data point observed in Git for Windows release notes [upcoming breaking changes](https://github.com/git-for-windows/build-extra/blob/76d6b0286c275eb445af2f4ab2fae41fe302341c/ReleaseNotes.md#upcoming-breaking-changes) section: > [...] Around the beginning of 2023, Git for Windows will drop support for Windows...

I don't think there's anything to do here for the Go 1.22 milestone. Moving to the next one.

@andydotxyz It could be convenient to use a go [workspace](https://go.dev/ref/mod#workspaces) for this. Try `go work init . ../glow` or something along those lines.

Thanks for reporting this. I'll take a look.

The documentation for `Query` currently includes: > q should be a pointer to struct that corresponds to the GraphQL schema. To make the snippet you've shown work as is, that...

> The issue is that data put into the history will be serialized by the browser. In turn, when you get it back out, you won't get an object of...

Following up here. @itsmontoya, have you seen my question in https://github.com/dominikh/go-js-dom/pull/35#issuecomment-268923431?