Sami Vaarala

Currently only UTF-8 encoding is supported throughout the Buffer bindings.

This is a good place to ask re: development directions etc :) I've done a few incremental mark-and-sweep experiments - it's (naturally) feasible but not a trivial feature because it...

@beevik re: > But any objects that haven't been garbage collected (by refcounting) by the time mark-and-sweep happens will need to be considered by the mark-and-sweep algorithm, correct? In other...

I'll probably try that before rewriting the GC at some point. It would make the function `.prototype` a virtual property that gets only actually created when accessed (often it's never...

Agreed, it would be nice, and it's a common request in very low memory targets. One reason is that with pool-based allocators one tries to always serve allocations from pools...

The easiest way to see the number of objects and strings is to [enable debug prints](http://wiki.duktape.org/HowtoDebugPrints.html) and look for mark-and-sweep summaries at the end of mark-and-sweep, similar to: ``` D0...

@beevik @fatcerberus Revived some old testing of the on-demand constructor `.prototype` property here: https://github.com/svaarala/duktape/pull/1873. It allows refcount collection of anonymous functions in many cases, but is far from a silver...

@JoshMarler No worries, sorry for the delay (been quite busy lately with other stuff). At present there's no support for incremental mark-and-sweep and the best low latency solution is to:...

No update at present, i.e. CommonJS style modules are used.

Re: the worst case, it is dominated by native functions that can take an arbitrary amount of time. For example, the `String(arr)` here takes a long time: ``` var arr...