Alan, I know you do a great deal of sound hacking, and I'm particulary looking forward to a time when meaningful full-duplex support is available without paying tribute to OSS. I've attempted to use their SB16 and Ensoniq support in their trial package, and the experience was excruciating. I banged my head to no avail. Abominable documentation. Our own free stuff is far better, IMHO. I ran out of time on their trial edition, and w/o source, I couldn't figure out what I was doing wrong, unlike the free drivers, which though sketchy, I could fathom. Any hope for folks like me?
Interesting that without piracy most copyrighted works wouldn't be popular in the first place. If M$ hadn't shipped ms/pc-dos unprotected, and win 3.1 wasn't freely copyable we wouldn't have a windows-only world right now. M$ spread like a virus. Now the virus and its minions demand their due. We know the answer. Free software... *And* (I'll say this again, so you guys may eventually get it): Geek's Day Off. We built it, and we can take it back, anytime we like. Think about it. A Geek's Guild. Hmmmm....
Damn straight. Sums up the whole excercise for me. Look at Gates's face when he talks. If he was any more full of doo-doo he'd explode! Hell, he has hand-jive consultants! (very inside unless you know politics) Not a good sign. He plans to do that. It WILL happen. Bill wants power. Badly. Maybe we can run him against steve forbes for global benevolent dictator. You scared yet?
My post is rather old, by now, so noone is likely to read this, but for the sake of completeness, I'll explain,cursorily, what that XOR gate did, to the extent that I can remember. (incidentally, I worked this out by *tracing circuit board foils* to figure out what was going on. How many of you HLL weenies have ever done THAT, eh?) If I recall correctly, it worked in concert with cbm's ieee 488 like protocol that communicated with the drive. There were three lines, clk, data, and atn, and a rather baroque but effective dance done twixt the c64 and 1541 that allowed a device on the serial chain to take either a master or slave role. It was pretty sophisticated stuff, really. IMHO cbm's firmware was some the slickest code I've ever hacked. Anyway, fastloaders got around the 'may I have a byte, please?' 'Yes you can!' 'Ok give it to me.' 'here it comes!' >get the byte 'I have it, thank you.' 'you're welcome.' cycle that made the 1541 so slow by running code in the drive (yes, you could do that! Gives me a woody just thinking about it!) that would read the disk directly, bypassing the os entirely, decode the group codes on the disk w/ your own optimised code, and do serial i/o manually, splitting the data bytes into bit pairs, and using two of the i/o lines to jam that data as fast as you could into the computer. Many programs to do this relied on knowing the clock speed and skew between the drive and computer cpu's, and just syncing up, and stuffing asynchronously a bunc of bit pairs in a row, resyncing, and doing it again, and again. This is fine for a US machine, but european machines have differing clock speeds, because of different video standards. I was stuck doing a fastloader that had to be portable to europe. I had to be synchronous. I found that the XOR gate on the ATN line complemented the data on the data line. This allowed me to use 2 translation tables ( one for clk=1, one for clk=0 ) and transfer data on clk *edge*. doubling my speed. I was faster than apple's prodos on a c64! Incidentally, for those who know the ins and out's of this stuff, the client didn't care about other devices being active on the serial bus. My previous code took that into account, but was us only. These guys (westwood) wanted portability. for it to work, only one drive and no printers could be on, or bus confusion resulted. The lore involved in c64 fastdos stuff is really neat. Wish I had time and space to get into it more here.
I don't mean to be a jerk, trust me. But if you have to ask that question, you need to learn a whole lot more about how gnu compliant software works. You need to know more about software, period. Configure is a brilliant hack that determines what sort of machine software is being compiled for. You don't want to compile a new libc and attempt to install it unless you know EXACTLY what the hell you're doing. It's the heart and soul (next to your kernel) of the whole machine. Break it, and you won't boot. Leave it alone. If you need a new libc at your point of development, get a new distro on cd, and reinstall.
"C programmers had to know assembler in those days. Believe it." My personal feeling is that they should know assembler TODAY, as well, so as to have some frigging idea as to the consequences of their coding. Doesn't hurt to solder up a micro from scratch, using only one's wits and a data book or two, either. I did that in '83 w/a 8085 (my first computer!) and it simply rocks! Not to mention the manly confidence that understanding a sytem from the metal up gives one! 8-} Helps when writing fastloaders for C64's, lemme tellya! Found a nifty use for that XOR gate on the 1541's ATN line, for sure! (if you understood what I just said, you really scare me) I've counseled a number of newbies to take this exact tack in their own educations, contrary to popular wisdom, and each and every one thanked me profusely for suggesting it. They eventually ran rings around their classmates, and actually GOT something out of (Acck!) DeVry!
I know I got flamed for this idea previously, but, now it's time. You and I and all readers of this place are generally geeks. We build things. We research things. We solve problems. We are the glue that holds this interconnected world together. Hell! We created it!
It's high time we put our collective foot down. Let's take this thing we built back! Let us put aside one day a year that we ALL stay home. And do nothing. at all. Jews have that. Muslims have it. Geekhood is as close to a religion that I have. Wanna see the world shake? Find a day. Pick a day That day, all geeks STAY HOME! No work. No calls. No nothing. You'll be going to mars with the blessing of the speaker of the house in 6 mos. Geeks are assumed to be pussies. WRONG! We are true warriors. We put our immediate needs on hold for the larger cause. Geeks rule this planet at this time. Assume that mantle responsibly. Assert your authority. Whether you like it or not, you're piloting this thing. Do it right.
I haven't the time to read all the various posts on this subject, but this crosswitch thing has been obvious to me since '74. It's already been done. Design your bus according to all those transmission line stuff you learned in skool and crank the living hell out of it. Multiplex, ATM-like. 500mhz was doable in *1975* with ecl logic and a big power supply (current mode switching. still a good idea.) GAAS gates have propagation times in the single digit PICOSECONDS! Use them! I leave the rest as an excercise to the observant reader.
I don't argue with anything you've said. I forgot to mention the thread-per-interface thing and feel a little silly since I realize that was our bottleneck. What I meant was that IIS does a thing similar to squid, where it allocates a bunch of RAM assumedly user-configurable, and rule-based, for caching frequently requested pages within its own process space. Apache doesn't do this by default, which, IMHO is a good idea. As to squid and dynamic content, it's insanely configurable in that arena. I also implied that the apache implementation in question would incorporate mod_perl and php modules as a piece of the instance. so as to avoid the forking you spoke of. An additional thing one can do with apache so as to avoid needless spawning of new processes is to extend the lifetime of the daemon. RTFM on apache.conf. BTW mod_rewrite rocks!
I'm rather ashamed not to know that. I love his work with kids, dont get me wrong. I just love his work as a great coder. He made that world his. He was a fscking van halen of coding. So was Bill Budge. Wonder where he is. He truly hacked. No more? I don't get it. A natural math prodigy. I would've loved him as a friend. BIG PICTURE. He got it, somehow.
Damn! You're right! I remember reading about this in a deadly flame thread on comp.protocols.tcpip. the guy who instigated it did us all a huge favor, as it made everyone think in a state-machine kinda way, which should be elemental to anyone who knows computers. Sometimes we abstract so much, we forget these things are stupid and have to be slapped into civilty from the metal on up!
Any apache site expecting to serve tons of static pages should run squid in accel mode in front of apache. apache's cache (IF USED???) doesn't even come close to squid, and the apache team will readily admit it. I can't believe the redhat guys didn't embrace this strategy since it's well known that a key factor in IIS performance is the fact that it caches it's own static pages IN RAM when possible! This is a no-brainer. Note the big increase in performance between 256M and 1G. Personally, I believe, even given Linux's shortcomings in its TCP stack, we should smoke IIS with a properly configured server. As for ACTIVE content.. Done properly, mod_perl or php should kill.asp.
Right on , pal. These guys are morons. Nobody owns the world of numbers. And nobody understands numbers better than geeks (us) do. Game's already over. We won. There's no way to enforce this shit in the US without a soviet-style Surveillance scheme, where everyone is monitored all the time. We also have a very cool 2nd amendment. (guns for everyone) We may soon have to excercise it, if this stuff continues.
What the hell happened to this guy? DAMN! If any of you weenie hacker wannabies ever read any of his code, you would see the clear, cool mind of a fscking GENIUS! MAN his stuff was elegant! You could sit, pass it around, and just ADMIRE it! He got nuked by something. Something REALLY BAD happened to him. I went to his site, and his comments don't have any continuity. He keeps repeating how he was the originator of the apple architecture (which is true). If he was as serene as he says he is, he would not complain. I think he's somewhat (justifiably) bitter about the dismissal of his role in mainstreaming computing. He does not now seem to remember the warrior he was. That is sad. Pete.
You are espousing drivel. Neither myth matters much in the big picture, in an immediate sense. They play out over long periods of time, generally. We trust, we don't trust. We trust OUR OWN, we don't trust OUR OWN. It all dissolves into a personal trust of one's own vision. All artists must trust that. Geeks fear trust. Interesting conflict. Geeks benefit from trust more than most. Hey! We're SHAMAN! (NOT!)
Dave Brin wrote an article on Salon EXACTLY of the flavor that you folks always bitch that JonKatz does. He takes his time. He dissembles. He refers to 'other sources'. He WRITES!!! This is exactly what katz does. Rather well, IMHO. Katz does NOT deserve the shit he gets here. He's trying, and, dammit, TRYING COUNTS!! If you shitheads continue to attack guys like katz, I'll have to disseminate bullshit about your skills. Personally. You know who you are.
Man, are you right! Dna is not designed to do bit-level processing. It's a subset of how the larger universe(tm) does it's processing - with wavefronts, and interference. A Dna molecule is basically a holographic representation of the entire being it's meant to reproduce and, like optical holograms, you can hurt it pretty bad before it loses much data. That's the graceful failure feature you mention. Use a mess of dna and mitochondria as a neural-net cpu, and you might have a real product...
maybe I'm just too tired right now, but I did not detect any heisenberg ref's in the threads I've read here on this topic. Trying to instrument a thread of execution is usually death for that thread. I despise the notion of "performance monitors". If you build it right, it will work, and any anomalies usually succumb to thoughtful analysis. Instrumenting a network at the level you guys are talking about can kill it, severely. Get ye a good sniffer, and learn to read it's utterances.
I've gotta go with you, phred. An operation like E-bay's pushes the bleeding edge of transaction processing. It's a constantly fluctuating processing environment *defined by its data*. Ok. I know that's fuzzy; You have db records relating to particular bidding "threads" popping in and out of existence on the fly... Reconciling structures that hammer at and mercilessly fragment your files. You gotta garbage collect your disks, handle peak loads, and all the while try not to *thrash* anything, thereby bringing everything dependent upon the thrashing entity to its knees. Worse, thrashing isn't predictable, so you gotta distribute your loads, making the reconciliation process even worse. As you tried to say, phred, these guys are trying, unwittingly, do cut new ground in TP. Let's give 'em a little slack!
Now I'm no serious physicist, but I do know that 7500 LHY is a stone's throw interstellar-wise. It's important to remember that stellar events involve a shitload of relativistic phenomena that can make them very interesting. I could see a potential simultaneous collapse/hypernova scenario that could cause those polar jets to spew all sorts of elementary particles a distance that could equal the radius of a small galaxy, albeit briefly. Sort of like a flash bulb. Wouldn't want to be caught in that.
No stunts of this ilk can be pulled off without willing geeks who compromise their principles and lie down with the forcesss offf EEEvilll! I believe it may come to a geeks-day-off sort of event to fully inform these bozos that without geek cooperation, NOTHING happens! Planes don't fly, sick folks don't heal, energy stops,... The potential consequences are TRULY HIDEOUS. We should understand how much power we possess, and wield it if necessary. I know we're just as idiotic politically as any other group, but at least we have a few ethics between us if we look.
I gather that while spam is not prohibited by aforesaid action, retaliation is not. Note Virgin.net's reaction to being RBL'ed because of failure to police spam emanating from their operation. I'm sure the black-holing of even a few such emboldened domains should render this matter moot in a hurry.
YIKES! That was harsher than I meant it to be but was accurate, nonetheless. Len, you and yours over at salon are probably the only true online *magazine* out there. It reads like one... it FEELS like one... and now you're a linux partisan. All I can say is *THANK YOU* for supporting intellectual freedom. Thanks again...
Slashdot readers tend to be young, and overly enthusiastic. For every one of them, you get ten of me; over 40 and both enthused and indulgent. Most of these {negative} posters wouldn't know computer science from a bite upon their middle class indulged asses. They're hungry, and wish to be manly. (true, guys. You know these people. I did, when I was a kid.) True geeks write code and contribute. They're true warriors. Not pussy dilletantes battling over procedure. Performance matters. Wrap it however you want. Do not accept any criticism whatsoever from the lesser of these assholes without justification. Katz gets flamed here all the time, but you know what? The fucker can WRITE! Choose your enemies wisely.
Slashdot Mirror
Alan, I know you do a great deal of sound hacking, and I'm particulary looking forward to a time when meaningful full-duplex support is available without paying tribute to OSS. I've attempted to use their SB16 and Ensoniq support in their trial package, and the experience was excruciating. I banged my head to no avail. Abominable documentation. Our own free stuff is far better, IMHO. I ran out of time on their trial edition, and w/o source, I couldn't figure out what I was doing wrong, unlike the free drivers, which though sketchy, I could fathom.
Any hope for folks like me?
Interesting that without piracy most copyrighted works wouldn't be popular in the first place. If M$ hadn't shipped ms/pc-dos unprotected, and win 3.1 wasn't freely copyable we wouldn't have a windows-only world right now. M$ spread like a virus. Now the virus and its minions demand their due.
We know the answer.
Free software...
*And* (I'll say this again, so you guys may eventually get it):
Geek's Day Off.
We built it, and we can take it back, anytime we like.
Think about it. A Geek's Guild. Hmmmm....
Damn straight. Sums up the whole excercise for me. Look at Gates's face when he talks. If he was any more full of doo-doo he'd explode!
Hell, he has hand-jive consultants!
(very inside unless you know politics)
Not a good sign. He plans to do that.
It WILL happen. Bill wants power. Badly.
Maybe we can run him against steve forbes for global benevolent dictator.
You scared yet?
My post is rather old, by now, so noone is likely to read this, but for the sake of completeness, I'll explain ,cursorily, what that XOR gate did, to the extent that I can remember. (incidentally, I worked this out by *tracing circuit board foils* to figure out what was going on. How many of you HLL weenies have ever done THAT, eh?)
If I recall correctly, it worked in concert with cbm's ieee 488 like protocol that communicated with the drive. There were three lines, clk, data, and atn, and a rather baroque but effective dance done twixt the c64 and 1541 that allowed a device on the serial chain to take either a master or slave role. It was pretty sophisticated stuff, really. IMHO cbm's firmware was some the slickest code I've ever hacked.
Anyway, fastloaders got around the 'may I have a byte, please?' 'Yes you can!' 'Ok give it to me.' 'here it comes!' >get the byte 'I have it, thank you.' 'you're welcome.' cycle that made the 1541 so slow by running code in the drive (yes, you could do that! Gives me a woody just thinking about it!) that would read the disk directly, bypassing the os entirely, decode the group codes on the disk w/ your own optimised code, and do serial i/o manually, splitting the data bytes into bit pairs, and using two of the i/o lines to jam that data as fast as you could into the computer. Many programs to do this relied on knowing the clock speed and skew between the drive and computer cpu's, and just syncing up, and stuffing asynchronously a bunc of bit pairs in a row, resyncing, and doing it again, and again.
This is fine for a US machine, but european machines have differing clock speeds, because of different video standards. I was stuck doing a fastloader that had to be portable to europe.
I had to be synchronous.
I found that the XOR gate on the ATN line complemented the data on the data line. This allowed me to use 2 translation tables ( one for clk=1, one for clk=0 ) and transfer data on clk *edge*. doubling my speed. I was faster than apple's prodos on a c64!
Incidentally, for those who know the ins and out's of this stuff, the client didn't care about other devices being active on the serial bus. My previous code took that into account, but was us only. These guys (westwood) wanted portability. for it to work, only one drive and no printers could be on, or bus confusion resulted.
The lore involved in c64 fastdos stuff is really neat. Wish I had time and space to get into it more here.
I don't mean to be a jerk, trust me.
But if you have to ask that question, you need to learn a whole lot more about how gnu compliant software works. You need to know more about software, period.
Configure is a brilliant hack that determines what sort of machine software is being compiled for. You don't want to compile a new libc and attempt to install it unless you know EXACTLY what the hell you're doing. It's the heart and soul (next to your kernel) of the whole machine. Break it, and you won't boot.
Leave it alone. If you need a new libc at your point of development, get a new distro on cd, and reinstall.
"C programmers had to know assembler in those days. Believe it."
My personal feeling is that they should know assembler TODAY, as well, so as to have some frigging idea as to the consequences of their coding. Doesn't hurt to solder up a micro from scratch, using only one's wits and a data book or two, either. I did that in '83 w/a 8085 (my first computer!) and it simply rocks!
Not to mention the manly confidence that understanding a sytem from the metal up gives one!
8-}
Helps when writing fastloaders for C64's, lemme tellya!
Found a nifty use for that XOR gate on the 1541's ATN line, for sure!
(if you understood what I just said, you really scare me)
I've counseled a number of newbies to take this exact tack in their own educations, contrary to popular wisdom, and each and every one thanked me profusely for suggesting it. They eventually ran rings around their classmates, and actually GOT something out of (Acck!) DeVry!
I know I got flamed for this idea previously, but, now it's time.
You and I and all readers of this place are generally geeks. We build things. We research things. We solve problems.
We are the glue that holds this interconnected world together.
Hell! We created it!
It's high time we put our collective foot down. Let's take this thing we built back!
Let us put aside one day a year that we ALL stay home. And do nothing. at all.
Jews have that. Muslims have it. Geekhood is as close to a religion that I have. Wanna see the world shake?
Find a day.
Pick a day
That day, all geeks STAY HOME!
No work.
No calls.
No nothing.
You'll be going to mars with the blessing of the speaker of the house in 6 mos.
Geeks are assumed to be pussies.
WRONG!
We are true warriors. We put our immediate needs on hold for the larger cause.
Geeks rule this planet at this time.
Assume that mantle responsibly. Assert your authority.
Whether you like it or not, you're piloting this thing.
Do it right.
I haven't the time to read all the various posts on this subject, but this crosswitch thing has been obvious to me since '74. It's already been done. Design your bus according to all those transmission line stuff you learned in skool and crank the living hell out of it. Multiplex, ATM-like. 500mhz was doable in *1975* with ecl logic and a big power supply (current mode switching. still a good idea.)
GAAS gates have propagation times in the single digit PICOSECONDS! Use them!
I leave the rest as an excercise to the observant reader.
I don't argue with anything you've said. I forgot to mention the thread-per-interface thing and feel a little silly since I realize that was our bottleneck. What I meant was that IIS does a thing similar to squid, where it allocates a bunch of RAM assumedly user-configurable, and rule-based, for caching frequently requested pages within its own process space. Apache doesn't do this by default, which, IMHO is a good idea.
As to squid and dynamic content, it's insanely configurable in that arena.
I also implied that the apache implementation in question would incorporate mod_perl and php modules as a piece of the instance. so as to avoid the forking you spoke of.
An additional thing one can do with apache so as to avoid needless spawning of new processes is to extend the lifetime of the daemon. RTFM on apache.conf.
BTW mod_rewrite rocks!
I'm rather ashamed not to know that. I love his work with kids, dont get me wrong. I just love his work as a great coder. He made that world his. He was a fscking van halen of coding.
So was Bill Budge. Wonder where he is. He truly hacked. No more? I don't get it. A natural math prodigy. I would've loved him as a friend. BIG PICTURE. He got it, somehow.
Damn! You're right! I remember reading about this in a deadly flame thread on comp.protocols.tcpip. the guy who instigated it did us all a huge favor, as it made everyone think in a state-machine kinda way, which should be elemental to anyone who knows computers.
Sometimes we abstract so much, we forget these things are stupid and have to be slapped into civilty from the metal on up!
Thanks for a great observation!
Any apache site expecting to serve tons of static pages should run squid in accel mode in front of apache. apache's cache (IF USED???) doesn't even come close to squid, and the apache team will readily admit it. .asp.
I can't believe the redhat guys didn't embrace this strategy since it's well known that a key factor in IIS performance is the fact that it caches it's own static pages IN RAM when possible! This is a no-brainer. Note the big increase in performance between 256M and 1G.
Personally, I believe, even given Linux's shortcomings in its TCP stack, we should smoke IIS with a properly configured server.
As for ACTIVE content.. Done properly, mod_perl or php should kill
Right on , pal.
These guys are morons. Nobody owns the world of numbers. And nobody understands numbers better than geeks (us) do.
Game's already over. We won. There's no way to enforce this shit in the US without a soviet-style Surveillance scheme, where everyone is monitored all the time.
We also have a very cool 2nd amendment. (guns for everyone) We may soon have to excercise it, if this stuff continues.
What the hell happened to this guy? DAMN!
If any of you weenie hacker wannabies ever read any of his code, you would see the clear, cool mind of a fscking GENIUS!
MAN his stuff was elegant! You could sit, pass it around, and just ADMIRE it!
He got nuked by something. Something REALLY BAD happened to him.
I went to his site, and his comments don't have any continuity. He keeps repeating how he was the originator of the apple architecture (which is true). If he was as serene as he says he is, he would not complain. I think he's somewhat (justifiably) bitter about the dismissal of his role in mainstreaming computing.
He does not now seem to remember the warrior he was. That is sad.
Pete.
You are espousing drivel. Neither myth matters much in the big picture, in an immediate sense. They play out over long periods of time, generally. We trust, we don't trust. We trust OUR OWN, we don't trust OUR OWN.
It all dissolves into a personal trust of one's own vision. All artists must trust that. Geeks fear trust. Interesting conflict. Geeks benefit from trust more than most. Hey! We're SHAMAN! (NOT!)
Dave Brin wrote an article on Salon EXACTLY of the flavor that you folks always bitch that JonKatz does. He takes his time. He dissembles. He refers to 'other sources'.
He WRITES!!!
This is exactly what katz does. Rather well, IMHO.
Katz does NOT deserve the shit he gets here. He's trying, and, dammit, TRYING COUNTS!!
If you shitheads continue to attack guys like katz, I'll have to disseminate bullshit about your skills. Personally. You know who you are.
So do I.
Man, are you right! Dna is not designed to do bit-level processing. It's a subset of how the larger universe(tm) does it's processing - with wavefronts, and interference. A Dna molecule is basically a holographic representation of the entire being it's meant to reproduce and, like optical holograms, you can hurt it pretty bad before it loses much data. That's the graceful failure feature you mention.
Use a mess of dna and mitochondria as a neural-net cpu, and you might have a real product...
maybe I'm just too tired right now, but I did not detect any heisenberg ref's in the threads I've read here on this topic. Trying to instrument a thread of execution is usually death for that thread. I despise the notion of "performance monitors".
If you build it right, it will work, and any anomalies usually succumb to thoughtful analysis.
Instrumenting a network at the level you guys are talking about can kill it, severely.
Get ye a good sniffer, and learn to read it's utterances.
I've gotta go with you, phred. An operation like E-bay's pushes the bleeding edge of transaction processing. It's a constantly fluctuating processing environment *defined by its data*.
Ok. I know that's fuzzy; You have db records relating to particular bidding "threads" popping in and out of existence on the fly... Reconciling structures that hammer at and mercilessly fragment your files. You gotta garbage collect your disks, handle peak loads, and all the while try not to *thrash* anything, thereby bringing everything dependent upon the thrashing entity to its knees.
Worse, thrashing isn't predictable, so you gotta distribute your loads, making the reconciliation process even worse.
As you tried to say, phred, these guys are trying, unwittingly, do cut new ground in TP. Let's give 'em a little slack!
Not bad! Maybe this exactly the sort of thing ol' Ayn was thinking of?
Now I'm no serious physicist, but I do know that 7500 LHY is a stone's throw interstellar-wise. It's important to remember that stellar events involve a shitload of relativistic phenomena that can make them very interesting. I could see a potential simultaneous collapse/hypernova scenario that could cause those polar jets to spew all sorts of elementary particles a distance that could equal the radius of a small galaxy, albeit briefly. Sort of like a flash bulb. Wouldn't want to be caught in that.
No stunts of this ilk can be pulled off without willing geeks who compromise their principles and lie down with the forcesss offf EEEvilll! ...
I believe it may come to a geeks-day-off sort of event to fully inform these bozos that without geek cooperation, NOTHING happens! Planes don't fly, sick folks don't heal, energy stops,
The potential consequences are TRULY HIDEOUS.
We should understand how much power we possess, and wield it if necessary. I know we're just as idiotic politically as any other group, but at least we have a few ethics between us if we look.
I gather that while spam is not prohibited by aforesaid action, retaliation is not. Note Virgin.net's reaction to being RBL'ed because of failure to police spam emanating from their operation.
I'm sure the black-holing of even a few such emboldened domains should render this matter moot in a hurry.
YIKES!
That was harsher than I meant it to be but was accurate, nonetheless.
Len, you and yours over at salon are probably the only true online *magazine* out there. It reads like one... it FEELS like one... and now you're a linux partisan.
All I can say is *THANK YOU* for supporting intellectual freedom.
Thanks again...
Slashdot readers tend to be young, and overly enthusiastic. For every one of them, you get ten of me; over 40 and both enthused and indulgent.
Most of these {negative} posters wouldn't know computer science from a bite upon their middle class indulged asses. They're hungry, and wish to be manly.
(true, guys. You know these people. I did, when I was a kid.)
True geeks write code and contribute. They're true warriors. Not pussy dilletantes battling over procedure.
Performance matters. Wrap it however you want.
Do not accept any criticism whatsoever from the lesser of these assholes without justification.
Katz gets flamed here all the time, but you know what?
The fucker can WRITE!
Choose your enemies wisely.