The comment implicit in your response is right. What I mean is that I agree with the idea that it all depends on what you're doing. For instance, my thought that "distance is bad, light is slow" comes mainly from my SAN background as well. I work for a company who, like others, plan data center locations all around the magical "fiber distance" metric. When you're running SRDF, your distances have to be reasonably short. We use Cisco's SSM cards to make use of Fibre Channel Write Acceleration to mitigate some of the effect of distance, but in the end... running a protocol that was meant to run in the timeframe of a few meters of almost light speed is going to have problems dealing with kilometers of light speed. That means that even though we'd love to run SRDF over the Atlantic ocean, it's not really possible without the help of SRDF-A (asynchronous).
As far as reference in that regard? Not sure. Really my comments just come from experience.
And there is a POLICY here where you absolutely, positively, HAVE TO have MS Office and USE IT here at Woodbury University.
This would seem like an alternate universe to me, coming from Rutgers where, like many other universities, not using Word is the norm and people look at you funny when you don't use TeX or some variation thereof. I can't imagine having to use Word for any real work. It's a pain to just write a simple letter.
We solved the problem by hiring an entirely immigrant (spansih speaking) kitchen. Productivity went through the roof, quality went up, cleanliness was impeccable and they came to work every day - usually early.
Doesn't surprise me at all. A lot of places I visit have a fair amount of hispanic workers. They seem to have twice the drive and work output of the equivalent native. Sad, really. That, and they actually say "you're welcome" when I say "thank you." That's more than you can say for a lot of Americans in low paying jobs.
99% of the people appear to think it was unnecessary. That's because it was unnecessary.
That's by 99% of the people here don't understand that even if he left by the time the police got there, he refused to leave immediately when asked by the CSOs. This makes him a trespasser and subject to arrest. OF COURSE the police aren't going to let him leave when they need to arrest him.
This is the best summation of events thus far. This situation is so blown out of proportion. He's very lucky he didn't get hit with a baton--which I think would have been completely warranted.
Sure, if the person didn't decide to fight with the police. A hostage situation can end "non-violently" too, but it doesn't mean that the hostage-taker wouldn't have been justly shot if the police were given the chance.
And probably a dozen more. He was trespassing and fighting the police. If the guy had somehow managed to break a cop's nose while he was resisting, which is far more harmful than a little tasing, no one would be giving any sympathy to the cop.
The insurance industy, a more vile den of scum and villainy....
How is the insurance industry vile? They are doing what many financial companies do, selling a derivative an underlying asset. In this case, an option on healthcare. They sell you a contract that they will give you healthcare at a fixed cost (your deductible) if some condition is satisfied (you get hurt). If we didn't have insurance, healthcare would be completely unaffordable when you need it most.
This is because none of the major labels would be on board.
This is a horrible argument. If there's nothing to buy, of course no one's going to buy anything.
The way I feel is that something has to give. It's silly to pay almost the same price for a lossy copy of something as the actual "something" itself. If songs were $0.25 a pop, I'd probably buy a lot. But, when an album is $9.99 and a lot of albums out there can be purchased for $12.99 at a store... why am I going to save $3 and get an inferior product?
Why in the world would you want a router + 48 port switch all in one? so when you take the router offline the whole network crashes?
Not to be rude, but this is how it's done in the real world. The fact that a switch "routes" is merely part of its feature set. Routing is switching. It's just that canonically, it's typically associated with layer 3 switching. Some switches even switch above layer 3.
Also, these devices don't go down. It's not really acceptable. As such they are configured with multiple, redundant supervisor engines. If one dies, the other takes over. You can upgrade them separately so that the other is running during the upgrade. See here. See the box all the way to the right? The two middle most cards are the redundant supervisors. You can see similar configurations in the rest.
And people think it's gonna be a case of "Hey. iPhone. Apple built it. World's best cellphone." just like that??
Yes. It's really that simple. They might not consciously say that, but I believe that will be the effective result. I've mentioned this before, but cell phones are horrible. I think mine would be more useful if it randomly rearranged the interface everytime I used it--that way at least every so often I'd get some sort of intuitive interaction with the stupid thing.
In taking graph theory, I expected the use of calculus to be quite low, and in the end it was, but every now and then you have to pull out calculus to prove results. For example, the crux of the argument for proving that if a simple graph G_n on n vertices has more than (n - 1) choose 2 edges, G_n is connected, comes down to a simple maximization problem. You basically end up proving that the "worst case scenario" is when (n - 1) of those n vertices form a complete graph and another edge *has* to make the whole graph connected.
It was sort of funny watching the professor coax along all of the 400 level math class into saying "Take the derivative, set it equal to zero."
Bottom line: I agree with the parent; calculus is still useful despite computer science being on more of the discrete side of things.
If you've read any of The Art of Computer Programming, or Concrete Mathematics, in fact, you'll realize that Knuth's publisher probably wishes they could charge by the integral symbol, as there are a heck of a lot of them.
I've never seen a broader generalizaton. Your anecdotal evidence about working for a.NET company is in no way indicative of a lot of places. Business people making technical decisions is a problem that exists because of poor management and organizational techniques, not because someone uses.NET. And it's just as likely that working as a Perl programmer might mean writing long monolithic scripts (read: boring) as it is to be doing boring work in.NET. Choose a company and group of people--not an architecture.
Apple has created an artificial need to stay with iPod if you use ITMS. Anyone who has purchased music through ITMS loses their ability to play their music on-the-go once they drop iPod (yeah, you can burn and rerip, losing a bit of quality and taking a/lot/ of time--realistically, most people will not do this).
Number of iPods I own: 3 Number of iTunes songs I have bought: 0 Probability of me switching to another player: limit of 1/n as n -> infinity.
I wouldn't say I'm the norm, but I would say that there are a fair amount of people with iPods that don't use the iTunes store.
OSX is denying the user one of the fundamental Freedoms.
Uh, it might be a "fundamental Freedom" if you had a "fundamental Right" of some sort to do as you wish with other people's IP. Unfortunately, you don't. A significant number of people make a good living for themselves and their families working for companies that, while being very understanding and supportive of the free software movement in its proper place, gain competitive advantage over their peers by employing the best intellectual talent to solve problems with technological solutions that if copied would eliminate any sort of advantage that company may have in solving a certain problem.
You've never 'resided' on a traditional UNIX desktop. That would be MWM, or CDE. You mentioned 'Debian' which didn't even exist in the 'traditional UNIX' era.
How the *heck* could you know what I've ever used? And yes, I *have* used CDE. And I have used MWM and associated LessTif niceties. Please, spare me the pedantry in analyzing my word choice. I think it was clear from context that I was referring to the thought of using non-OS X GUIs that happen to run on top of UNIX-like underpinnings.
Slashdot Mirror
The comment implicit in your response is right. What I mean is that I agree with the idea that it all depends on what you're doing. For instance, my thought that "distance is bad, light is slow" comes mainly from my SAN background as well. I work for a company who, like others, plan data center locations all around the magical "fiber distance" metric. When you're running SRDF, your distances have to be reasonably short. We use Cisco's SSM cards to make use of Fibre Channel Write Acceleration to mitigate some of the effect of distance, but in the end... running a protocol that was meant to run in the timeframe of a few meters of almost light speed is going to have problems dealing with kilometers of light speed. That means that even though we'd love to run SRDF over the Atlantic ocean, it's not really possible without the help of SRDF-A (asynchronous).
As far as reference in that regard? Not sure. Really my comments just come from experience.
Hops add far more latency than distance
Not really. Switching is fast. Light is slow.
Distance is the #1 factor.
And there is a POLICY here where you absolutely, positively, HAVE TO have MS Office and USE IT here at Woodbury University.
This would seem like an alternate universe to me, coming from Rutgers where, like many other universities, not using Word is the norm and people look at you funny when you don't use TeX or some variation thereof. I can't imagine having to use Word for any real work. It's a pain to just write a simple letter.
Not as good as the Windows WDM Driver Model.
Everyone should know that WDM stands for Wavelength Division Multiplexing. Anything else is just silly.
If it's Reno they might have a chance for a fast recovery. Tahoe? Forget it.
*Sigh*
Long day makes for bad jokes.
And the post to the opensuse dev list was just uncalled for
Don't have an open mailing list for OpenSUSE if you don't want to deal with sometimes unwanted comments.
We solved the problem by hiring an entirely immigrant (spansih speaking) kitchen. Productivity went through the roof, quality went up, cleanliness was impeccable and they came to work every day - usually early.
Doesn't surprise me at all. A lot of places I visit have a fair amount of hispanic workers. They seem to have twice the drive and work output of the equivalent native. Sad, really. That, and they actually say "you're welcome" when I say "thank you." That's more than you can say for a lot of Americans in low paying jobs.
99% of the people appear to think it was unnecessary. That's because it was unnecessary.
That's by 99% of the people here don't understand that even if he left by the time the police got there, he refused to leave immediately when asked by the CSOs. This makes him a trespasser and subject to arrest. OF COURSE the police aren't going to let him leave when they need to arrest him.
Let them give every other penny they make for the rest of their lives to this kid.
He should pay them for ruining their evening.
This is the best summation of events thus far. This situation is so blown out of proportion. He's very lucky he didn't get hit with a baton--which I think would have been completely warranted.
It could've been done non-violently
Sure, if the person didn't decide to fight with the police. A hostage situation can end "non-violently" too, but it doesn't mean that the hostage-taker wouldn't have been justly shot if the police were given the chance.
Did he deserve that first tazzing?
Yes
Did he deserve the next 4?
Yes.
And probably a dozen more. He was trespassing and fighting the police. If the guy had somehow managed to break a cop's nose while he was resisting, which is far more harmful than a little tasing, no one would be giving any sympathy to the cop.
He was asked to leave. Once you're asked to leave and you don't, you're a trespasser. Why is this difficult to understand?
NO THANK YOU.
The insurance industy, a more vile den of scum and villainy ....
How is the insurance industry vile? They are doing what many financial companies do, selling a derivative an underlying asset. In this case, an option on healthcare. They sell you a contract that they will give you healthcare at a fixed cost (your deductible) if some condition is satisfied (you get hurt). If we didn't have insurance, healthcare would be completely unaffordable when you need it most.
I can sell my used CD on E-Bay for $5 if I don't like it. Try that with your used I-Tunes songs.
This is my point... iTunes is overpriced. As are their movies. Im sure Apple would love to go lower, but the studios just don't seem to understand.
This is because none of the major labels would be on board.
This is a horrible argument. If there's nothing to buy, of course no one's going to buy anything.
The way I feel is that something has to give. It's silly to pay almost the same price for a lossy copy of something as the actual "something" itself. If songs were $0.25 a pop, I'd probably buy a lot. But, when an album is $9.99 and a lot of albums out there can be purchased for $12.99 at a store... why am I going to save $3 and get an inferior product?
I'm *really* confused.
That is, VLAN 100 on port 1 should be switched to VLAN 105 on port 2
What does this mean? You want traffic switched between the two ports? What's connected on the other end, hosts? switches?
Like I said... I'm confused.
Why in the world would you want a router + 48 port switch all in one? so when you take the router offline the whole network crashes?
Not to be rude, but this is how it's done in the real world. The fact that a switch "routes" is merely part of its feature set. Routing is switching. It's just that canonically, it's typically associated with layer 3 switching. Some switches even switch above layer 3.
Also, these devices don't go down. It's not really acceptable. As such they are configured with multiple, redundant supervisor engines. If one dies, the other takes over. You can upgrade them separately so that the other is running during the upgrade. See here. See the box all the way to the right? The two middle most cards are the redundant supervisors. You can see similar configurations in the rest.
And people think it's gonna be a case of "Hey. iPhone. Apple built it. World's best cellphone." just like that??
Yes. It's really that simple. They might not consciously say that, but I believe that will be the effective result. I've mentioned this before, but cell phones are horrible. I think mine would be more useful if it randomly rearranged the interface everytime I used it--that way at least every so often I'd get some sort of intuitive interaction with the stupid thing.
In taking graph theory, I expected the use of calculus to be quite low, and in the end it was, but every now and then you have to pull out calculus to prove results. For example, the crux of the argument for proving that if a simple graph G_n on n vertices has more than (n - 1) choose 2 edges, G_n is connected, comes down to a simple maximization problem. You basically end up proving that the "worst case scenario" is when (n - 1) of those n vertices form a complete graph and another edge *has* to make the whole graph connected.
It was sort of funny watching the professor coax along all of the 400 level math class into saying "Take the derivative, set it equal to zero."
Bottom line: I agree with the parent; calculus is still useful despite computer science being on more of the discrete side of things.
If you've read any of The Art of Computer Programming, or Concrete Mathematics, in fact, you'll realize that Knuth's publisher probably wishes they could charge by the integral symbol, as there are a heck of a lot of them.
I've never seen a broader generalizaton. Your anecdotal evidence about working for a .NET company is in no way indicative of a lot of places. Business people making technical decisions is a problem that exists because of poor management and organizational techniques, not because someone uses .NET. And it's just as likely that working as a Perl programmer might mean writing long monolithic scripts (read: boring) as it is to be doing boring work in .NET. Choose a company and group of people--not an architecture.
Apple has created an artificial need to stay with iPod if you use ITMS. Anyone who has purchased music through ITMS loses their ability to play their music on-the-go once they drop iPod (yeah, you can burn and rerip, losing a bit of quality and taking a /lot/ of time--realistically, most people will not do this).
Number of iPods I own: 3
Number of iTunes songs I have bought: 0
Probability of me switching to another player: limit of 1/n as n -> infinity.
I wouldn't say I'm the norm, but I would say that there are a fair amount of people with iPods that don't use the iTunes store.
OSX is denying the user one of the fundamental Freedoms.
Uh, it might be a "fundamental Freedom" if you had a "fundamental Right" of some sort to do as you wish with other people's IP. Unfortunately, you don't. A significant number of people make a good living for themselves and their families working for companies that, while being very understanding and supportive of the free software movement in its proper place, gain competitive advantage over their peers by employing the best intellectual talent to solve problems with technological solutions that if copied would eliminate any sort of advantage that company may have in solving a certain problem.
You've never 'resided' on a traditional UNIX desktop. That would be MWM, or CDE. You mentioned 'Debian' which didn't even exist in the 'traditional UNIX' era.
How the *heck* could you know what I've ever used? And yes, I *have* used CDE. And I have used MWM and associated LessTif niceties. Please, spare me the pedantry in analyzing my word choice. I think it was clear from context that I was referring to the thought of using non-OS X GUIs that happen to run on top of UNIX-like underpinnings.