News for hackers. Stuff that matters.
Re:GopherJS 1.7-1 is released by andrewstuart on Sunday August 21, 2016 @10:15PM (#12333718)
I had expected this to be a JavaScript implementation of Gopher. A little disappointed.
Re:GopherJS 1.7-1 is released by shurcooL on Sunday August 21, 2016 @10:20PM (#12333726)
Sorry about that. :) This does come up occasionally, but given that the gopher is the mascot animal for Go, this name has a nice ring to it once you're used to it, at least IMO.

Also reminds me of earlier days where people would talk about Go, I'd get excited and it turned out it was the board game not the programming language.

Re:GopherJS 1.7-1 is released by enneff on Monday August 22, 2016 @03:22AM (#12334642)
I always thought it was a clever play on "Go-for-JS". If not, you should change the backstory retroactively! ;-)
Re:GopherJS 1.7-1 is released by shurcooL on Monday August 22, 2016 @03:47AM (#12334717)
That is... genius!

Now that I think about it, I could've made this connection sooner. There's an (awesome) set of Go packages at go4.org, and the description text says:

> ... go4, go four, gopher... get it?

Re:GopherJS 1.7-1 is released by Jaruzel on Monday August 22, 2016 @04:25AM (#12334853)
> but given that the gopher is the mascot animal for Go

As it still is for the Gopher protocol, which predates the Go language by a couple of decades.

Maybe it's because I'm a Gopher (the protocol) advocate, but this theft of the Gopher mascot by the Go community continues to irk me... :)

Re:GopherJS 1.7-1 is released by acheron on Monday August 22, 2016 @02:22PM (#12338284)
See also "elm" the language or framework or whatever it is that gets featured on HN occasionally. Me every time: "Wait, like the mail client?"

Probably will continue to happen as old names are reused by people who never knew the originals.

Re:GopherJS 1.7-1 is released by simonsarris on Sunday August 21, 2016 @11:22PM (#12333906)
One of the lead devs of GoJS here (where Go is short for graphical object). Just wondering: did you consider using our name when starting the project?
Re:GopherJS 1.7-1 is released by shurcooL on Sunday August 21, 2016 @11:39PM (#12333961)
Good question. I only found out about the GopherJS project about a year after it was created, so you'd have to ask Richard for how he picked its name.

Looking at the first commit from Aug 27, 2013 [0], it was originally inside a folder "golang2js". The first mention of the rename to "gopher.js" is on Sep 18, 2013 [1]. It was also a transpiler rather than compiler originally, before it picked up more steam and started doing really sophisticated stuff to support all of Go's concurrency features.

Also, I've never heard of GoJS before today, so thanks for telling me about it! I guess I never tried to search for that term.

[0] https://github.com/gopherjs/gopherjs/commit/2f31215a988a07bc...

[1] https://github.com/gopherjs/gopherjs/commit/9223c657a92578ea...

Re:GopherJS 1.7-1 is released by cheriot on Monday August 22, 2016 @06:52AM (#12335372)
Has anyone gone the other direction? Javascript to Go. It would be cool to use Go for server logic and serve an isomorphic reactjs app.
Re:GopherJS 1.7-1 is released by xargon7 on Monday August 22, 2016 @09:35AM (#12336195)
Just this weekend I found this: https://github.com/olebedev/go-starter-kit

It uses the duktape JS engine in Go to render react apps server-side, with live-reload & hot-module replacement during development. Pretty cool!

Re:GopherJS 1.7-1 is released by fizzbatter on Monday August 22, 2016 @10:28AM (#12336547)
I'm actually quite impressed by that. I had looked into that a bit, but believed Ducktape & React to be too slow to be worth while. This is really interesting!