Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jterrace
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
jterrace
14y ago
Other output formats: http://jterrace.github.com/sphinxtr/ GitHub repository: https://github.com/jterrace/sphinxtr
32.
▲
Sphinxtr: Creating a Portable PhD Thesis
(jterrace.github.com)
93 points
by
jterrace
14y ago
|
73 comments
33.
▲
Comparing Image Comparison Algorithms
(jterrace.blogspot.com)
1 points
by
jterrace
14y ago
|
0 comments
34.
▲
How I Write LaTeX
(jterrace.blogspot.com)
2 points
by
jterrace
14y ago
|
1 comments
35.
▲
Gigabit Hack Weekend 3D Demo
(jterrace.blogspot.com)
1 points
by
jterrace
14y ago
|
0 comments
36.
▲
Sharing photos across social networks
(jterrace.blogspot.com)
1 points
by
jterrace
14y ago
|
0 comments
37.
▲
by
jterrace
14y ago
Yeah, I'm in no way proud of that beast of a code. There are a couple things at play here: 1. The js.js API is currently very low-level, which makes it verbose and difficult to use. There's a lot of room for improvement. 2. The twitter scri
38.
▲
by
jterrace
14y ago
The sandboxing of third-party scripts that we talk about in the paper ( http://www.cs.princeton.edu/~jterrace/docs/jsjs.pdf ) is one possible use case
39.
▲
by
jterrace
14y ago
This is because I'm converting to an i32 rather than a double. It should be able to be fixed relatively easily.
40.
▲
by
jterrace
14y ago
There's narcissus too ( https://github.com/mozilla/narcissus )
41.
▲
by
jterrace
14y ago
Hah, that's definitely not what I meant. It was in reference to the previous time js.js was (prematurely) posted to hacker news
42.
▲
JavaScript in JavaScript (js.js): smaller, faster, and with demos
(sns.cs.princeton.edu)
174 points
by
jterrace
14y ago
|
44 comments
43.
▲
URL Shortener Analysis - Tweets from 2009 vs. 2012
(ewencp.org)
13 points
by
jterrace
15y ago
|
10 comments
44.
▲
URL Shortener Analysis
(ewencp.org)
2 points
by
jterrace
15y ago
|
2 comments
45.
▲
by
jterrace
15y ago
We wanted the full power of the SpiderMonkey JS API and maximum browser compatibility.
46.
▲
by
jterrace
15y ago
Agreed, it's partially cheating, although a lot of work went into getting it to compile to LLVM and patching it work with Emscripten. That's not where it stops though. The plan is to make the library work just like the SpiderMonkey JS API,
47.
▲
by
jterrace
15y ago
Not quite. It will support everything that SpiderMonkey's API supports when embedding the interpreter into a C++ application. Much more powerful than eval().
48.
▲
by
jterrace
15y ago
65MB is our current unoptimized, uncompressed version. I expect the final version to be around 5-10MB. Still large, but not quite as bad.
49.
▲
Do you play WoW? Stanford and Princeton researchers need your help.
(reddit.com)
1 points
by
jterrace
16y ago
|
0 comments