4 ms·
I think this is awesome! As John Carmack said [1], you can hop in and enjoy in seconds. What is even cooler, IMO, is that you don't necessarily have to write J
by shurcooL 12y ago
I think this is awesome! As John Carmack said [1], you can hop in and enjoy in seconds.
What is even cooler, IMO, is that you don't necessarily have to write JavaScript and target WebGL only to get your game to work in the browser. You can write using Go and use packages with 2 backends, WebGL/OpenGL and GLFW/Canvas, to abstract out the platform differences behind a common API.
Then your game can be a single codebase that can either run as a native binary on desktop, or inside the browser.
See a working demo of what I'm describing here:
https://github.com/shurcooL/play/commit/e53557dd9c070ce0ec5251108249e5fa85333ae0#commitcomment-9101168 https://github.com/shurcooL/play/commit/e53557dd9c070ce0ec52...
[1] - https://twitter.com/ID_AA_Carmack/status/553720089674260480 https://twitter.com/ID_AA_Carmack/status/553720089674260480
- tesmar2 12y agoGiven Carmack's view of JS, I am surprised he was so positive. Good for him!
- deleted 12y ago[deleted]
- jokoon 12y agoI don't understand when you say "you don't necessarily have to write JavaScript and target WebGL only to get your game to work in the browser" What is deployed then ? Is an executable deployed ? Is it something like nacl, or asm.js ? Or does the user have to install an executable on his system ?
- ewindisch 12y agoThe parent was referring to using gopherjs to compile golang code to Javascript.