[dev-context] yarv

Nikolai Weibull now at bitwi.se
Fri Mar 3 16:43:30 CET 2006

On 3/3/06, Hans Hagen <pragma at wxs.nl> wrote:
> Patrick Gundlach wrote:
> > Well, it is the opposite from what I've found out. Running rails:
> > yes, rendering dynamic stuff: no. So this is not really rails... and
> > not really usable. But I have no experience from myself. I'd love to
> > see that I am wrong. It might make some of my stuff faster.

> So how about nitro?
> Anyhow, from the perspective of running tex, those frameworks solve only part of the problem. I'm currently writing some web stuff and as usual the relative long tex runs have some session and caching demands that forces one to write quit esome code. A nasty characteristic of scripting languages is that chdir and env vars are global to the process, so threading multiple sessions using different tex trees and resource paths is possible, but a bit painful. For this I extended texmfstart a bit and  also a kind of texmf configuration system, but i need to document it .. .

Eh, sorry, but I wasn't trying to get into a discussion on
web-frameworks here.  I just said that YARV is on its way to becoming
the standard VM and it seems to be doing a good job at that.


More information about the dev-context mailing list