Go 1.11: run Go in your web browser without compiling it to JavaScript
-
This is amazing and I have no idea what I can possibly use it for other than maybe writing a piece of software that does the "you can have JavaScript on the client AND the server" thing in reverse.
-
This release adds preliminary support for a new concept called “modules,”
Nuff said.
-
Something something js type system generics
-
@ben_lubar said in Go 1.11: run Go in your web browser without compiling it to JavaScript:
I have no idea what I can possibly use it for
This is how we all feel about Go.
-
@ben_lubar said in Go 1.11: run Go in your web browser without compiling it to JavaScript:
the "you can have JavaScript on the client AND the server" thing in reverse.
JavaScript on the server, Go in the browser? Why not Go everywhere? Traveling sounds fun.
-
@LB_ said in Go 1.11: run Go in your web browser without compiling it to JavaScript:
Go everywhere? Traveling sounds fun.
-
@ben_lubar
JavaGo Everywhere! I'm sure it'll work this time...
-
@lolwhat said in Go 1.11: run Go in your web browser without compiling it to JavaScript:
@ben_lubar
JavaGo Everywhere! I'm sure it'll work this time...I propose the name "gooplets" instead of "java applets".
-
@cvi said in Go 1.11: run Go in your web browser without compiling it to JavaScript:
@lolwhat said in Go 1.11: run Go in your web browser without compiling it to JavaScript:
@ben_lubar
JavaGo Everywhere! I'm sure it'll work this time...I propose the name "gooplets" instead of "java applets".
Does Go have beans yet?
Filed under: after 13 years of TDWTF I still don't know any meaning other than brillant.
-
@topspin they should be called Goblins.
-
Saw the title and thought, "oh, they added a WASM compilation target?" Opened the first link and... yep.
-
As a result of the addition of the new GOOS value "js" and GOARCH value "wasm", Go files named *_js.go or *_wasm.go will now be ignored by Go tools except when those GOOS/GOARCH values are being used. If you have existing filenames matching those patterns, you will need to rename them.
I have no words.
-
@CreatedToDislikeThis said in Go 1.11: run Go in your web browser without compiling it to JavaScript:
As a result of the addition of the new GOOS value "js" and GOARCH value "wasm", Go files named *_js.go or *_wasm.go will now be ignored by Go tools except when those GOOS/GOARCH values are being used. If you have existing filenames matching those patterns, you will need to rename them.
I have no words.
Yeah, implicit build tags are a dumb feature I wish they'd get rid of.
-
Go programs currently compile to one WebAssembly module that includes the Go runtime for goroutine scheduling, garbage collection, maps, etc. As a result, the resulting size is at minimum around 2 MB, or 500 KB compressed.
That's even bigger than an Ember site!
-
Rust's had this for a while now - there's a compilation target
wasm32-unknown-unknown
, thewasm-bindgen
crate, and a few crates that wrap it.
-
@ben_lubar said in Go 1.11: run Go in your web browser without compiling it to JavaScript:
Yeah, implicit build tags are a dumb feature I wish they'd get rid of.
Wait.
Criticism of Go?
And it looks non-sarcastic?
WHO ARE YOU AND WHERE DO YOU HAVE BEN LOCKED UP!?!? Oh his basement? Hm.
-
@blakeyrat said in Go 1.11: run Go in your web browser without compiling it to JavaScript:
his basement
Right, where else would he possibly be...
-
@lolwhat Thanks, yes, that was the joke.
-
@blakeyrat said in Go 1.11: run Go in your web browser without compiling it to JavaScript:
@lolwhat Thanks, yes, that was the joke.