ofrobots

4 ms·

1.
by ofrobots 7y ago
It made the back button useless for me.
2.
by ofrobots 10y ago
This profiler is sampling based. It takes a sample once every 512KiB allocated (on average, randomized) and reports all the allocations still alive at the end of the interval. So, yes it reports the subset of allocations that are sampled an
3.
by ofrobots 10y ago
Recent versions of Chrome DevTools have a new profiling feature called 'Record allocation profile' that may help. Enable this around a few of the sawtooth and it will give you a profile based on a sampling of allocations that happ
4.
by ofrobots 10y ago
The plan is for a Node.js 6.0 release on Tuesday: https://github.com/nodejs/node/issues/5766#issuecomment-1983... . This would include V8 5.0.
5.
by ofrobots 10y ago
To be precise, Node.js 6.x will include V8 5.0. There has been a little discussion on being able to include V8 5.1 down the road, maybe, but there is nothing concrete on it at this point. Also, the fate for tail-call-elimination is pretty u
6.
by ofrobots 11y ago
> 1 line of COBOL Offtopic, but this would be quite a challenge.
7.
by ofrobots 11y ago
Never use a single workload as a predictor of performance of the universe of all other workloads. The best benchmark is not a benchmark at all – it is your actual workload.
8.
by ofrobots 11y ago
Yeah, 'ship' means different things in different contexts. In the context of your original comment, node stable is getting arrow functions within a week of Chrome stable getting them. In general, io.js has been very good at pickin
9.
by ofrobots 11y ago
This is not really accurate. Arrow functions shipped in Chrome on Tuesday (Sep 1) with Chrome 45 (V8 4.5).
10.
by ofrobots 11y ago
Congrats on the public announce of your 'secret' project! When do you release the code publicly? It would be great to be able to hack on it again.