Can someone explain motivation for this? Why would someone need Go bindings for V8? What's the practical applications of this?
Not trying to be a jerk, just plain curiosity
Not trying to be a jerk, just plain curiosity
I have already replaced parts of our suite with components written in Go, but at this point I wouldn't port the pointy end because I don't want to loose the agility that Python allows. If I could spider/parse with JavaScript and at once exploit the Go performance and concurrency features, this would be very attractive.
Funnily enough, the previous incarnation of the same solution was written in C++ with a JavaScript run-time used in exactly the same way. It predates Node.js by some years.
Build bindings to system functions in Go (e.g. write the common parts of an app in JS, run it in V8, write platform-specific things in Go).
Write the next Node.js/Io.js in Go?
Sure, but you could already do that. There are several V8 implementations in Go you could use directly to invoke javascript code, but you'd have to pass values directly in and get return values directly out to interface between the two languages.
- Provide a scripting layer to an executable.
- Re-implement nodejs in Go ...
There are quite a few js engines/bindings already for go, like duktape, otto, go-v8, ...