Both Intel and AMD have a wide range of price points. At least in the low to mid-range. Intel has a swath of parts that cost a lot more than any AMD parts, but they also perform a lot better than anything else in existence.
Not really. The magnetosphere protects us from most of it. It makes some radio noise, brighter aurorae at the poles, and a lot of hoo-ha on the tee-vee.
We'll find out in 3.5 years when an article in Wired describing the failure of the power grid due to transformer saturation later this week asks why nothing was done to prevent such saturation after the last N such events.
1. Allowing too many options / features in the design
Easy to manage if you can organize them under a few classes and they don't couple too hard; if you let them all have a different top-level class you're fucked.
2. Assuming 5 working-days of effort can be achieved in a working week.
_The Mythical Man-Month_ covered this (mumble) decades ago.
3. The tacit assumption that testing will inevitably be followed by release - rather than bug-fixing.
Seriously? That's a firing offense.
4. The rest.
Most of that is just generic bad project management. It's not at all limited to software practice. It's a feature of allowing inexperienced or untrained PM's to do your scheduling, which is a very frequent choice of middle management, which becomes a hindrance when things start to go off the rails. This is the sort of thing that makes Agile processes relatively successful; when you plan for chaos and get it, it doesn't look so much like failure.
The use of goto is not justified by ignorance of the underlying action of while, do, for, switch, break, continue, return, throw, f(), or longjmp, but is justified by knowing their underlying action and finding it inadequate or obfuscatory.
(I get the nagging feeling I missed one...and not in asm...)
No, there are several contradictions, and several of the "mistakes" are complicated policy issues that coders don't get to decide until they're in lead positions. It's not a very good article.
If you document what you know and give that to the user then it's their fault for doing stupid stuff and you can charge them more to change it provided they didn't spell it out when they told you what they wanted it to do before you wrote it.
Don't be an idiot. You have the right to travel. On what's called the Right of Way.
All airspace used for air travel is federally controlled. That way, you don't have to negotiate with every property owner when you fly over. Because there's no right of way in airspace.
And when you drive, you do so at the pleasure of the people who issued your license, which gives you a license to drive a motor vehicle on the right of way. You could walk, but you chose to bring along 1000 kg of metal and move it at 100+ km/h, all the while distracting yourself to post to/. on your iPhone. In other words, you don't have a right to drive, any more than you have a right to fly.
You have a right to travel, on any pair of legs you care to sport.
This, on the other hand, you do not have: "I have every right under the sun unless something is explicitly forbidden by law." That isn't what the Constitution says. What it says is that there exist some rights that the Constitution doesn't speak of. Not that every action that humans are capable of that the Constitution doesn't speak of is a right. You don't make your own rights, and when it comes time to remind you of that you will find that you've probably gone way past them, if you don't understand this beforehand.
If it were possible to use the internet to kill someone, there would be controls on the use of the internet that would apply to everyone. Not just you, and not just because you called Mitch McConnell a shit-eating nazi babyfucker.
I'd bet most of these guys are current or former military EOD, and they have all the same tools.
Since the place is likely coated in explosive residue, the only choice is to burn it down. It would be nice to remove any big pieces of explosive first, but they explained why that's a stupid idea in this case.
Which makes me think that there's a lot of weird stuff, but not a lot of explosives, in a world where something like the Murrah Federal Building bomb is a lot of explosives.
I also expect that the perp has told them what's in the house by now, so the unknown nature of this is somewhat overstated.
Regardless, homemade explosives are not "safe" like commercial explosives are, and just stepping on goop in the backyard got one guy almost killed, so wandering around pulling things apart like it's an episode of Hoarders is not a good idea.
That's what the Russians are doing (I posted a link up yonder; if you don't find it, google for "russian space junk nuclear $2 billion" and you'll see recent stories).
They'll put up a drone with a nuclear-powered ion drive that will move things from their current orbit to one that's less threatening. Most likely that means making the transition from a given GEO slot to one of the natural junk-magnet orbits more expeditious and certain than it is now.
Actually deorbiting something to burn up in the atmosphere would be tricky, since it would involve putting the drone and the satellite in nearly that position, then getting the drone into a more stable orbit. Just one more thing to go wrong in a touchy business.
1. George was way more popular than anyone else involved with MSL or HSF.
2. MSL is a lot more than a few notes similar to HSF.
3. The company (Bright Music) that published HSF was owned by the Tokens. Hardly the sort of megaslime that is being invoked in this thread. Allen Klein didn't get involved until after the suit started, and he started out on Harrison's side before he tried to buy Bright Music to try to get a chunk of the judgment in a case that was certain to go against Harrison.
Trust me. This is not an example of what you want to prove.
Intel has parts similar to these at about these prices. The Intel part that costs $1000 more makes one of these things run like an abacus.
Both Intel and AMD have a wide range of price points. At least in the low to mid-range. Intel has a swath of parts that cost a lot more than any AMD parts, but they also perform a lot better than anything else in existence.
You should be able to see big ones from 50N.
This event won't produce one, though. It won't hit Earth.
Not really. The magnetosphere protects us from most of it. It makes some radio noise, brighter aurorae at the poles, and a lot of hoo-ha on the tee-vee.
We'll find out in 3.5 years when an article in Wired describing the failure of the power grid due to transformer saturation later this week asks why nothing was done to prevent such saturation after the last N such events.
Only if money changed hands. Lobbying is legal. Slimy in most cases, but legal.
1. Allowing too many options / features in the design
Easy to manage if you can organize them under a few classes and they don't couple too hard; if you let them all have a different top-level class you're fucked.
2. Assuming 5 working-days of effort can be achieved in a working week.
_The Mythical Man-Month_ covered this (mumble) decades ago.
3. The tacit assumption that testing will inevitably be followed by release - rather than bug-fixing.
Seriously? That's a firing offense.
4. The rest.
Most of that is just generic bad project management. It's not at all limited to software practice. It's a feature of allowing inexperienced or untrained PM's to do your scheduling, which is a very frequent choice of middle management, which becomes a hindrance when things start to go off the rails. This is the sort of thing that makes Agile processes relatively successful; when you plan for chaos and get it, it doesn't look so much like failure.
True.
The use of goto is not justified by ignorance of the underlying action of while, do, for, switch, break, continue, return, throw, f(), or longjmp, but is justified by knowing their underlying action and finding it inadequate or obfuscatory.
(I get the nagging feeling I missed one...and not in asm...)
No, there are several contradictions, and several of the "mistakes" are complicated policy issues that coders don't get to decide until they're in lead positions. It's not a very good article.
If you document what you know and give that to the user then it's their fault for doing stupid stuff and you can charge them more to change it provided they didn't spell it out when they told you what they wanted it to do before you wrote it.
If you don't, then you're asking for it.
I have any freedom not specifically prohibited by duly enacted law
Really?
There's no law against pissing down your neighbor's leg.
But I bet if you try it, you'll find your "freedom" limited by the swing of his fist. And the court will give the match to him.
Don't be an idiot. You have the right to travel. On what's called the Right of Way.
All airspace used for air travel is federally controlled. That way, you don't have to negotiate with every property owner when you fly over. Because there's no right of way in airspace.
And when you drive, you do so at the pleasure of the people who issued your license, which gives you a license to drive a motor vehicle on the right of way. You could walk, but you chose to bring along 1000 kg of metal and move it at 100+ km/h, all the while distracting yourself to post to /. on your iPhone. In other words, you don't have a right to drive, any more than you have a right to fly.
You have a right to travel, on any pair of legs you care to sport.
This, on the other hand, you do not have: "I have every right under the sun unless something is explicitly forbidden by law." That isn't what the Constitution says. What it says is that there exist some rights that the Constitution doesn't speak of. Not that every action that humans are capable of that the Constitution doesn't speak of is a right. You don't make your own rights, and when it comes time to remind you of that you will find that you've probably gone way past them, if you don't understand this beforehand.
If it were possible to use the internet to kill someone, there would be controls on the use of the internet that would apply to everyone. Not just you, and not just because you called Mitch McConnell a shit-eating nazi babyfucker.
Please post an album of pictures of your basement. Cc: the FBI, too.
No we haven't. You haven't and I haven't. It's those other guys, those are the ones who think they know better.
I'd bet most of these guys are current or former military EOD, and they have all the same tools.
Since the place is likely coated in explosive residue, the only choice is to burn it down. It would be nice to remove any big pieces of explosive first, but they explained why that's a stupid idea in this case.
The insurance company is unlikely to cover this sort of thing.
Which makes me think that there's a lot of weird stuff, but not a lot of explosives, in a world where something like the Murrah Federal Building bomb is a lot of explosives.
I also expect that the perp has told them what's in the house by now, so the unknown nature of this is somewhat overstated.
Regardless, homemade explosives are not "safe" like commercial explosives are, and just stepping on goop in the backyard got one guy almost killed, so wandering around pulling things apart like it's an episode of Hoarders is not a good idea.
Renting to someone doesn't absolve you of responsibility for your property.
That's what the Russians are doing (I posted a link up yonder; if you don't find it, google for "russian space junk nuclear $2 billion" and you'll see recent stories).
They'll put up a drone with a nuclear-powered ion drive that will move things from their current orbit to one that's less threatening. Most likely that means making the transition from a given GEO slot to one of the natural junk-magnet orbits more expeditious and certain than it is now.
Actually deorbiting something to burn up in the atmosphere would be tricky, since it would involve putting the drone and the satellite in nearly that position, then getting the drone into a more stable orbit. Just one more thing to go wrong in a touchy business.
The White House doesn't do pork.
Pork is Congressmen directing projects and spending to their home districts.
What you're describing is simply successful lobbying.
Not that it isn't a bad reason for something to happen, it's just not correct to call it pork.
Decentralized control makes it easier to hijack the whole thing.
Mine is at version inf.
So there.
And Stuxnet may or may not have been the product of some government.
All the more reason that camouflage requires that it be named Felchnet.
1. George was way more popular than anyone else involved with MSL or HSF.
2. MSL is a lot more than a few notes similar to HSF.
3. The company (Bright Music) that published HSF was owned by the Tokens. Hardly the sort of megaslime that is being invoked in this thread. Allen Klein didn't get involved until after the suit started, and he started out on Harrison's side before he tried to buy Bright Music to try to get a chunk of the judgment in a case that was certain to go against Harrison.
Trust me. This is not an example of what you want to prove.