marshalling

Often he's marshalling the same impatient sarcasm against the right as he more famously deploys against the left.

You have to do some data marshalling, but that's true of any dynamic language -> c binding.

When you consider that Erlang adds on top of this built-in marshalling and demarshalling of data structure.

The proper way to fix it is perhaps taking encoding/json sources and converting marshalling/unmarshalling code to use go-duktape Push/To/etc.

One lesson from QNX is that marshalling and interprocess communication should be separated if performance matters.

Not only marshalling/demarshalling of data, but fanning-in and then fanning out your concurrency on each end.

All you need is a shell capable of marshalling data between the different programs piped together.

In cases where it does not, they are essentially the same, possibly message passing being slightly slower due to marshalling/encode/decode overheads.

You run into similar problems when marshalling your objects to, say, a Thrift structure definition.

Note that all of the stores rely on Ruby marshalling underneath.

After all, the benefit of generics is that you do the work at compile time instead of runtime (no casting, data marshalling is tight, etc).

If you're using Readthis[0] for Redis caching you can use an alternate marshaller to avoid the size and performance overhead of marshalling all objects through Ruby.

If that its not the case, it will have to perform and extra deferred marshalling step to put the payload in "canonical" format prior to demarshalling proper.

In this sense Go kind of feels sad because []byte is far from having all the information you need, and if you want a "generic" B-tree that only handles []byte, you will waste a lot of time (un)marshalling.

Usually you can find ways to make them less necessary—IronRuby doesn't contain its own GC with Ruby semantics, it just translates Ruby's GCing requirements into calls to the CLR allocator+GC and the result works "well enough." > Not only marshalling/demarshalling of data, but fanning-in and then fanning out your concurrency on each end.

Marshalling a string object ref to an actual value (before it can be used for string manipulations internally) must incur a fair bit of CPU overhead.