I have an old 486 that I've stripped down to the absolute bare bones. All it is is a floppy drive, motherboard, and powersupply, plus nics and a video card. For software, I run LRP on a... you guessed it... floppy! Easy to manipulate, you can write-protect the disk, it's quieter... overall a nice solution.
Well, perhaps out in Central Canada. Here in the west (Alberta), most bars have a pleasant mix, usually with at least one or two Big Rock brews on tap... mmm... Traditional.:) Heck, I've really never seen Algonquin (which, BTW, sucks) on tap around here, and Coors isn't that common either... thank god for that.:)
BTW, it's not like that kind of exclusive licensing is that uncommon. Look at most restaurants... Pepsi or Coke products?
Unfortunately, your explanation is wrong, particularly WRT the role of NVP in the Internet. ie, it has none. Today, the great majority of digital voice sent over the 'net is transmitted using RTP (Real-Time Protocol), which is a protocol layered over IP (ie, at the same level as UDP or TCP). In fact, RTP is also used for things like digital audio, as well (ie, RealAudio). Interestingly, digital voice these days still uses what are essentially separated control and data streams. Today, SIP is used for the signalling portion, and then RTP kicks in for the transport.
As for GSM, etc, within the wireless network itself, that stuff is transmitted as radio frames using fairly standard communication protocols over what is essentially circuit-switched networks (not quite... it's ATM and other things, but it's all point-to-point links in a tree structure) into the core telephony network. Well, at least, that's what the standards dictate. Within company backbones, it's quite possible they're using RTP or something like that for sending the voice, assuming they're using an IP-based, packet-switched transport, but I wouldn't put money on it, especially since I have no direct knowledge in that area of the telephony industry. It's quite likely they're using various proprietary technologies for that. But they're certainly NOT using NVP.
BUT, your average kid using a P2P program isn't the kind of person Moby is referring to. He specifically referred to "very tech savvy fans", computer geeks, that sort of thing... ie, folks who are intelligent and technologically adept. And, I hate to say it, but your average p2p-using kid is neither of these things.:) Although, it's rather presumptious of Moby to assume he HAS an intelligent, tech-savvy audience.
Umm... just OOC, why not get yourself a steroid or Ventolin inhaler, take a pre-emptive hit before physed, and then get some exercise like everyone else? I mean, I understand what asthma is like... I have a pretty good case of it myself. But I'm still an avid cyclist and, occasionally, basketball player. I just keep my inhaler around with me. Plus, I've found that the exercise has helped me strengthen my lungs so that my attacks aren't nearly as severe as they used to be.
Actually, I have to say, depending on the settings of the machine, DDR can really provide bang for the buck. Here in Edmonton Alberta, Canada, the DDR machines I've encountered have all been a buck for 5 dances, which amounts to about 15 minutes of playtime. So, for two bucks, you get 30 minutes of playtime and a good workout. Compare this to many other games (particularly racers) where you spend two bucks (or more!) and play for about 5 to 10 minutes, depending on your skills, and DDR seems like a pretty good deal to me.
Actually, this concept is a lot more complicated than just the traditional packet-switching we see in the Internet today (although, it's not "new"). The network architecture implied here is referred to as an adhoc, or parasitic network. These networks have to dynamically update the network topology in real time in order to forward traffic appropriately, which is horribly more complicated than the internet we have today which is, in essence, statically routed. The development of these types of networks is currently a hot topic in the networking research community, since there are a number of interesting applications.
I have to say, sir, that your characterization of Unix "geeks" is more than just a bit insulting. I work in a small firm myself, and we are strictly a Unix house. But we do not have a single "geek", as you describe, in the company, and after completing a BSc in computing science, I can tell you that the majority of grads, who could be considered Unix "geeks", do not fall in this stereotype either. The world is changing, "son", and so is the face of Unix and Computing Science.
Moreover, the fact that you're advocating selecting a product based on the stereotypical appearance of its associated software administrator suggests to me that you're anything but professional. A product should be selected based on it's technical merits, cost to administer, etc, etc, NOT based on the type of people you *think* you will be forced to employ in order to use said product. Now, whether you select IIS based on those criteria is your decision. But pidgeon-holing every Unix developer as a "geek" and making technical decisions based on that viewpoint is both narrow-minded and short-sighted.
And to add to this, even in 3G wireless, they're still talking something like 3-400 ms in roundtrip delay... and they're having a bitch of a time meeting that, BTW.:)
Morally speaking, why? How is killing any other living creature different from killing a human being. Simply because it's "different from us"? Well, let's try a thought experiment. Suppose, some day, we travel to the stars and run across a new, sentient species. Is it okay for us to kill them?
The reason the live music trading community (most notably etree.org [etree.org]) uses the shorten format is because there was not a way to widely distribute exact copies of, say, master DATs. Now, assuming the person transferring the DAT, did a reasonably good job, every person after that who receives the SHN files can create an exact copy of that DAT. This is crucial because of the way shows are distributed. One person gets a copy from his friend, and he passes it on to his friends. If there was a lossy step involved in the middle of the chain, each copy would be worse than the one before. Note tape trading. Copying a...
Hmm... but you're making an assumption here that, for some reason, every person in the chain would re-encode the audio data into said lossy format before sending it to the next person in the tape tree, which would (hopefully) not be true, in general. For example, I try to keep an archive of all the compressed audio files I download, even if I burn them to CD. In fact, often times, I just make a multisession disk with the compressed audio on the data portion. Then again, there's no telling what an uneducated trader might do.:)
I guess what I'm driving at here is that, if the traders were bright enough not to re-encode all the time, and just pass around the original files, a compressed format could make trading a LOT easier for those with reduced bandwidth. Frankly, I think the community chose Shorten for the same reason some audiophiles prefer vinyl... they think it sounds better (and, IMHO, given the quality of your average taped show, a compressed format probably wouldn't affect quality that much.:)
I would partially agree. Yes, in the real world, there is some very complicated code. BUT, if you write the code correctly, you should be able to understand it with relatively minimal commenting. Basically, comments should exist to clarify parts of the code that are difficult to understand, or to provide information not immediately obvious (ie, code assumptions, side-effects, etc). The rest should be self-documenting. If it's not, there's something wrong. Period. After all, how can someone else maintain the code if they constantly have to read the comments just to figure out what it's doing?
First, you have to build what the consumer wants, not what is academically "correct". Read his comments about Word Perfect. From a strictly CS standpoint, they wrote GREAT software. All hand tuned Assembly.
I take great issue with this. Why on earth would you think that hand-tuned assembler is "technically excellent" from a "CS standpoint"? From a CS standpoint, technically excellent code is code that is well structured, well documented, easy to maintain, and easy to understand. I would argue that hand-tuned assembler is rarely any of these things. And I would also argue that customers would *much* rather have code that is academically correct... if all code was well written, well designed, and well documented, I'd imagine your average large software project would have significantly fewer bugs, and that's probably something your average customer would be pretty happy with.
Try using XPLNS... search Freshmeat for it. It's free and does a fairly decent job of producing charts. 'course, I'm no expert in star charting apps, so I may not be the best to judge.:) Anyway, I've used it a number of times to generate charts for various things.
Actually, that impact really didn't effect human civilization at all. IIRC, there were little to no casualities involved, and in fact, the event wasn't even reported until long after it happened, since, at the time, the Czar didn't care much for the Siberian region or it's inhabitants. So, compared to the fall of an entire civilization, I'd say this particular event doesn't really compare.
Re:I'll switch to Emacs when I can fold text with
on
GNU Emacs 21
·
· Score: 2
And a little nitpick... it's "voila!" (a should be accented), a French word which, when translated, means "there!".
Slashdot Mirror
I have an old 486 that I've stripped down to the absolute bare bones. All it is is a floppy drive, motherboard, and powersupply, plus nics and a video card. For software, I run LRP on a... you guessed it... floppy! Easy to manipulate, you can write-protect the disk, it's quieter... overall a nice solution.
LOL! Sorry... Rickards Red and related beers are NOT Microbrews. They're brewed by Molson! Unless you're talking about a different Rickards Red... :)
BTW, it's not like that kind of exclusive licensing is that uncommon. Look at most restaurants... Pepsi or Coke products?
Unfortunately, your explanation is wrong, particularly WRT the role of NVP in the Internet. ie, it has none. Today, the great majority of digital voice sent over the 'net is transmitted using RTP (Real-Time Protocol), which is a protocol layered over IP (ie, at the same level as UDP or TCP). In fact, RTP is also used for things like digital audio, as well (ie, RealAudio). Interestingly, digital voice these days still uses what are essentially separated control and data streams. Today, SIP is used for the signalling portion, and then RTP kicks in for the transport.
As for GSM, etc, within the wireless network itself, that stuff is transmitted as radio frames using fairly standard communication protocols over what is essentially circuit-switched networks (not quite... it's ATM and other things, but it's all point-to-point links in a tree structure) into the core telephony network. Well, at least, that's what the standards dictate. Within company backbones, it's quite possible they're using RTP or something like that for sending the voice, assuming they're using an IP-based, packet-switched transport, but I wouldn't put money on it, especially since I have no direct knowledge in that area of the telephony industry. It's quite likely they're using various proprietary technologies for that. But they're certainly NOT using NVP.
Ummm... what about Transformiix? That would be the Mozilla XSLT engine, which is built right into Moz 1.0. Check out the project website here.
Okay, this really deserves a "Are the moderators on crack?!?" post. WTF... insightful?!
BUT, your average kid using a P2P program isn't the kind of person Moby is referring to. He specifically referred to "very tech savvy fans", computer geeks, that sort of thing... ie, folks who are intelligent and technologically adept. And, I hate to say it, but your average p2p-using kid is neither of these things. :) Although, it's rather presumptious of Moby to assume he HAS an intelligent, tech-savvy audience.
But... but... Simcity said this would happen!!!
Umm... just OOC, why not get yourself a steroid or Ventolin inhaler, take a pre-emptive hit before physed, and then get some exercise like everyone else? I mean, I understand what asthma is like... I have a pretty good case of it myself. But I'm still an avid cyclist and, occasionally, basketball player. I just keep my inhaler around with me. Plus, I've found that the exercise has helped me strengthen my lungs so that my attacks aren't nearly as severe as they used to be.
Actually, I have to say, depending on the settings of the machine, DDR can really provide bang for the buck. Here in Edmonton Alberta, Canada, the DDR machines I've encountered have all been a buck for 5 dances, which amounts to about 15 minutes of playtime. So, for two bucks, you get 30 minutes of playtime and a good workout. Compare this to many other games (particularly racers) where you spend two bucks (or more!) and play for about 5 to 10 minutes, depending on your skills, and DDR seems like a pretty good deal to me.
Actually, this concept is a lot more complicated than just the traditional packet-switching we see in the Internet today (although, it's not "new"). The network architecture implied here is referred to as an adhoc, or parasitic network. These networks have to dynamically update the network topology in real time in order to forward traffic appropriately, which is horribly more complicated than the internet we have today which is, in essence, statically routed. The development of these types of networks is currently a hot topic in the networking research community, since there are a number of interesting applications.
Which, BTW, is one of the topics the IETF is working on... along with a ton of other researchers.
And to truly hammer home my point, I neglect to preview and show my excellent HTML formatting skills. Lovely... *sigh* :)
Moreover, the fact that you're advocating selecting a product based on the stereotypical appearance of its associated software administrator suggests to me that you're anything but professional. A product should be selected based on it's technical merits, cost to administer, etc, etc, NOT based on the type of people you *think* you will be forced to employ in order to use said product. Now, whether you select IIS based on those criteria is your decision. But pidgeon-holing every Unix developer as a "geek" and making technical decisions based on that viewpoint is both narrow-minded and short-sighted.
Umm, do you think a regular ol' fibre line would be able to withstand seismic activity, a volcano, or a depth charge? Somehow I doubt it...
And to add to this, even in 3G wireless, they're still talking something like 3-400 ms in roundtrip delay... and they're having a bitch of a time meeting that, BTW. :)
Morally speaking, why? How is killing any other living creature different from killing a human being. Simply because it's "different from us"? Well, let's try a thought experiment. Suppose, some day, we travel to the stars and run across a new, sentient species. Is it okay for us to kill them?
The reason the live music trading community (most notably etree.org [etree.org]) uses the shorten format is because there was not a way to widely distribute exact copies of, say, master DATs. Now, assuming the person transferring the DAT, did a reasonably good job, every person after that who receives the SHN files can create an exact copy of that DAT. This is crucial because of the way shows are distributed. One person gets a copy from his friend, and he passes it on to his friends. If there was a lossy step involved in the middle of the chain, each copy would be worse than the one before. Note tape trading. Copying a...
:)
:)
Hmm... but you're making an assumption here that, for some reason, every person in the chain would re-encode the audio data into said lossy format before sending it to the next person in the tape tree, which would (hopefully) not be true, in general. For example, I try to keep an archive of all the compressed audio files I download, even if I burn them to CD. In fact, often times, I just make a multisession disk with the compressed audio on the data portion. Then again, there's no telling what an uneducated trader might do.
I guess what I'm driving at here is that, if the traders were bright enough not to re-encode all the time, and just pass around the original files, a compressed format could make trading a LOT easier for those with reduced bandwidth. Frankly, I think the community chose Shorten for the same reason some audiophiles prefer vinyl... they think it sounds better (and, IMHO, given the quality of your average taped show, a compressed format probably wouldn't affect quality that much.
I would partially agree. Yes, in the real world, there is some very complicated code. BUT, if you write the code correctly, you should be able to understand it with relatively minimal commenting. Basically, comments should exist to clarify parts of the code that are difficult to understand, or to provide information not immediately obvious (ie, code assumptions, side-effects, etc). The rest should be self-documenting. If it's not, there's something wrong. Period. After all, how can someone else maintain the code if they constantly have to read the comments just to figure out what it's doing?
First, you have to build what the consumer wants, not what is academically "correct". Read his comments about Word Perfect. From a strictly CS standpoint, they wrote GREAT software. All hand tuned Assembly.
I take great issue with this. Why on earth would you think that hand-tuned assembler is "technically excellent" from a "CS standpoint"? From a CS standpoint, technically excellent code is code that is well structured, well documented, easy to maintain, and easy to understand. I would argue that hand-tuned assembler is rarely any of these things. And I would also argue that customers would *much* rather have code that is academically correct... if all code was well written, well designed, and well documented, I'd imagine your average large software project would have significantly fewer bugs, and that's probably something your average customer would be pretty happy with.
Try using XPLNS... search Freshmeat for it. It's free and does a fairly decent job of producing charts. 'course, I'm no expert in star charting apps, so I may not be the best to judge. :) Anyway, I've used it a number of times to generate charts for various things.
Ahh, true... I remember that as well. Still... if that did anything to civilization, all it did was let us a little more. :)
Actually, that impact really didn't effect human civilization at all. IIRC, there were little to no casualities involved, and in fact, the event wasn't even reported until long after it happened, since, at the time, the Czar didn't care much for the Siberian region or it's inhabitants. So, compared to the fall of an entire civilization, I'd say this particular event doesn't really compare.
And a little nitpick... it's "voila!" (a should be accented), a French word which, when translated, means "there!".
Yes... yes, precisely... :)