[links] Links and javascript

[Karel Kulhavy]

On Sun, Apr 15, 2007 at 09:07:17PM -0400, Philip Ganchev wrote:
> On 4/15/07, Mikulas Patocka <mikulas at artax.karlin.mff.cuni.cz> wrote:
> [...]
> > > How about if we start a fund or a bounty for javascript on Links?  How
> > > much do you think it would cost to have it implemented?  The Links
> > > Development page (http://links.twibright.com/development.php) shows
> > > some prices in the thousands. I'll start by offering a modest US$100
> > > and increase that if there is need and other people pitch in.
> > >
> > > I think there is even a website that facilitates this process for FOSS
> > > but I can't find it.
> >
> > Hi
> >
> > I have no time for it, but if you find someone who has, you can pay him.
> 
> Any chance we can use the Links website to advertize that, for example at
> http://links.twibright.com/development.php ?  I guess that this is the
> most likely to find someone interested.

On Ronja I have policy that I encourage donations only for things which are new
features. I consider bugfixes my fault and do them for free. Even bugfixes
that mean redesigning a whole module from scratch, which already happened
once and half times, are bugfixes, and therefore for free. I don't think it
would be appropriate to expect donations for a bugfix.

I think this is a reasonable policy for the whole Twibright Labs label. If we
behave like pigs, people stop trusting Twibright Labs. The advantage of
Twibright Labs branding is when someone uses one product (e. g. Ronja) and sees
how we strive for quality, he will automatically assume the same level of
quality in other products (e. g. Links).

The general problem is that often you have 10 programs that solve one problem
and you don't know which of them really work and which are crap. And trying
that out takes a lot of time. That's the purpose of the Twibright Labs branding
- this helps you to get some idea about quality.

I think better having a reliable browser without Javascript than a crappy
browser with Javascript, when we don't have enough resources to fix it.

If someone has a lot of time he can take PerM's code, refactor it so it's more
understandable and fix all the bugs. It's just labour intensive I guess.

CL<
> 
> Another idea is Google Summer of Code, but that would need someone to
> supervise a student, and the best person would be someone who has
> worked on Links before.
> 
> 
> > I am removing javascript right now --- I left the hooks there (file
> > jsint.c), so you can just take spidermonkey or whatever javascript
> > interpreter, call it from jsint_execute_code and do callbacks to jsint.c
> > file --- this will just get form editing, url redirection, image
> > replacement and similar Netscape 3 stuff working. Doing DOM is hard to
> > impossible.
> 
> OK.
> _______________________________________________
> links-list mailing list
> links-list at linuxfromscratch.org
> http://linuxfromscratch.org/mailman/listinfo/links-list