The code does the same thing either way. But, if you think of argv[1] as the Question, I'm just showing that we can't know it, because we know the Answer. Perhaps I should have written it more like this:
int main(int argc, char **argv) { int Answer=42; char Question=argv[1]; if (Answer) { Question=NULL; } return Answer; }
This program is valid in C, C++, python, perl, basic, and a few other languages, and it also accomplishes the rare feat of printing its own source code without reading from a file:
Note that, even though this is standard C, gcc won't compile it, complaining about the lack of a "main" function.
I highly doubt they'd fit on an iPod. I don't know if/how they'd be compressed, but you'd probably be lucky to fit them on an 80gb HD. High-quality digital video is huge.
IIRC, there is a cookie patch out there, but it's not in standard dillo[1]. I stand corrected on the PNG support, but it seems that my version of dillo(0.6.4) doesn't support background images, which is almost worse. And yeah, it does have bookmarks. I don't use dillo often, and it doesn't have the most intuitive UI, so I didn't see that.
But really, for most people, a browser that supports no CSS, Javascript, or frames (lynx-style frame support is useless in most cases, for example pages with a framed navbar) is not very useful. If it works for you, that's great. But in most cases, it's not a viable choice.
[1]. I see that a new version of dillo has recently been released, with cookie support. Apparently it hasn't gotten into Debian yet, so I'm not using it.
Ummm... Opera was the only browser to have its latest version reviewed. Netscape, Mozilla, and Galeon all have one or more new releases out. If anything, it's a pro-Opera bias. But I doubt that, it's just someone who hasn't seen the light and insists on using old versions because "it's too much trouble to upgrade".
Dillo's great for browsing on a 386. But really, it doesn't support cookies, PNG's, bookmarks, frames, CSS, proper text wrapping around images, and it barely supports tables. It's not a serious option for most people.
Saved for posterity, from a discussion about the new subscription system:
... while I don't mean to dismiss the value of comment posters, the percentage of readers that read comments is small. Yes comments draw readers, and keep them coming back. But half of readers don't care! An accepted story submission provides a benefit to hundreds of thousands of Slashdot readers. A Score:3 comment is read by 1/50th of that. So if we decide that an accepted story submission is worth 1000 page views, you would need to post perhaps 50 Score:3 comments to affect the same number of people:)
A statistic in the hand of the ignorant is more dangerous than a gun in the hand of a child. Malda's dismissal of the importance of comments [slashdot.org] reflects on the inability of Slashdot's "editors" to understand the way communities work.
For the record, my feelings on the Slashdot Subscription Embroglio rests firmly in the uninterested. I have almost zero opinion on the final outcome of subscriptions. I love Slashdot, and will probably subscribe at some point to support the site, but the details are dull (to me).
Says Rob Malda, "... while I don't mean to dismiss the value of comment posters, the percentage of readers that read comments is small. Yes comments draw readers, and keep them coming back. But half of readers don't care!" In that case, Slashdot would be much better served by dumping the flaky and irritating overhead of a DB server and filling the pipe with a longer "Favorites" list--which, essentially, is what Slashdot is once you strip away the comments and comment posters. This is where a meaningless SQL query puts dangerous statistics in the hand of the ignorant. If Malda thinks that he can divine real knowledge from a SELECT query, he is sadly mistaken. While I do not doubt the validity of the numbers, I seriously doubt the validity of his extrapolation of the data. The ebb and flow of a community cannot be read from the tea leaves of an Apache log file.
This easy dismissal of the value of the only providers of interesting and insightful content on Slashdot is offensive. Thus, I propose a small revolt. The (Hopefully) Great Slashdot Blackout.
T(H)GSB will be during the week of April 21 through April 27. Easy to remember, the full moon in April falls on the 27th. During that time, I will not be posting, nor will I click through to read the comments from the home page. I will become as Malda's idea of the typical Slashdot reader. I will provide no new content (neither comments, nor story submissions--although I'm not much of a story submitter).
During that week, I'd like to see if Malda sees Slashdot become a better place, or if it becomes the Hallowed Shrine of Troll. I'd like for the logs to be revisited and new queries run. And, I'd like for the "editors" to really see what the true value of Slashdot is--not the sum of click-throughs and page-views, but the sharing of knowledge and dissemination of information; the passing of experience from the more to the less.
This is where the (Hopefully) comes in. This is only meaningful if enough free content-providers (i.e., comment posters) agree to go along and participate. If there is only me and a handful of others who cease normal activities during that week, it will be pretty meaningless. Barely a dent will be made, and Malda and the other "editors" will never realize the incredible value they receive from comment posters.
To spread the word, I'm changing my sig to link to this journal entry. If you would like to help, you can link to this journal from your own sig, or you can simply resolve to enter into a voluntary one-week blackout. Pass the word. This will only work if a goodly number of comment posters participate.
To summarize, if you wish to participate, during the week of April 21 through April 27
Do not click through from the home page to the comment page
Do not post any comments to stories
Do not submit new stories
A useful HTML link to this journal entry (69 characters, should fit in most sigs). You'll probably have to unfungle it after the lameness filter gets through with it:
KDE 3 will not be in Woody. This is in no way related to the lack of packages. Packages could have been released the day KDE3 came out and it still wouldn't be in Woody, because it's a brand-new.0 release without much testing and doesn't belong in the "stable" distribution.
Slashdot Mirror
int main(int argc, char **argv)
{
if (argc==2)
{
argv[1]=NULL;
}
return 42;
}
Given the >400 comments in this story, apparently not.
You just did it.
Note that, even though this is standard C, gcc won't compile it, complaining about the lack of a "main" function.
Perhaps he's enough of a non-idiot to realize that not everything he says is worthy of being shouted, and occasionally checks the "No Bonus" box.
I highly doubt they'd fit on an iPod. I don't know if/how they'd be compressed, but you'd probably be lucky to fit them on an 80gb HD. High-quality digital video is huge.
Ummmm... no you can't, and no they're not.
Umm... since when does Abiword not support columns?
But really, for most people, a browser that supports no CSS, Javascript, or frames (lynx-style frame support is useless in most cases, for example pages with a framed navbar) is not very useful. If it works for you, that's great. But in most cases, it's not a viable choice.
[1]. I see that a new version of dillo has recently been released, with cookie support. Apparently it hasn't gotten into Debian yet, so I'm not using it.
Ummm... Opera was the only browser to have its latest version reviewed. Netscape, Mozilla, and Galeon all have one or more new releases out. If anything, it's a pro-Opera bias. But I doubt that, it's just someone who hasn't seen the light and insists on using old versions because "it's too much trouble to upgrade".
Dillo's great for browsing on a 386. But really, it doesn't support cookies, PNG's, bookmarks, frames, CSS, proper text wrapping around images, and it barely supports tables. It's not a serious option for most people.
Evolution is configured by default to render HTML, but not load images unless you ask. I think that's the best way around the problem.
Yeah, I know, I was joking. I actually use Evolution.
I also use Outlook, and I have had no viruses. I suspect the reason is that neither of us has any friends.
Obligatory BBSpot link: The dMac and vMac.
IIRC, the default format of all OpenOffice derivitives is binary, because it's just gzipped XML.
Last Chance to See! The final opportunity to discuss this before the lights go out [slashdot.org]
Questions? There are answers here! [slashdot.org]
Saved for posterity, from a discussion about the new subscription system:
... while I don't mean to dismiss the value
of comment posters, the percentage of readers
that read comments is small. Yes comments draw
readers, and keep them coming back. But half
of readers don't care! An accepted story
submission provides a benefit to hundreds
of thousands of Slashdot readers. A Score:3
comment is read by 1/50th of that. So if we
decide that an accepted story submission is
worth 1000 page views, you would need to post
perhaps 50 Score:3 comments to affect the
same number of people
A statistic in the hand of the ignorant is more dangerous than a gun in the hand of a child. Malda's dismissal of the importance of comments [slashdot.org] reflects on the inability of Slashdot's "editors" to understand the way communities work.
For the record, my feelings on the Slashdot Subscription Embroglio rests firmly in the uninterested. I have almost zero opinion on the final outcome of subscriptions. I love Slashdot, and will probably subscribe at some point to support the site, but the details are dull (to me).
Says Rob Malda, "... while I don't mean to dismiss the value of comment posters, the percentage of readers that read comments is small. Yes comments draw readers, and keep them coming back. But half
of readers don't care!" In that case, Slashdot would be much better served by dumping the flaky and irritating overhead of a DB server and filling the pipe with a longer "Favorites" list--which, essentially, is what Slashdot is once you strip away the comments and comment posters. This is where a meaningless SQL query puts dangerous statistics in the hand of the ignorant. If Malda thinks that he can divine real knowledge from a SELECT query, he is sadly mistaken. While I do not doubt the validity of the numbers, I seriously doubt the validity of his extrapolation of the data. The ebb and flow of a community cannot be read from the tea leaves of an Apache log file.
This easy dismissal of the value of the only providers of interesting and insightful content on Slashdot is offensive. Thus, I propose a small revolt. The (Hopefully) Great Slashdot Blackout.
T(H)GSB will be during the week of April 21 through April 27. Easy to remember, the full moon in April falls on the 27th. During that time, I will not be posting, nor will I click through to read the comments from the home page. I will become as Malda's idea of the typical Slashdot reader. I will provide no new content (neither comments, nor story submissions--although I'm not much of a story submitter).
During that week, I'd like to see if Malda sees Slashdot become a better place, or if it becomes the Hallowed Shrine of Troll. I'd like for the logs to be revisited and new queries run. And, I'd like for the "editors" to really see what the true value of Slashdot is--not the sum of click-throughs and page-views, but the sharing of knowledge and dissemination of information; the passing of experience from the more to the less.
This is where the (Hopefully) comes in. This is only meaningful if enough free content-providers (i.e., comment posters) agree to go along and participate. If there is only me and a handful of others who cease normal activities during that week, it will be pretty meaningless. Barely a dent will be made, and Malda and the other "editors" will never realize the incredible value they receive from comment posters.
To spread the word, I'm changing my sig to link to this journal entry. If you would like to help, you can link to this journal from your own sig, or you can simply resolve to enter into a voluntary one-week blackout. Pass the word. This will only work if a goodly number of comment posters participate.
To summarize, if you wish to participate, during the week of April 21 through April 27
A useful HTML link to this journal entry (69 characters, should fit in most sigs). You'll probably have to unfungle it after the lameness filter gets through with it:
<a href="http://slashdot.org/~rho/journal/5872">T( H)GSB</a> Apr 21-27
Last Chance to See! The final opportunity to discuss this before the lights go out [slashdot.org]
Questions? There are answers here! [slashdot.org]
Shouldn't that be "nearly always does"?
Screenshot of the old Chimera browser.
KDE 3 will not be in Woody. This is in no way related to the lack of packages. Packages could have been released the day KDE3 came out and it still wouldn't be in Woody, because it's a brand-new .0 release without much testing and doesn't belong in the "stable" distribution.
And many times redundant.
We should go start pushing it at goatse.cx :-).
So log in.
As opposed to middle school kids with jobs?