A new way of blogging about Golang
blog.klipse.tech
A new way of blogging about Golang
1–8 of 8 posts
Re: A new way of blogging about Golang
#2So can anybody tell me if I can write a go app and run it in the browser yet.
Years ago people were talking about WASM, but did it every take off?
Re: A new way of blogging about Golang
#3Something to do with touch events not being handled properly maybe?
Re: A new way of blogging about Golang
#4This is cool. So can anybody tell me if I can write a go app and run it in the browser yet. Years ago people were talking about WASM, but did it every take off?
Re: A new way of blogging about Golang
#5On mobile, if I put the cursor on any word and press any key (even backspace), the word gets repeated at the current cursor position. Something to do with touch events not being handled properly maybe?
Re: A new way of blogging about Golang
#6This is cool. So can anybody tell me if I can write a go app and run it in the browser yet. Years ago people were talking about WASM, but did it every take off?
Re: A new way of blogging about Golang
#7On mobile, if I put the cursor on any word and press any key (even backspace), the word gets repeated at the current cursor position. Something to do with touch events not being handled properly maybe?
Re: A new way of blogging about Golang
#8This is cool. So can anybody tell me if I can write a go app and run it in the browser yet. Years ago people were talking about WASM, but did it every take off?
Miguel Liezun used yaegi https://github.com/traefik/yaegi compiled to WASM to let Klipse evaluate Go code snippets in the browser https://github.com/viebel/klipse/pull/393