If you'd bought a new processor at $100 every two years, it would've cost you $300 to have a near-cutting-edge processor for six years, instead of $280 for an ageing one at the end of that time-frame.
Not having to upgrade AMD motherboards to support new processors (in general) means such optimal cost options actually exist.
My advice to anyone buying computer components has always been the same: "Buy what you need now. If you don't need it now, wait as it'll be cheaper later."
So next time you see someone ignorantly hand waving that simply stomping the brakes fixes all, please understand they are completely fucking clueless about the world around them and its likely very safe to ignore anything they have to say on the subject - and likely many other subjects for that matter.
I usually ask such people if the friction takes into account the surface area of the tire.
If they say no, they can probably be reasoned with.
People forget about momentum. You're not just stopping a vehicle from accelerating, you're stopping its existing momentum as well. Not to mention the brakes overheating fairly rapidly on consumer vehicles under these situations.
On a similar note, this is why many malware authors used IRC for bot controlling. Connecting to a well-known IRC network and listening for commands pretty much prevents your 'server' from being taken down.
First, who cares? Second, in terms of top-n anythings, supercomputing has an awful lot of nobody-to-sue OS usage.
Wait, you honestly believe that most companies run only proprietary systems?
If you asked me (a database programmer and consultant), I'd point out that only the small fries actually believe Windows is in their best interest. Most of the medium to large sized companies have competent IT staff who want to make things work on a decent budget and would rather spend the money on hardware than OS licensing.
There are an awful lot of unintellectual crackpots on both sides of every debate who like to froth at the mouth without knowing a thing about what they're talking about. Very few of them are interested in actually learning, or being open-minded or realizing there are a lot of egos floating about in science on both sides of any camp.
The vast majority of scientists "agreeing" with climate change also aren't climate scientists but rather colleagues in one way or another.
To all the GW crowd, a lot of AGW people aren't yelling conspiracy, they're just sick of empty rhetoric when the facts appear to swing both ways if you pay attention.
Almost every normal human being I know (that's those with sub-genius IQs) calls them "Legos" (note the plural) and each individual brick a "Lego". The people I know in the "I can quote Starwars" camp call them "Lego bricks."
Obviously this is undesirable for the brand as this would lower the Trademark to simply being the name of a type of object.
Actually no. I see a proposal for exactly how engineering does work. The code monkeys are responsible to their supervisor or employer, but the software is certified by a software engineer who signs off on it. Right now, that last step isn't done.
Read the disclaimer that comes with any software, and imagine that same disclaimer attached to a bridge.
Your virtual size is not indicative of the size of the program in memory at all.
The resident size is fairly valid, and shows the size of the program currently in memory, but can be both code and data size.
A lot of that is also shared (note the shared field) as its the memory used by glibc or other libraries.
For example, launching four copies of the Java VM doesn't use 4x more RAM. Compile a quick program that just does a sleep for an hour and run a thousand of them. Check the resident size on any one, then add them together, then check your free memory. They won't add up, because a lot of that size is shared space.
The reality here is this: if you try to put engineers (especially software engineers) into a situation where every line of code they produce might put them in court, you're going to find yourself with a severe shortage of engineers. There are many things that creative minds can do, and if you make a particular line of work too personally dangerous nobody will enter that field.
That's exactly what real Professional Engineering is all about. Sign on the dotted line that the building is safe. Sign on the dotted line that the road will carry the load. Sign on the dotted line that the bridge will survive specific winds.
What we need is a few actual Professional Software Engineers taking responsibility for this crap just like out in the rest of the real world. Why do we treat software so much more laxly than building codes when bad software can cause hospital shutdowns or nuclear meltdowns?
I didn't insult my readers. I could've just as easily said "anyone who goes by what they hear on the radio" but then someone would've said "who listens to the radio anymore?" The term sheep is hardly an insult on the level of "moron", but simply a reference to not thinking for one's self about an issue (despite the possible capacity to do so).
I'm not going to list all the examples of bad science in the last fifty years. I seem to recall a researcher named Jones recently at least losing his data at Everest(?) if you'd like a recent one.
My point was simply that being skeptical hardly makes one the bad guy. "Almost everyone agrees" isn't a valid argument.
You didn't watch the second movie did you? He never saved the universe. He wanted to rescue the one person he cared about, that was all. When they took her from him and converted her, he killed their leader for it. There's no indication at the end of the movie that he doesn't make the Necros twice as evil as they were before he took over.
Slashdot Mirror
Like the build-your-own $200 netbooks at the store here? Or how about the build-your-own five year warranty like you can get with an Optiplex?
As a geek, I build my own. As a consultant, I push pre-built.
If you'd bought a new processor at $100 every two years, it would've cost you $300 to have a near-cutting-edge processor for six years, instead of $280 for an ageing one at the end of that time-frame.
Not having to upgrade AMD motherboards to support new processors (in general) means such optimal cost options actually exist.
My advice to anyone buying computer components has always been the same: "Buy what you need now. If you don't need it now, wait as it'll be cheaper later."
Or in the case of a murder: "She's dead now, why prosecute?"
Nice logic.
Your laziness is someone else's problem how exactly?
Wanna bet? I can tell my BIOS to shut off all the case fans and not sound the overheat alarm.
I usually ask such people if the friction takes into account the surface area of the tire.
If they say no, they can probably be reasoned with.
People forget about momentum. You're not just stopping a vehicle from accelerating, you're stopping its existing momentum as well. Not to mention the brakes overheating fairly rapidly on consumer vehicles under these situations.
That's called panic and its hardly a reason for my car to think on my behalf.
You don't know about fixed point math I take it?
You know Android doesn't run on Java, right?
Next question?
Assets get copied out no matter what you do. It happens all the time. Don't worry about it and make a game people want to buy.
And somehow selling health insurance is considered an honest profession. Go figure.
On a similar note, this is why many malware authors used IRC for bot controlling. Connecting to a well-known IRC network and listening for commands pretty much prevents your 'server' from being taken down.
Hypertransport itself, heavily used by AMD was an Alpha technology in the first place as well as I recall. Very neat stuff.
First, who cares? Second, in terms of top-n anythings, supercomputing has an awful lot of nobody-to-sue OS usage.
Wait, you honestly believe that most companies run only proprietary systems?
If you asked me (a database programmer and consultant), I'd point out that only the small fries actually believe Windows is in their best interest. Most of the medium to large sized companies have competent IT staff who want to make things work on a decent budget and would rather spend the money on hardware than OS licensing.
There are an awful lot of unintellectual crackpots on both sides of every debate who like to froth at the mouth without knowing a thing about what they're talking about. Very few of them are interested in actually learning, or being open-minded or realizing there are a lot of egos floating about in science on both sides of any camp.
The vast majority of scientists "agreeing" with climate change also aren't climate scientists but rather colleagues in one way or another.
To all the GW crowd, a lot of AGW people aren't yelling conspiracy, they're just sick of empty rhetoric when the facts appear to swing both ways if you pay attention.
Awesome, lol.
There's a huge difference between claiming that a brick SHOULD be called a Lego Brick and claiming that people DON'T call it a Lego.
People DO walk out from in between parked cars, people DO eat soup while driving, people DO talk on their cell phones in a movie theatre, etc.
What people ought to do is a totally different argument than the GP was making and the parent was correct to be annoyed by it.
If you honestly believe that, as I'm sure you do, that's great. But you're wrong.
Plenty of people refer to a singular Lego brick as a Lego just as they refer to a Ford vehicle as a Ford and I refer to each of my tires as a Pirelli.
Almost every normal human being I know (that's those with sub-genius IQs) calls them "Legos" (note the plural) and each individual brick a "Lego". The people I know in the "I can quote Starwars" camp call them "Lego bricks."
Obviously this is undesirable for the brand as this would lower the Trademark to simply being the name of a type of object.
Actually no. I see a proposal for exactly how engineering does work. The code monkeys are responsible to their supervisor or employer, but the software is certified by a software engineer who signs off on it. Right now, that last step isn't done.
Read the disclaimer that comes with any software, and imagine that same disclaimer attached to a bridge.
Your virtual size is not indicative of the size of the program in memory at all.
The resident size is fairly valid, and shows the size of the program currently in memory, but can be both code and data size.
A lot of that is also shared (note the shared field) as its the memory used by glibc or other libraries.
For example, launching four copies of the Java VM doesn't use 4x more RAM. Compile a quick program that just does a sleep for an hour and run a thousand of them. Check the resident size on any one, then add them together, then check your free memory. They won't add up, because a lot of that size is shared space.
That's exactly what real Professional Engineering is all about. Sign on the dotted line that the building is safe. Sign on the dotted line that the road will carry the load. Sign on the dotted line that the bridge will survive specific winds.
What we need is a few actual Professional Software Engineers taking responsibility for this crap just like out in the rest of the real world. Why do we treat software so much more laxly than building codes when bad software can cause hospital shutdowns or nuclear meltdowns?
I didn't insult my readers. I could've just as easily said "anyone who goes by what they hear on the radio" but then someone would've said "who listens to the radio anymore?" The term sheep is hardly an insult on the level of "moron", but simply a reference to not thinking for one's self about an issue (despite the possible capacity to do so).
I'm not going to list all the examples of bad science in the last fifty years. I seem to recall a researcher named Jones recently at least losing his data at Everest(?) if you'd like a recent one.
My point was simply that being skeptical hardly makes one the bad guy. "Almost everyone agrees" isn't a valid argument.
You didn't watch the second movie did you? He never saved the universe. He wanted to rescue the one person he cared about, that was all. When they took her from him and converted her, he killed their leader for it. There's no indication at the end of the movie that he doesn't make the Necros twice as evil as they were before he took over.