Hi Jon,

> I'm more uneasy with all that JavaScript code that comes with those
> buttons, especially the 181.1 KB of jQuery (v1.4.2) that turns up in
> @lib/socialshareprivacy/js.l. I have trouble understanding that an
> entire jQuery library is needed for those buttons to work. All that
> JavaScript code for just a few buttons doesn't feel right when used
> in company with "The Scalpel of Programming". Sorry for being so
> negative about this. ;-)

No, you are very right. I feel exactly the same about it.

Initially, I thought to recreate these buttons with PicoLisp on-board
mechanisms. However, I feel that it is more "right" to take these
"official" buttons, for example to spread this 2-click concept and its

And, of course, it would involve quite a lot of work to find out how
exactly they work, and how they communicate with the social networks
behind them.

And, third, I expect Heise Verlag to support these buttons in the
future, possibly supporting other networks and/or features. Keeping in
sync with that would involve even more work.

> I may not see the benefit of having those buttons at the bottom of
> every page in the PicoLisp Wiki. If they will generate increased

The overhead may not be sooo big as it looks like. The jQuery code is
loaded only once, and then cached in the browser.

The effort of including them into a PicoLisp project is also minimal. As
described in "lib/socialshareprivacy/README", you need to add only two
lines to a project.

> interest in PicoLisp, that is very fine, but will we/you be able to
> say whether they do so?

The initial reason was actually not the PicoLisp Wiki, but a commercial
project for which I'm requested to add such social buttons. It's just a
kind of by-product ;-)

- Alex
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Reply via email to