update
I've created a little repository that simply exposes the final utility as npm
module.
It's called html-escaper
there is basically one rule only: do not ever replace one char after another if you are transforming a string into another.
update
I've created a little repository that simply exposes the final utility as npm
module.
It's called html-escaper
there is basically one rule only: do not ever replace one char after another if you are transforming a string into another.
Embedders of V8 should generally use the head of the branch corresponding to the minor version of V8 that ships in Chrome.
To find out what version this is,
Navigation and Resource Timing provides timing data for the fetch, but currently there is no interoperable way for the server to communicate own timing information to the client. For example:
<!--Page generated in X.X seconds.-->
, and many sites provide more detailed stats (cache, db, generation) to enable performance debugging.Instead of relying on arbitrary HTML comments, we can define an HTTP header that can be used to send key-value pairs in a well defined format. Making this data available via a well defined interface would...
The prep-script.sh
will setup the latest Node and install the latest perf version on your Linux box.
When you want to generate the flame graph, run the following (folder locations taken from install script):
sudo sysctl kernel.kptr_restrict=0
# May also have to do the following:
# (additional reading http://unix.stackexchange.com/questions/14227/do-i-need-root-admin-permissions-to-run-userspace-perf-tool-perf-events-ar )
sudo sysctl kernel.perf_event_paranoid=0
(function() { | |
// request PerformanceResourceTiming info for all resources on the page | |
var resources = window.performance.getEntriesByType('resource'); | |
// filter all resources to just +1 button iframes with timing information | |
var p1Resources = resources.filter(function(rtInfo) { | |
return rtInfo.name.indexOf('_/+1/fastbutton') != -1 && | |
rtInfo.responseStart != 0; | |
}); |
$ cat test.js | |
function foo () { while (true) { } } | |
function bar () { return foo(); } | |
bar(); | |
$ node test.js & | |
$ gdb attach $(pidof node) | |
0x00000bf778c63d5f in ?? () | |
(gdb) b v8::internal::Runtime_StackGuard | |
Breakpoint 1 at 0x84a1f0 | |
(gdb) print 'v8::V8::TerminateExecution'(0) |
sudo apt-get update | |
sudo apt-get install libfreetype6 libfreetype6-dev libfontconfig | |
# /etc/apt/sources.list should contain these: | |
# deb http://us.archive.ubuntu.com/ubuntu/ lucid multiverse | |
# deb-src http://us.archive.ubuntu.com/ubuntu/ lucid multiverse | |
# deb http://us.archive.ubuntu.com/ubuntu/ lucid-updates multiverse | |
# deb-src http://us.archive.ubuntu.com/ubuntu/ lucid-updates multiverse | |
sudo echo ttf-mscorefonts-installer msttcorefonts/accepted-mscorefonts-eula select true | sudo debconf-set-selections |
I have marked with a * those which I think are absolutely essential Items for each section are sorted by oldest to newest. Come back soon for more!
BASH
The spec has moved to a repo: https://github.com/defunctzombie/package-browser-field-spec to facilitate collaboration.