>
> I prefer to create a bulleted list like this:
>
>
> {% for item in listitems %}
> item.name
> {% endfor %}
>
>
>
Hmm, that looks like Django. Come to think of it, why use a high level
framework like that. Why not write plain sql statements, write plain
html, write your own authentication sy
>
> Interestingly with a distributed model, the notion of commit access may not
> be that important at all. Nobody commits directly to the Linus git
> repository of the kernel except himself yet we have that model scaling
> incredibly well. Just a side note.
>
This line of reasoning is slightly bi
>>
>> Firefox extension DownThemAll is awesome
>
> resume doesnt always work though
>
There are lots of sites that don't report the Content-Length HTTP
header or support the Byte-Range request feature. The latter is
required for downloading specific chunks. That might be one reason
for the failu
>
> Apropos some flaming^Wdiscussion that took place on this list
> earier.
>
> http://www.linuxjournal.com/content/stallman-vs-clouds
>
> Own/control your data.
Another take:
"Are we so deranged here in the twenty-first century that we're going
to re-enact, wide-eyed, the twin tragedies of the
>
> I'm not so sure. PHP is not exactly a general purpose language. It's meant
> for writing web apps. And db-driven ones at that.
Not true. The FreeBSD based router m0n0wall uses php for all of it's
startup/init
scripts. There's nothing intrinsically webbish about php although the original
intent
