jterrace

What kind of compression ratio do you get?

indeed :)

Aren't they both just modeled after the 2007 paper Events Can Make Sense that outlines Tame http://pdos.csail.mit.edu/papers/tame-usenix07.pdf

You're confusing the language with the build system. LaTeX wouldn't be very useful without the awesome build system. This project is a build system for producing both high-quality HTML and high-quality PDF (through latex) with a single, high-level ReST markup language. It also uses latex formulas for math.

You've never used ReST but you somehow know it's not good for typesetting research papers?

It has inline math. I just forgot to add an example for it. If by IEEE style, you mean bibtex, then yes, you can easily swap the bibtex format.

Sure, but that's what the PDF format exists for.

You can cite a URL.

You can link to a section with a URL. No "section xyz" or "page n" needed.

Mathjax is very good at it too.

The HTML format does generate multiple pages for different sections and chapters, completely configurable. The format above is the singlehtml format where everything is on one page. I'd much rather have a link to a specific anchor tag on a page that goes directly to where I want than a citation to a page number on a 200 page document.

100% intentional

Agreed, but for my case, I didn't really care too much about the PDF output. The printed version of my thesis is going to sit in my university library untouched forever. I'm much more concerned with having a semantically correct, searchable, beautiful HTML output.

This is a nice project, but different goals. I don't want my HTML output to look like a PDF. I want it to look like a nicely formatted web document

To be fair, I only released it after my thesis was done :)

Yeah, my university formatting requirements are crazy also. This allowed me to have one source that outputs (nicely) to a bunch of different formats, including the university PDF requirement.

This uses an existing format, restructuredtext, not a new markup format.

Pull requests accepted :)

It's using http://code.google.com/p/latex-makefile/ which is a really awesome makefile. It has nice colored output and throws away all the garbage output.

it had to be done

intentional :)

Other output formats: http://jterrace.github.com/sphinxtr/

GitHub repository: https://github.com/jterrace/sphinxtr

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 script was actually chosen because it's complex. It has a ton of boilerplate code that you'd probably be surprised is in there.

3. A lot of the code written could be generalized into a generic virtual DOM interface library that is not specific to this twitter script. Things like screen.width and screen.height are common properties that would be accessed by many different scripts and so could be generalized.

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

This is because I'm converting to an i32 rather than a double. It should be able to be fixed relatively easily.

There's narcissus too (https://github.com/mozilla/narcissus)

Hah, that's definitely not what I meant. It was in reference to the previous time js.js was (prematurely) posted to hacker news

We wanted the full power of the SpiderMonkey JS API and maximum browser compatibility.

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, which will require wrapper scripts in JS.

Not quite. It will support everything that SpiderMonkey's API supports when embedding the interpreter into a C++ application. Much more powerful than eval().