Live data from Hacker News

GopherJS

github.com

11–20 of 42 posts

Re: GopherJS

#11
post #5

Most recent major GopherJS news: - 29 days ago, the support for blocking calls became default, without needing to mark with `//gopherjs:blocking`. This was the last "not-really-Go" thing you needed to do previously. [0] - There's a 1.0 milestone now, so Richard is getting closer to a 1.0 release. [1] - Also recently, added support to make GET, POST requests via "net/http" (in browser) by providing a `net.Transport` i…

Thanks, I missed [0] which really is awesome. Edit: just looked at the webgl links, which is sweet.

Re: GopherJS

#12
post #4

I'm somewhat disappointed this has nothing to do with Gopher. http://en.wikipedia.org/wiki/Gopher_%28protocol%29

Do you mind me asking why? I was going to implement the protocol as an intro rust project, but Wikipedia and others called it obsolete so I ended up falling back onto the familiar IRC bot. My interest is still piqued however...

Re: GopherJS

#13
post #7

I've used GopherJS. I actually gave a talk just this past week about full-stack Go[0] (ie, using Go for native mobile/desktop, and client-side web development in addition to server-side), and GopherJS was, unsurprisingly, a bit part of that. GopherJS works surprisingly well; the biggest issue for most people will be the unminified file size. But based on my initial profiling, between minifiers, caching, and the fact…

> the biggest issue for most people will be the unminified file size I wanted to write my validation logic in Go and use that at the client side too, in a React app. Size was indeed my biggest problem. Gzipped size was around 60KB, and that's after the closure compiler advanced level minification. It would make sense if the whole app was being written in Go but having a JS channels implementation transferred through…

I still think gopherjs should emit code compatible with and annotated for the google closure compiler. The fact that go programs have all source present, and are statically typed, means it could emit some tiny code.

Re: GopherJS

#15

I've used GopherJS. I actually gave a talk just this past week about full-stack Go[0] (ie, using Go for native mobile/desktop, and client-side web development in addition to server-side), and GopherJS was, unsurprisingly, a bit part of that. GopherJS works surprisingly well; the biggest issue for most people will be the unminified file size. But based on my initial profiling, between minifiers, caching, and the fact…

> My hope is that the next client-side MVC/MVVC/etc. framework will be written in Go from the start.

A friend and I are working on exactly that! It's called humble: https://github.com/soroushjp/humble. We took a lot of inspiration from backbone and react. Still in an experimental phase and hasn't been touched much since we built it for the Gopher Gala, but we have plans to work on it a lot more in the future. There is also https://github.com/gowade/wade.

Re: GopherJS

#16
post #12
post #4

I'm somewhat disappointed this has nothing to do with Gopher. http://en.wikipedia.org/wiki/Gopher_%28protocol%29

Do you mind me asking why? I was going to implement the protocol as an intro rust project, but Wikipedia and others called it obsolete so I ended up falling back onto the familiar IRC bot. My interest is still piqued however...

Historical interest, mainly. Gopher is still used, but not by any large number of people; however, it occupies an interesting place in the history of the Internet as the main implementation of the idea of hypertext before the Web caught on.
Post reply on HN