Re:a fantastic movie (made for $7k)
on
Primer
·
· Score: 2, Informative
Shane Carruth was at the Waterfront Film Festival earlier this summer
talking to the audience after a screening of Primer about how the movie
was made. I got the impression of an energetic, independent, and
creative guy, relatively untainted by the business of the movie industry.
Here's an
interview
with Carruth that goes into some of the background, including the $7000
budget.
Yes, it was easy to bootstrap pkgsrc when I used it on Slackware. I do not remember any major problems. It helps to be comfortable with make and autoconf tools - the good and bad of open source is it's such a moving target.
Pkgsrc can coexist with other packaging systems. In one case, we had a couple aging Slackware 7 servers running. We did not want to take them out of service but needed to run a new program on them. By adding a pkgsrc tree, we got a whole new generation of compiler, autoconf tools, etc without affecting the legacy bits.
What would probably not work well would be mixing an interpreter from one packaging system (Perl, Python, Erlang, etc) with modules from another packaging system.
There may be more software available in the "native" packages for a given OS than with pkgsrc. OTOH we like that pkgsrc gives us a consistent interface for config management across several OSes. YMMV.
For another option, netbsd's pkgsrc system works very well with many Unix variants. I have used it with previous Slackware releases, not 10 yet. Pkgsrc has the advantage of giving you a single multiplatform packaging toolset for BSDs, Linuxes, Solaris, and others.
I don't get it. It sounds like another protocol inversion: UDP over DNS. OTOH we have seen IT managers solemnly accepting RPC over HTTP (SOAP) and TCP over HTTP (Web Services).;-)
Maybe it's time to break from the lemming-like rush to format
absolutely everything in XML.
If you want a concise, readily-parsed alternative, consider
UBF
- don't let the title of the paper throw you; it's really about
a lean alternative to XML.
Or just enjoy some alternative viewpoints on the subject at the
Portland Pattern Repository's
XML Sucks
page.
Under guise of keeping us safe from terrorists, FBI & friends get an undisclosed inside picture of developing corporate mergers and acquisitions, etc. It's hard to believe, in view of recent scandals, that this information would not be abused.
I don't know about the Ohio legislature. But I have to wonder which constituency was served by this recent regulation? Did voters clamor for a stop to the making of bootleg recordings in theatres?
Bravo to the politicians for timely and effective response to the the needs of those who elected them.
This just in - SCO has finally announced the stolen source in the Linux kernel. It amounts to exactly 17,351 occurrences of
int i; also infringing are occurrences of
i++; and
return; "And that's just the tip of the iceberg" a SCO source reported.
Actually, the highest form of humor is clown jokes, specifically "What is the most difficult thing about X?" - Ans: "Getting the blood off the clown suit." Suitable values of X are: arguing intellectual property issues before Congress, marketing.NET, etc.
We already have Americans for Customary Weight & Measure
- http://www.bwmaonline.com/ACWM.htm - now we must hold the line with Americans for Customary Packet Size (anti IPv6), followed by Americans for Pretending Things Are So Simple a Hamster Can Figure Them Out.
A person who visits a site via deep link today is likely to skip the commercials in a taped TV program tomorrow, or read just the articles from a magazine and not the ads.
There was a time when the Phone Company would only let you connect their phones to your local loop. And you heard a lot about how dangerous it would be to allow a person to hook up any third party equipment instead of bona fide Ma Bell telephones.
In order to hook up a modem, you had to get a special Data Access Arrangement from them, for which the monthly charge was more than you'd pay for a modem today.
Why come up with a new 'Mebibyte' system? What does 'kilo-' and 'mega-' actually mean? Answer: 1000 and 1,000,000, not the perversion of the computer scientists.
Amen, brother. Bad enough we had to put up with the perversions of the physicists and chemists, trying to foist those unnatural kilo- this and centi- that instead of God's own inches and feet. We can hold the line again, if we all stick together. Just say no to powers of two.
If we lose this one, who knows what could be next? IPv6? Math literacy in your neighborhood?
Slashdot Mirror
Knuth's http://www-cs-faculty.stanford.edu/~knuth/rice.htm lopen letter
to Condi Rice.
Shane Carruth was at the Waterfront Film Festival earlier this summer talking to the audience after a screening of Primer about how the movie was made. I got the impression of an energetic, independent, and creative guy, relatively untainted by the business of the movie industry.
Here's an interview with Carruth that goes into some of the background, including the $7000 budget.
Yes, it was easy to bootstrap pkgsrc when I used it on Slackware. I do not remember any major problems. It helps to be comfortable with make and autoconf tools - the good and bad of open source is it's such a moving target.
Pkgsrc can coexist with other packaging systems. In one case, we had a couple aging Slackware 7 servers running. We did not want to take them out of service but needed to run a new program on them. By adding a pkgsrc tree, we got a whole new generation of compiler, autoconf tools, etc without affecting the legacy bits.
What would probably not work well would be mixing an interpreter from one packaging system (Perl, Python, Erlang, etc) with modules from another packaging system.
There may be more software available in the "native" packages for a given OS than with pkgsrc. OTOH we like that pkgsrc gives us a consistent interface for config management across several OSes. YMMV.
For another option, netbsd's pkgsrc system works very well with many Unix variants. I have used it with previous Slackware releases, not 10 yet. Pkgsrc has the advantage of giving you a single multiplatform packaging toolset for BSDs, Linuxes, Solaris, and others.
I don't get it. It sounds like another protocol inversion: ;-)
UDP over DNS. OTOH we have seen IT managers solemnly accepting
RPC over HTTP (SOAP) and TCP over HTTP (Web Services).
$man ls | grep "^ *-" | wc -l
28
How boring. 7-bit ASCII. Only 28 things to do with ls.
Add hanzi, kanji, kana, hangul and get another 100K or so 1-character switches.
Man in suit: Hey kid, nice software you have there. What's it called?
Kid: Um, Linux, why?
Man: Because I'm from SCO/Microsoft and I think it looks like my
software now.
Kid: No way, in fact I wrote some of it myself
Man [pushing attorneys in front of him]: Moose! Lefty! Help the kid
find his wallet.
That is part of the problem.
Maybe it's time to break from the lemming-like rush to format absolutely everything in XML.
If you want a concise, readily-parsed alternative, consider UBF - don't let the title of the paper throw you; it's really about a lean alternative to XML.
Or just enjoy some alternative viewpoints on the subject at the Portland Pattern Repository's XML Sucks page.
Under guise of keeping us safe from terrorists, FBI & friends get an undisclosed
inside picture of developing corporate mergers and acquisitions, etc. It's hard
to believe, in view of recent scandals, that this information would not be abused.
I don't know about the Ohio legislature. But I have to wonder which
constituency was served by this recent regulation? Did voters
clamor for a stop to the making of bootleg recordings in theatres?
Bravo to the politicians for timely and effective response to the
the needs of those who elected them.
This just in - SCO has finally announced the stolen source in the
Linux kernel. It amounts to exactly 17,351 occurrences of
int i;
also infringing are occurrences of
i++;
and
return;
"And that's just the tip of the iceberg" a SCO source reported.
Actually, the highest form of humor is clown jokes, specifically "What is the most difficult thing about X?" - Ans: "Getting the blood off the clown suit." Suitable values of X are: arguing intellectual property issues before Congress, marketing .NET, etc.
Why Threads Are A Bad Idea (for most purposes)
Use Nvidia for games if you like. For some of us, open source - which Nvidia drivers are not - matters more than video gaming frame rate.
Nvidia => no BSD support, no support if your Linux kernel strays too far from the snapshots they use.
Never liked the performance and resource-consumption price of Java anyway, so no big deal.
We already have Americans for Customary Weight & Measure
- http://www.bwmaonline.com/ACWM.htm - now we must hold the line with Americans for Customary Packet Size (anti IPv6), followed by Americans for Pretending Things Are So Simple a Hamster Can Figure Them Out.
Or something.
A person who visits a site via deep link today is likely to skip the commercials in a taped TV program tomorrow, or read just the articles from a magazine and not the ads.
Where will it all end?
In order to hook up a modem, you had to get a special Data Access Arrangement from them, for which the monthly charge was more than you'd pay for a modem today.
Eternal vigilance, etc.
SBE makes T1/E1 and T3 PCI WAN interfaces with integrated CSU. Driver source is available for Linux and all three BSDs.
TV is for nursing homes and coma wards. If you are blessed with more cortical activity than a salad bar, turn off the tube and go do something useful.
Ok so it's not gnintegrated, but MagicPointrocks.
Amen, brother. Bad enough we had to put up with the perversions of the physicists and chemists, trying to foist those unnatural kilo- this and centi- that instead of God's own inches and feet. We can hold the line again, if we all stick together. Just say no to powers of two.
If we lose this one, who knows what could be next? IPv6? Math literacy in your neighborhood?
Several characters of Katakana are, um, unistroke. Let's sue Japan.
And Mesopotamia...
There is no such thing as X Windows
man x