God forbid they should have to make the effort to put a few pages up on the web. If people want to read that stuff, they can just dig up a print version. When I was young we didn't need no fancy schmancy hypertext systems. We walked seven miles to the library in the snow, barefoot! And we were GRATEFUL!
PS. I'm not saying they made it up. To take what I said that way is a bit of a stretch. --
Hmm, I was born in such a country and I don't recall ever using the dm except in math class. Decilitres are another story. On the other hand, *what does that have to do with anything*!?
I find the imperial system quite silly, the metric system perfectly logical. An added bonus is that it's easy to remember the Earth's circumference in metres. --
I had a lot more fun playing Wolfenstein than I did playing DOOM. Maybe it's because I was younger, maybe because Wolfenstein was the first of its kind and it was all so new to me. But I don't think so.
I think Wolfenstein was simply a better game. I'm not sure what the difference is, but when I played Wolfenstein, I was on edge. There were periods of slight nervousness, ended abruptly by a single gunshot that made me jump in my seat, followed by a fit of sheer panic: "Where the fuck is he!?". I'm sure a lot of you know exactly what I'm talking about.
DOOM never gave me that feeling. Quake brought back a little of it, but not enough.
I think the later games just got too big. Bigger monsters and bigger guns translated to bigger health packs and stronger armour. In DOOM(2) you're plodding along waiting for a target worthy of the BGF because using it is a treat. In Wolfenstein you're just trying to stay alive. --
People getting sued for stuff like that is one problem.
People not doing stuff like that for fear of being sued is another, and much larger problem.
I wonder what would happen if a large group of people just stood up and said no. "No, I will not put a disclaimer in my sources", "No, I will not hesitate to do them a favour by mirroring their site", "No, I won't live in constant fear of legal action!"
Do you know how Google gets such wonderfully relevant answers to your searches? First they rate each page in their database individually, according to number of matches, phrase matches, etc. Then they rate each page on the number of highly rated pages that link to it. That way, if there are a bunch of pages that appear to be about the GIMP, and most of them point to www.gimp.org, then www.gimp.org is assumed to be a mother load of GIMP resources.
As the people running Google admit, this is a rather circular definition, but it really does work.
What does this have to do with slashdot moderation? Well, a similar system might be used to rate moderators. I won't suggest implementation specifics, but the basic idea is that if you moderate the same way as a lot of good moderators do, then you too are a good moderator.
This system could no doubt fail in many ways, with disasterous consequences, but if it doesn't, I think it could turn out to be the best system. It's certainly worth thinking about. --
This shows Iceland's connectivity since 1993. Note that this shows traffic in and out of the country, and not traffic within the country. I don't know if any conclusions can be drawn from this.
Hmm. I wonder if Iceland will be slashdotted:-> --
No, they don't have control. He can export his crypto wares very easily. He just can't do it legally, and will therefore have trouble making money off the transaction. A software company in, say, Iceland, is therefore in a better position to compete than he is. The point he's making is that the export controls do not make it significantly harder for an embargoed country to get the software. Contrast that with export restrictions on, say, mortar rounds or land mines, and the distinction should be quite clear. --
I wouldn't say that stripping out the comments makes for a more "accurate" line count. The fact is that source code with comments takes longer to write and is worth more than the corresponding commentless source. --
The windows and menu keys are a godsend. I use mine for meta and compose. Actually, I only use the left windows key for meta, so that leaves one free. What should I do with that one? --
I'm ashamed of my comment at the end of my reply to your post. It was inflammatory and demeaning and I wish I hadn't made it.
If I hadn't, then you wouldn't have done the same to me. I started this, and I apologise.
To clarify, I did read and comprehend your request for the specific clause in the OSD which the APSL violates. It is not because I didn't understand you that I replied with quotes from Bruce's article, but because I felt that Bruce had made it clear in those section why the APSL didn't qualify under the OSD.
Given that "Section 9.1 of the APSL allows Apple to terminate our rights to use any or all APSL-covered code", it is obvious that the APSL does not fit the OSD. It doesn't take careful reading of the OSD to see that; a general knowledge of its nature is sufficient. It is this obvious conclusion that I thought you were missing.
Whether the above quoted statement is true, and a valid premise on which to draw conclusions, is another matter. I haven't made up my mind about that yet. --
Answer the question before jumping to conclusions
on
Response to the APSL
·
· Score: 1
Section 2.2(c) of the APSL requires that the producer of modifications to APSL-licensed code use a particular URL in the Apple.com domain to notify Apple. While the demise of Apple Computer, Inc. is unlikely in the near future, that sad event would leave us unable to comply with this section of the APSL. This would constitute a restriction on all rights granted by the license, including those rights necessary to qualify under the Open Source Definition.
Section 9.1 of the APSL allows Apple to terminate our rights to use any or all APSL-covered code, at its sole discretion, in the event of an unproven claim of infringement, no matter how specious.
I don't know why I bother. If you didn't get it when you read the article, you probably don't get it when you read it here. --
If Slashdot Readers were behind Linux it'd FAIL!
on
Response to the APSL
·
· Score: 1
Linux is the belief that by COOPERATION, a group of people can creat greatness.
No, Linux is an operating system (or an operating system kenel, for the GNU/Linux crowd).
Linux could disappear tomorrow, and it would only slightly hurt the free software movement. A new kernel would be written. It would be harder to replace the thousands of talented people who wrote it, but they aren't going away. There's no linux movement. There's a freedom movement.
It's exactly the freedom element that you're overlooking. Like Ed Muth, you just don't "get it". --
It was a great computer for its time (in the Commodore 64 era). The Amstrad 6128 had 128K RAM, a screen, and a floppy drive. The disks took a whopping 196K. You could even run CP/M on it.
Most people had a 646, though. That one had 64K RAM and a tape deck. --
The beauty of the Amiga was how simple and stable it was to go in and fuss with the guts. The user had a high degree of control over the OS, and the hardware had handy features that still aren't available today
(like splitting the screen between multiple resolutions)
I remember software that did this on the Amstrad as well. I'm not very familiar with the Amiga, but I'm guessing this is the same thing, in which case you can can't change the resolution in the middle of a scanline. The trick is to just change the video mode at precisely the right time as the screen is being redrawn.
If you find that interesting, you might want to dig up an old demo called "copper" (should be on the Hornet archive), run it, and read the docs that come with it. Guided by those docs, I once wrote a TSR for MS-DOS that, with practically no CPU overhead, scrambled the display (making it look like cable tv). I pondered making a virus out of it, but I was too damn responsible. It would have been the coolest virus ever, though. Just imagine the tech support calls!:-)
Anyway, to get back on the topic, the same technique can possibly be used to achieve multiple simultaneous resolutions on a PC. I think the copper docs may even have covered that. --
It had a few major bugs, including one that crashed my system (it involved the bttv driver).
The point is that everybody was very understanding, reported these bugs, and went on to install 2.2.1 and 2.2.2. Give gnome the same chance.
Of course there are those who have already decided that gnome sucks and the sorry state of this release will give them ample opportunity to confirm their assessment. I'd lust like to ask those people to keep their opinions to themselves unless they can put them into words in a *constructive* manner.
I've tried a couple of those on linux, but never got them to run. I tried one Windows build, and that ran great. (Hey, perhaps I could just run that one in Wine)
Anyway, what kind of experience have others had with the nightly builds for linux. Is it the builds that are fucked up, or my system?
The actual developers aren't the rabid flamers in the GNOME vs. KDE argument.
The developers have expressed a desire to facilitate interoperability between components, even if they're not that keen on sharing code (that whole c/c++ thing).
Slashdot Mirror
How many of you have written a program that draws the pattern on the paper dress?
--
God forbid they should have to make the effort to put a few pages up on the web. If people want to read that stuff, they can just dig up a print version. When I was young we didn't need no fancy schmancy hypertext systems. We walked seven miles to the library in the snow, barefoot! And we were GRATEFUL!
PS. I'm not saying they made it up. To take what I said that way is a bit of a stretch.
--
Hmm, I was born in such a country and I don't recall ever using the dm except in math class. Decilitres are another story. On the other hand, *what does that have to do with anything*!?
I find the imperial system quite silly, the metric system perfectly logical. An added bonus is that it's easy to remember the Earth's circumference in metres.
--
clear Lock
keycode 66 = Multi_key
--
I use caps lock for Multi_key. CAPSLOCK-"-i -> ï, etc.
These lines in .Xmodmap will arrange that: clear Lock keycode 66 = Multi_key
--
I'm not the previous poster but for me, if it ain't hyperlinked, it ain't there.
--
Thank you for summing that up.
--
I had a lot more fun playing Wolfenstein than I did playing DOOM. Maybe it's because I was younger, maybe because Wolfenstein was the first of its kind and it was all so new to me. But I don't think so.
I think Wolfenstein was simply a better game. I'm not sure what the difference is, but when I played Wolfenstein, I was on edge. There were periods of slight nervousness, ended abruptly by a single gunshot that made me jump in my seat, followed by a fit of sheer panic: "Where the fuck is he!?". I'm sure a lot of you know exactly what I'm talking about.
DOOM never gave me that feeling. Quake brought back a little of it, but not enough.
I think the later games just got too big. Bigger monsters and bigger guns translated to bigger health packs and stronger armour. In DOOM(2) you're plodding along waiting for a target worthy of the BGF because using it is a treat. In Wolfenstein you're just trying to stay alive.
--
People getting sued for stuff like that is one problem.
People not doing stuff like that for fear of being sued is another, and much larger problem.
I wonder what would happen if a large group of people just stood up and said no. "No, I will not put a disclaimer in my sources", "No, I will not hesitate to do them a favour by mirroring their site", "No, I won't live in constant fear of legal action!"
Yes, I am naïve.
--
Do you know how Google gets such wonderfully relevant answers to your searches? First they rate each page in their database individually, according to number of matches, phrase matches, etc. Then they rate each page on the number of highly rated pages that link to it. That way, if there are a bunch of pages that appear to be about the GIMP, and most of them point to www.gimp.org, then www.gimp.org is assumed to be a mother load of GIMP resources.
As the people running Google admit, this is a rather circular definition, but it really does work.
What does this have to do with slashdot moderation? Well, a similar system might be used to rate moderators. I won't suggest implementation specifics, but the basic idea is that if you moderate the same way as a lot of good moderators do, then you too are a good moderator.
This system could no doubt fail in many ways, with disasterous consequences, but if it doesn't, I think it could turn out to be the best system. It's certainly worth thinking about.
--
This shows Iceland's connectivity since 1993. Note that this shows traffic in and out of the country, and not traffic within the country. I don't know if any conclusions can be drawn from this.
Hmm. I wonder if Iceland will be slashdotted :->
--
If someone says a licence is an Open Source license and it isn't, then that is inappropriate, don't you agree?
--
No, they don't have control. He can export his crypto wares very easily. He just can't do it legally, and will therefore have trouble making money off the transaction. A software company in, say, Iceland, is therefore in a better position to compete than he is. The point he's making is that the export controls do not make it significantly harder for an embargoed country to get the software. Contrast that with export restrictions on, say, mortar rounds or land mines, and the distinction should be quite clear.
--
I wouldn't say that stripping out the comments makes for a more "accurate" line count. The fact is that source code with comments takes longer to write and is worth more than the corresponding commentless source.
--
The windows and menu keys are a godsend. I use mine for meta and compose. Actually, I only use the left windows key for meta, so that leaves one free. What should I do with that one?
--
I'm ashamed of my comment at the end of my reply to your post. It was inflammatory and demeaning and I wish I hadn't made it.
If I hadn't, then you wouldn't have done the same to me. I started this, and I apologise.
To clarify, I did read and comprehend your request for the specific clause in the OSD which the APSL violates. It is not because I didn't understand you that I replied with quotes from Bruce's article, but because I felt that Bruce had made it clear in those section why the APSL didn't qualify under the OSD.
Given that "Section 9.1 of the APSL allows Apple to terminate our rights to use any or all APSL-covered code", it is obvious that the APSL does not fit the OSD. It doesn't take careful reading of the OSD to see that; a general knowledge of its nature is sufficient. It is this obvious conclusion that I thought you were missing.
Whether the above quoted statement is true, and a valid premise on which to draw conclusions, is another matter. I haven't made up my mind about that yet.
--
I don't know why I bother. If you didn't get it when you read the article, you probably don't get it when you read it here.
--
No, Linux is an operating system (or an operating system kenel, for the GNU/Linux crowd).
Linux could disappear tomorrow, and it would only slightly hurt the free software movement. A new kernel would be written. It would be harder to replace the thousands of talented people who wrote it, but they aren't going away. There's no linux movement. There's a freedom movement.
It's exactly the freedom element that you're overlooking. Like Ed Muth, you just don't "get it".
--
It was a great computer for its time (in the Commodore 64 era). The Amstrad 6128 had 128K RAM, a screen, and a floppy drive. The disks took a whopping 196K. You could even run CP/M on it.
Most people had a 646, though. That one had 64K RAM and a tape deck.
--
I remember software that did this on the Amstrad as well. I'm not very familiar with the Amiga, but I'm guessing this is the same thing, in which case you can can't change the resolution in the middle of a scanline. The trick is to just change the video mode at precisely the right time as the screen is being redrawn.
If you find that interesting, you might want to dig up an old demo called "copper" (should be on the Hornet archive), run it, and read the docs that come with it. Guided by those docs, I once wrote a TSR for MS-DOS that, with practically no CPU overhead, scrambled the display (making it look like cable tv). I pondered making a virus out of it, but I was too damn responsible. It would have been the coolest virus ever, though. Just imagine the tech support calls! :-)
Anyway, to get back on the topic, the same technique can possibly be used to achieve multiple simultaneous resolutions on a PC. I think the copper docs may even have covered that.
--
Am I just weird? I thought Starship Troopers rocked. Then again, I didn't go into that theatre expecting acting and a plot, like some people.
"THE ENEMY CANNOT PUSH A BUTTON WHEN HIS HAND IS NAILED TO THE WALL!"|
Gratuitous violence is always kinda fun.
--
It had a few major bugs, including one that crashed my system (it involved the bttv driver).
The point is that everybody was very understanding, reported these bugs, and went on to install 2.2.1 and 2.2.2. Give gnome the same chance.
Of course there are those who have already decided that gnome sucks and the sorry state of this release will give them ample opportunity to confirm their assessment. I'd lust like to ask those people to keep their opinions to themselves unless they can put them into words in a *constructive* manner.
--
I've tried a couple of those on linux, but never got them to run. I tried one Windows build, and that ran great. (Hey, perhaps I could just run that one in Wine)
Anyway, what kind of experience have others had with the nightly builds for linux. Is it the builds that are fucked up, or my system?
--
How does shuffling your proxy around help security?
--
The actual developers aren't the rabid flamers in the GNOME vs. KDE argument.
The developers have expressed a desire to facilitate interoperability between components, even if they're not that keen on sharing code (that whole c/c++ thing).
--