[deleted]
GopherJS
21–30 of 42 posts
Re: GopherJS
#22I'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…
There's also Wade[1], maybe you can merge efforts?
[1]: https://github.com/gowade/wade
edit: I've just seen that you already mentioned it. I hadn't drunk my coffee then, sorry!
Re: GopherJS
#23I'm somewhat disappointed this has nothing to do with Gopher. http://en.wikipedia.org/wiki/Gopher_%28protocol%29
They are just a bit confused with naming there at Google: Go, Gopher, Golang etc.
Re: GopherJS
#24Any information on https://tardisgo.github.io/ ? They target Haxe, so I guess they have a bit more ambition, but it does mean a lot more moving parts. It looks like GopherJS is more mature, though.
Hi, I'm the author of TARDISgo.
Yes, GopherJS is not only more mature, it is also a really great project. If you want to target JS today, you should use it.
By contrast, TARDISgo not only targets JS, it also targets C++, C# and Java (plus some other minor languages). In addition it gives access to the rich Haxe cross-platform development ecosystem.
I am actively developing the project, but that work is not yet visible on GitHub because of breaking changes in the Haxe compiler. The project will get a major upgrade once it is stable with the new version of Haxe (3.2.0). This upgrade will raise the number of standard packages which pass their tests (for at least one target language) to 80.
Major announcements about TARDISgo will appear on twitter @TARDISgo. Please stay tuned!
Re: GopherJS
#25I used this once to port some math-heavy Go and both amazed and aghast when I saw how int64 values were handled in the resulting javascript.
Can you post an example? The playground doesn't seem to be working right now.
Re: GopherJS
#26Re: GopherJS
#27Re: GopherJS
#28Re: GopherJS
#29Any information on https://tardisgo.github.io/ ? They target Haxe, so I guess they have a bit more ambition, but it does mean a lot more moving parts. It looks like GopherJS is more mature, though.
Hi, I'm the author of TARDISgo. Yes, GopherJS is not only more mature, it is also a really great project. If you want to target JS today, you should use it. By contrast, TARDISgo not only targets JS, it also targets C++, C# and Java (plus some other minor languages). In addition it gives access to the rich Haxe cross-platform development ecosystem. I am actively developing the project, but that work is not yet visibl…
I am pleasantly surprised to find a Chinese sentence on the TARDIS Go website :) That sentence - "请发送一份汉语的电子邮件到作者" - is a perfectly comprehensible, but you can sound more Chinese. For the amusement of the Chinese-illiterate, I have included a word-by-word English translation of each sentence.
* Put the preposition phrase before the verb, which is the usual order. That turns "请发送一份汉语的电子邮件到作者" (please send a Chinese email towards author) into "请向作者发送一份汉语的电子邮件" (please towards author send a Chinese email). I have also changed the preposition from "到" to "向".
* Drop the unnecessary quantifier and "的". Chinese defaults on "a" most of the time, and "的" is often not needed for noun phrases. That turns "请向作者发送一份汉语的电子邮件" into "请向作者发送汉语电子邮件" (please towards author send Chinese email).
* Use "写" (write) instead of "发送" (send). The latter is a direct translation from English and not very native. Also "电子邮件" (email) can just be "邮件" (mail), especially when on-line. That turns "请向作者发送汉语电子邮件" into "请给作者写汉语邮件" (please towards author write Chinese mail). I have changed the preposition again, from "向" to "给".
* Prefer composite verb phrases over adjectives for describing means (here, the mail is written in Chinese). That turns "请给作者写汉语邮件" into "请用汉语给作者写邮件" (please use Chinese towards author write mail).
That's pretty it. Actually, "请用汉语给作者写邮件" is how I would write the sentence, and I figured out a path from your version towards mine :)
PS1. About the preposition changes - yes, "到", "向", and "给" all mean "towards" in this case, and I cannot really explain why I changed them. I can probably point to some literature if you are interested...
PS2. Another tiny detail: since you are already using the Chinese period mark "。" I recommend you also to use the Chinese question mark "？" in the previous sentence for consistency.
Re: GopherJS
#30I'm somewhat disappointed this has nothing to do with Gopher. http://en.wikipedia.org/wiki/Gopher_%28protocol%29
They are just a bit confused with naming there at Google: Go, Gopher, Golang etc.
Go is the language name, golang is the search-friendly alt, and "gophers" are the users of the language. Your apparent distaste for Google doesn't justify your mean attempts at humour.