I'm personally more excited about Rust. It is a true systems language with a modern type system, does away with the GC for more predictable performance and generally outperforms Go on CPU-bound tasks. It could actually become an interesting option for a highly parallel Parsoid 2.0 version once its 1.0 is out of the door. The Mozilla folks have built solid PEG and DOM libraries, which are important for that task.
In any case, I see little benefit in porting existing Node code to Go right now. The performance gains are marginal, and the cost of language fragmentation is real. We have a large number of JS developers, and it looks like the web is not going to move away from JS any time soon. Modern JS with promises and generators is also quite a bit nicer than old-style callbacks, and we are seeing speed-ups of around 10% with io.js. Gabriel PS: Wikia are building an auth service in Go <https://github.com/Wikia/helios/>, but have otherwise standardized on Java for now. On Thu, Jan 29, 2015 at 7:21 PM, Ori Livneh <[email protected]> wrote: > (Sorry, this was meant for wikitech-l.) > > On Thu, Jan 29, 2015 at 7:20 PM, Ori Livneh <[email protected]> wrote: > > > We should do the same, IMO. > > http://bowery.io/posts/Nodejs-to-Golang-Bowery/ > > > _______________________________________________ > Wikitech-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
