mcuadros
Go-Git has a new home v5 and some explanations
Show HN: Go-git v4, covering almost all the commonly used Git functionalities
Workdays vs. Weekends and Morning vs. Night GitHub Commit Analysis
Show HN: Kallax a PostgreSQL Typesafe ORM for the Go Language
Comparing Git trees in Go
Show HN: Proteus, keeping Go as the source of truth, .proto files from Go code
Show HN: High Performance and Large Scale K-means and K-nn on Nvidia GPU/CUDA
Show HN: Go-git and aerospike: a Git repository backed by a database
Show HN: Hercules – Calculates the lines burnout stats in a Git repository
Śiva: Why We Created yet Another Archive Format
Show HN: Ofelia – a simple job scheduler ready for Docker
Show HN: Golang fixed versions tool for your private and public dependencies
Show HN: Gce-Docker – Google Cloud Engine Integration for Docker
Show HN: Go-git – low-level and extensible Git client library in Go
With go-duktape, you can compile CandyJS just lake a normal Go package without any other tool or library.
Other reason is that many of the features are based on ECMA6 Proxy, something that is not supported on v8.
But the main goal of the project is be fully transparent more than the performance. At the very beginning I was making every case by hand but this is a endless work: https://github.com/mcuadros/go-candyjs/blob/54c8beb723aa8b1b...
I will take a closer look to the NaN issue and also a closer look to your code.
BTW I made a PR to go-duktape based on you fork: https://github.com/olebedev/go-duktape/commit/65f0be48ece4f6...
A good example could be a chan bot in Go with plugins written on JS. (like https://github.com/djosephsen/lazlo) but with CandyJS the effort to make this will be minimal, since you can use the same structures on JS and Go.
About the performance, CandyJS javascript is much slower than pure Go, since the reflection is very expensive.
A small quick bench of this example: https://github.com/mcuadros/go-candyjs/blob/master/examples/...
Pure Go: 165951 requests
CandyJS: 36304 requests
That means that CandyJS is 4,5 times slower than pure Go. Both
About the pool of workers, they share the stack? Or how you keep the same status on each.
BTW this behaviour is undocumented, I will fix that.