Inside the Go Playground

http://blog.golang.org/playground

by enneff • 13 years ago

92 14 13 years ago

blog.golang.org

mseepgood• 13 years ago

Runnable code in documentation, talk slides, blog posts and as a pastebin/playground is extremely convenient and user friendly.

ykumar6• 13 years ago

check out runnable.com :)

jbarham2• 13 years ago

And by the way, Go 1.3 will include support for Native Client (aka "NaCL").

Also: Russ Cox is the Chuck Norris of Go programming.

pokstad• 13 years ago

So this is how Go will make its appearance on Chrome Browser & Chrome OS? Pretty cool. I was a little scared off from NaCl from the C/C++ requirement, but Go will make that a little easier to handle. When is 1.3 suppose to be released?

jbarham2• 13 years ago

When is 1.3 suppose to be released?

Around 7 months from now according to http://blog.golang.org/go12.

kkowalczyk• 13 years ago

Not really, at least not in 1.3.

As http://golang.org/s/go13nacl describes, supporting Chrome is not a goal for 1.3 release, only being able to run nacl-sandboxed executables from command line.

AYBABTME• 13 years ago

Can you expand on the Russ Norris part? Just out of curiosity as I also have much respect for Chuck Cox.

jitl• 13 years ago

I'm very interested in the NaCl approach to server-side jails:

  > To isolate user programs from Google's infrastructure, the back 
  > end runs them under Native Client (or "NaCl"), a technology 
  > developed by Google to permit the safe execution of x86 programs 
  > inside web browsers. The back end uses a special 
  > version of the gc tool chain that generates NaCl executables

I'm a bit sad that the article didn't discuss using NaCl for constrained execution environments a bit more. Docker/linux containers are still a bit heavy-weight for low-budget ARM servers, and it'd be interesting to check out NaCl as a more lightweight, per-executable sandbox.

enneff• 13 years ago

I don't think the NaCl port will do ARM code generation.

I'll write more about Go's NaCl support once it's actually in the tree. :-)

comex• 13 years ago

I'm annoyed that NaCl's SFI is being repurposed so blatantly uselessly. The overhead isn't that much, but when seccomp provides equal or better security without any expense, it really seems like reinventing the wheel.

krasin• 13 years ago

It's always better to have multiple layers of defense. I won't be surprised, if Russ Cox has chosen sel_ldr_seccomp as the loader: https://src.chromium.org/viewvc/native_client/trunk/src/nati...

akanet• 13 years ago

If anyone's interested, https://coderpad.io has this exact feature as well - you can give an interview candidate a problem in Go, and watch them solve it in realtime. As you go, you can execute any of the code written so far.

My sandboxing uses Docker instead of NaCl.

thomasahle• 13 years ago

How do you handle things like filesystem, threading, networks and time?

ithkuil• 13 years ago

The time thing is ingenious. It reduces backend memory usage and allows caching.

However, it's possible to achieve the same advantage of cacheability, by executing a unmodified binary and recording the output in a time stamped manner, save it in a cache and replay it later.

Inside the Go Playground

Related Stories