It also stands to reason that with a network using CSMA/CD (like 802.11 a/b/g), of course having a slower device on the network is going to decrease the total available throughput. Only one station at once can be transmitting, so you can easily say that the scarce resource on the network is time. A slow node is using that time less efficiently, by taking more time to transfer each bit. Which of course leaves proportionally less time available to all of the other nodes on the network.
Apparently you don't understand the meaning of "I/O bound". Okay, you have SCSI. We'll say that through some amazing physics this allows you to read twice as much data from disk per unit time than the rest of us. Your virus scan task will happily take all of it, leaving pretty much exactly the same amount of "whatever's left" for loading Halo maps. Allowing multiple requests in flight doesn't help latency that much when the real issue has a lot more to do with the time it takes heads to fly across a platter.
WPA-PSK "complicates" things? The standard setup, which you're likely to see in home use, is like WEP, except you don't have to worry about bullshit like "why is this giving me four different slots for the key?" and "what's a hex?". All the information I need to provide to connect to my network is SSID, and PSK (an ordinary string, which gets securely hashed, the same way mind you, into a key on all of my devices).
Support is a little more of an issue, but actually not relevant for situations like TFA. If you're setting up a network in your business, you don't have to support Nintendo DSs. And you can just buy network cards with drivers that have made it out of the stone age.
Right, but the more common usage doesn't reflect this because it uses "code" as a mass noun. You don't have a singular "code" or plural "codes"; you have some code, a piece of code, the Apache code, or all of the code that was ever written in C. That's my point. It's not a difference in scale, it's a difference in usage entirely.
Heh, alright. As an entirely different type of "real programmer", it just sounds ignorant to me. "Codes" is usually a word used by people who don't understand that code is code is code.
Yes. Because you can't bend metal at all! Or a thin layer of wood. I mean, man, wood, that stuff just shatters if you try to bend it. Anyway, it's a good thing that there's no metal at all in DVDs. Because metal, you just can't bend that shit.
Well... I dunno about that. I actually find that cell phones usually have too few buttons and that their buttons are too small if you want to do anything really useful with them. It's best to just stick to making phone calls.
When it comes to a PDA, I think that perhaps the best form-factor out there is the clamshell Zaurus. Or at least it would be if they filled the entire "screen area" with screen. Yeah, it's a bit bigger than people have come to expect from a PDA, but it's still quite manageable, and it even fits in a pocket if you have big pockets. And that buys you a very good amount of visible information, buttons and such that are big enough to interact with, and a keyboard that's actually comfortable after some adjustment.
You know, this actually makes some real sense. Look how long the Dreamcast managed to survive after its death due to the hack that allowed the "homebrew scene". Of course, the same hack may well have been what killed the Dreamcast, but that's a controllable factor. Lock out unlicensed games during hte profitable period in the system's life. Then eventually something new comes out, and the games aren't selling like they used to. But most likely, the cost of production of the system has gone way down. So now you turn things around. Allow the homebrew folks to produce cheap games (and if there's some piracy in there too, don't worry too much) -- and make money off of selling the hardware for the first time. Interesting.
B is about cost, in both money and time. it's the way project managers think, or technical folks who rise above just pure implementation. but A is about why that cost is worth it.
No, it's not. It's about unrelated fluff that might have something to do with how you came to the idea that B was worth it, and which might have been relevant at a strategy meeting 6 months ago. In itself, B is worth it because it will increase sales by $2 million a year. That's its nature, and its entire relevance to your business position. The rest, in context, is just cheerleading.
But even still there's a difference in scale. With the cloning hoax, the odds that some secretive scientist managed to make everything work out for a human cloning were one in a billion at best, but they were there. With this compression claim, the odds are one-in-an-"everything we know about math, starting from arithmetic, is wrong".
You're an asshole and besides that you're wrong. The left lane is not the "fast" lane. It is the passing lane. You know all those "KEEP RIGHT EXCEPT TO PASS" signs you see all over? What do you think they mean, numbnuts?
You're an asshole and besides that you're wrong. Yes, a few states actually say that specifically. Most are considerably more reasonable. Pennsylvania, for example, says this in 75 PA 3313:
Except as provided in paragraph (2) and unless otherwise posted, upon all limited access highways having two or more lanes for traffic moving in the same direction, all vehicles shall be driven in the right-hand lanes when available for traffic except when any of the following conditions exist:
When overtaking and passing another vehicle proceeding in the same direction,
When traveling at a speed greater than the traffic flow.
When moving left to allow traffic to merge.
When preparing for a left turn at an intersection, exit or into a private road or driveway when such left turn is legally permitted
You can clearly see that the rule isn't "keep right except to pass", it's "keep right except to pass, or to drive fast, or to get out of the way of merging traffic." This is in fact the more common rule in US states, as far as I've been able to determine. The code goes on to explain that "vehicles proceeding at less than normal speed" are required to stay right; other states specifically enumerate an offense of "obstructing traffic" by driving slowly on the left.
Oh, and the real zinger is that your quote doesn't support your argument at all. It begins by saying that the section only applies to a vehicle being driven "at a speed less than the normal speed of traffic". If you're not driving slowly, then none of that wording applies.
Which is just awesome if you really think about it. Suppose you have a 6-lane highway, and everybody is so in love with the law that they all do exactly the speed limit. Nobody would ever be passing anyone, so the road would only be operating at 1/3 capacity, and traffic would be backed up all the way to New Jersey (without regard to which state this hypothetical road is in).
Thank you. Yeah, okay, tell me that Java can be just as efficient as anything else, you know what, I believe you. But when your app still takes 4 times as long to start up, uses 3 times as much memory, and is noticeably less responsive than a feature-equivalent app written in another language, I don't care about the potential. I care about the fact that, like everyone else so far, you've failed to reach that potential, and I care about having an app that actually behaves.
No, this isn't about freenet, but about another app that's rather popular at the moment. Use your imagination.
The concept of "market" is a direct extension of the concept of "property", which is a direct extension of the concept of "human life". Price gouging can't meaningfully exist. In the case of, say, a hurricane, you will get a spike in demand for some good, or an interruption in supply, or both. There has to be some way to apportion those goods that are available, and the market is as good an answer today as it was yesterday. Some people are going to end up doing without some things, maybe even essential things, but that can't be changed. In the case where you enforce a price cap, what changes is that a somewhat different set of people ends up doing without (due to the enforced market breakdown), and that the merchants supplying the demanded good suffer by having to absorb upstream costs themselves, possibly compounding the shortage. Oh yeah, and it further encourages theft, black markets, and people shooting each other on the streets over loaves of bread. Good job.
I don't think it would be too much of a spoiler to say that she doesn't get too much of a chance to be good or bad. Yes, she's a significant character in a way, but that doesn't mean she has a lot of lines. Come to think of it, there are very few characters in the movie that have more than two or three lines; that's just the way the thing was written.
I'm not saying we shouldn't do everything possible to keep our astronauts safe, but if they hadn't contracted the shuttle out to the lowest bidder in the first place, we might have better craft.
Actually, in light of consideration 1 (money), if they hadn't contracted out to the lowest bidder in the first place they would have had no craft.
Slashdot Mirror
It also stands to reason that with a network using CSMA/CD (like 802.11 a/b/g), of course having a slower device on the network is going to decrease the total available throughput. Only one station at once can be transmitting, so you can easily say that the scarce resource on the network is time. A slow node is using that time less efficiently, by taking more time to transfer each bit. Which of course leaves proportionally less time available to all of the other nodes on the network.
But it's so much less work to just quote the bullshit that the submitter came up with, regardless of whether it has any basis in reality.
Apparently you don't understand the meaning of "I/O bound". Okay, you have SCSI. We'll say that through some amazing physics this allows you to read twice as much data from disk per unit time than the rest of us. Your virus scan task will happily take all of it, leaving pretty much exactly the same amount of "whatever's left" for loading Halo maps. Allowing multiple requests in flight doesn't help latency that much when the real issue has a lot more to do with the time it takes heads to fly across a platter.
WPA-PSK "complicates" things? The standard setup, which you're likely to see in home use, is like WEP, except you don't have to worry about bullshit like "why is this giving me four different slots for the key?" and "what's a hex?". All the information I need to provide to connect to my network is SSID, and PSK (an ordinary string, which gets securely hashed, the same way mind you, into a key on all of my devices).
Support is a little more of an issue, but actually not relevant for situations like TFA. If you're setting up a network in your business, you don't have to support Nintendo DSs. And you can just buy network cards with drivers that have made it out of the stone age.
Right, but the more common usage doesn't reflect this because it uses "code" as a mass noun. You don't have a singular "code" or plural "codes"; you have some code, a piece of code, the Apache code, or all of the code that was ever written in C. That's my point. It's not a difference in scale, it's a difference in usage entirely.
Heh, alright. As an entirely different type of "real programmer", it just sounds ignorant to me. "Codes" is usually a word used by people who don't understand that code is code is code.
What the hell is that about? Is this a bad spy movie? "Give us the codes or we'll make it very bad for you, Mr. Glossy Photo..."
Yes. Because you can't bend metal at all! Or a thin layer of wood. I mean, man, wood, that stuff just shatters if you try to bend it. Anyway, it's a good thing that there's no metal at all in DVDs. Because metal, you just can't bend that shit.
+1 Not Fantastically Stupid Like Everyone Else Today
Slashdot needs this moderation option almost as much as it needs
-1 Just Plain Obviously Wrong Stuff Quoted as Fact
Well... I dunno about that. I actually find that cell phones usually have too few buttons and that their buttons are too small if you want to do anything really useful with them. It's best to just stick to making phone calls.
When it comes to a PDA, I think that perhaps the best form-factor out there is the clamshell Zaurus. Or at least it would be if they filled the entire "screen area" with screen. Yeah, it's a bit bigger than people have come to expect from a PDA, but it's still quite manageable, and it even fits in a pocket if you have big pockets. And that buys you a very good amount of visible information, buttons and such that are big enough to interact with, and a keyboard that's actually comfortable after some adjustment.
Not to be rude, but his name still isn't Felton, just like it hasn't been any other time some slashdotter misspells it.
Er... which good laws are those? 99 and 44/100% (at least) of laws are useless, and merely stand in the way of justice.
You know, this actually makes some real sense. Look how long the Dreamcast managed to survive after its death due to the hack that allowed the "homebrew scene". Of course, the same hack may well have been what killed the Dreamcast, but that's a controllable factor. Lock out unlicensed games during hte profitable period in the system's life. Then eventually something new comes out, and the games aren't selling like they used to. But most likely, the cost of production of the system has gone way down. So now you turn things around. Allow the homebrew folks to produce cheap games (and if there's some piracy in there too, don't worry too much) -- and make money off of selling the hardware for the first time. Interesting.
B is about cost, in both money and time. it's the way project managers think, or technical folks who rise above just pure implementation. but A is about why that cost is worth it.
No, it's not. It's about unrelated fluff that might have something to do with how you came to the idea that B was worth it, and which might have been relevant at a strategy meeting 6 months ago. In itself, B is worth it because it will increase sales by $2 million a year. That's its nature, and its entire relevance to your business position. The rest, in context, is just cheerleading.
"Size of the encryption algorithm"? In what sense exactly?
But even still there's a difference in scale. With the cloning hoax, the odds that some secretive scientist managed to make everything work out for a human cloning were one in a billion at best, but they were there. With this compression claim, the odds are one-in-an-"everything we know about math, starting from arithmetic, is wrong".
Read on. He's as wrong about California as anywhere else. Apparently he thinks he's in New Jersey. They have a real keep-right law.
You're an asshole and besides that you're wrong. Yes, a few states actually say that specifically. Most are considerably more reasonable. Pennsylvania, for example, says this in 75 PA 3313:
You can clearly see that the rule isn't "keep right except to pass", it's "keep right except to pass, or to drive fast, or to get out of the way of merging traffic." This is in fact the more common rule in US states, as far as I've been able to determine. The code goes on to explain that "vehicles proceeding at less than normal speed" are required to stay right; other states specifically enumerate an offense of "obstructing traffic" by driving slowly on the left.
Oh, and the real zinger is that your quote doesn't support your argument at all. It begins by saying that the section only applies to a vehicle being driven "at a speed less than the normal speed of traffic". If you're not driving slowly, then none of that wording applies.
Which is just awesome if you really think about it. Suppose you have a 6-lane highway, and everybody is so in love with the law that they all do exactly the speed limit. Nobody would ever be passing anyone, so the road would only be operating at 1/3 capacity, and traffic would be backed up all the way to New Jersey (without regard to which state this hypothetical road is in).
Thank you. Yeah, okay, tell me that Java can be just as efficient as anything else, you know what, I believe you. But when your app still takes 4 times as long to start up, uses 3 times as much memory, and is noticeably less responsive than a feature-equivalent app written in another language, I don't care about the potential. I care about the fact that, like everyone else so far, you've failed to reach that potential, and I care about having an app that actually behaves.
No, this isn't about freenet, but about another app that's rather popular at the moment. Use your imagination.
The concept of "market" is a direct extension of the concept of "property", which is a direct extension of the concept of "human life". Price gouging can't meaningfully exist. In the case of, say, a hurricane, you will get a spike in demand for some good, or an interruption in supply, or both. There has to be some way to apportion those goods that are available, and the market is as good an answer today as it was yesterday. Some people are going to end up doing without some things, maybe even essential things, but that can't be changed. In the case where you enforce a price cap, what changes is that a somewhat different set of people ends up doing without (due to the enforced market breakdown), and that the merchants supplying the demanded good suffer by having to absorb upstream costs themselves, possibly compounding the shortage. Oh yeah, and it further encourages theft, black markets, and people shooting each other on the streets over loaves of bread. Good job.
I don't think it would be too much of a spoiler to say that she doesn't get too much of a chance to be good or bad. Yes, she's a significant character in a way, but that doesn't mean she has a lot of lines. Come to think of it, there are very few characters in the movie that have more than two or three lines; that's just the way the thing was written.
non-gel rollerballs for the win, definitely! Most enjoyable writing/drawing experience I've ever found.
I'm not saying we shouldn't do everything possible to keep our astronauts safe, but if they hadn't contracted the shuttle out to the lowest bidder in the first place, we might have better craft.
Actually, in light of consideration 1 (money), if they hadn't contracted out to the lowest bidder in the first place they would have had no craft.
apwgm xuafz uebpt