When you are given a screw driver to drive a nail, blaming the tool makes sense!
If I was given a screwdriver to drive a nail, I'd be more apt to blame the tool that handed me the screwdriver, or perhaps the one that neglected to ensure a hammer was available for the task.
It looks to me like you'd need more gas-manipulation punch to pull off the Scorcher; at minimum (3rd) caster level, it's a roughly 5 foot wide by 30 foot long damage zone but producing only a brief flash of singeing flame.. As it is, it looks more to me like a first-level Zann Esu style Inferno, with maybe 10 foot range but higher and more sustained damage delivery.
So how is this much different from the situation of Microsoft's red-headed stepchild, the Compact Framework? No ASP.Net, no WPF, no binary serialization, no CodeDom or System.Reflection.Emit, no useful marshaling, worthless AppDomain support, a wimpy client-only WCF, even WinForms is half-assed. (I can only assume that because of space considerations, only half of an ass would fit!)
Confusing "apocalypse" -- literally, revelation -- with the end of humanity is a common mistake, possibly because of the sheer volume of literature discussing revelation in that context. I don't exactly find the fact that mass numbers of twits want to tell the world their about their day-to-day lives to be a worldview-shattering revelation, however.
Think of it as follows. You are driving on the highway and somebody on the highway drives the speed limit exactly, stays in the center lane, and does not switch lanes at all. Even though that would seem to be right, it is actually quite wrong and it would make police suspicious.
Wonderful. Now using cruise control is suspicious?
I figure there's got to be protection against data loss built-in, but I'm not able to find details regarding any individual drive or manufacturer's approach to solving that problem. Does anyone know more about this subject?
Write-ahead would be one simple technique. Keep at least a spare block around, and don't blow away the old block until you've copied what you need to keep.
+1. Problem is, current CPUs themselves are buggy and exploitable, so you still need a verifier, and if you need that you may as well have a VM and a JIT. Unfortunately the major VMs that have the building blocks to be capability-secure -- such as CLR and JVM -- threw it all away with their standard library designs.
There's also a hidden side of capability security: preventing data, or more generally causality, from leaking in or out of a given piece of code. If there's an API exposed to untrusted code that allows it to detect its environment -- even so simple as the default object hash code or a way to get the current time -- you have a covert channel waiting to bite you.
The crux of the difference between geek-think and law-think here is that typically the legal issues turn not on the assets themselves, but on their provenance -- which is not an intrinsic property of the assets, but rather a sort of implicit metadata that requires extra bookkeeping to track reliably.
The legality of a song-file depends on how you got it, not the fact that it's a song by a major label artist. Downloaded from a properly licensed online store? No problem. The same exact sequence of bits, downloaded from someplace shady? Problem.
Similarly, the legality of a stack of $100 notes likewise depends on how you got it. If you got it by, say, making and selling custom cabinetry, you're probably fine, but if you got it by unauthorized sale of controlled substances, and the law catches on, you'll have problems.
Compressors turn off while you're accelerating hard, so you don't notice.
It's a really annoying feature in America's southwestern deserts: in the summer, jump on the accelerator and you catch a blast of heat in the face for your trouble. Maybe they should disable the ventilation fan at the same time to mitigate the annoyance?
My old Zenith space command control does not work with apple's frontrow.
And I'm annoyed it doesn't work with the vinyl and CDs I already bought.
It doesn't fit in the protective case I bought for my iphone.
it does not fit in my itouch dock.
my old memory sticks don't fit in my new imac.
Damn you apple, always making my older gear obsolete. I think I'll blame it on DRM and post it on slashdot.
Those wood-cabinet Zenith sets are pretty robust, but count yourself lucky if your Space Command remote still works at all! I have a soft spot for older gear myself, but those things fall over dead if you so much as look at them funny, let alone bump them on something.
Anyway, that set will probably need a DTV converter box soon, which might further degrade the usefulness of the remote.
It's CO2 that was pulled out of the atmosphere when the vegetables it came from were grown, so in that respect it's carbon-neutral. The CO2 emitted by farming equipment, fertilizer production, and so forth would have happened anyway.
The abusive parts certainly do, but there are a few gems of common sense in it, such as 17 USC 117.
Per the USDoJ's gloss in the manual on prosecuting IP crime, chapter 2, pages 68-69,
"... this allows the lawful owner of a piece of software to install it on his machine, even if doing so requires copying the program from a CD-ROM to the hard drive or loading it from the hard drive into RAM, both of which are considered reproduction under copyright law.", and cite some case law supporting this view.
Look closely enough, take things out of context and maybe squint a little, and you'll find scriptural evidence for any old idea. There's even a wiki page of scriptural evidence for eXtreme Programming.
Have you considered reformatting to FAT32 instead of NTFS? (Yes, I know Windows will try to prevent you from formatting a sufficiently large volume as FAT32, but there are other ways.)
Because the license costs a high volume OEM about $60 and they bundle -$70 worth of free trial crapware that only runs under Windows, so the Windows license comes at no cost to you and the OEM makes an extra $10 in the bargain. That's why a Linux box and a Windows box price out the same in practice.
I'm probably either preaching to the choir or feeding a troll, but I'll join in anyway.:-)
Quite true. The "cars and trucks" or "animal" kind of tutorial OOP metaphor, understandable as it seems, actually seems to be one of the worst abuses of OOP; people take the advice literally, and write all these hardcoded class hierarchies of their business objects.
Without realising that in the real world, a "customer" might morph into a "user" just by signing a document, but if they've been created as CustomerPerson and UserPerson entities by someone diligently following Object-Oriented Design methodology, there's no way the system can make that happen, because objects can't change their class at runtime.
Cats don't become dogs. Prospects do occasionally become customers. If you try to model that with inheritance on Person you're doing it wrong. Add a role or state or something to the Person instead. Better yet, add a collection of purchase transactions with timestamps, entitlements with validity intervals, or whatever else you need. (I say this because even experienced data modelers tend to make a mess when dealing with temporal data, regardless of the data representation paradigm.)
"However, in practice, you use object orientation to avoid zillions of "if" statements, special case code, large blocks of almost-but-not-quite duplicated code."
Method dispatch is the defining control structure of object-oriented code. It's supposed to replace conditionals.
And then in actual actual practice, what we often end up doing in OOP is the reverse: duplicating, for example, a SQL database schema in a ton of cut-and-pasted boilerplate 'business object' class definitions.
If you're treating the boilerplate as source code, you're doing it wrong. Use compile-time or run-time code generation and don't hand-edit the code generator output. It also doesn't help our sanity that using a database usually means connecting two languages with radically different type systems via remote calls; generated stubs are often used as a sort of transcription of the foreign types.
And then we compound the pain with that final abomination of OOP 'best practice', getter and setter methods. Whose whole reason for existence is to be a cause of almost-but-not-quite-duplicated code!
Properties are a weakness in an object-oriented design, not a best practice. Move that logic into the object that has the fields you need. With apologies to the U.S. military: "Tell, don't ask." Also, much of the ink spilled on 'best practice' is a waste, since much of it is motivated by a desire to replace thinking and comprehension with adherence to policy -- or to sell snake oil.
Oy. We do it to ourselves, and that's what really hurts.
And consultants still get to sell Object Oriented Analysis and Design as if it's *not* snake oil.
The unfortunate part of consulting is that it's mostly salesmanship, and if you don't have a real solution you still have to eat, so it's unsurprising that many consultants sell snake oil to make up the shortfall.
XP Embedded also offers a fast boot feature called HORM - Hibernate Once, Resume Many. With this enabled, an ordinary cold boot reloads the saved hibernation snapshot without removing it. The downside: any filesystems mounted when the snapshot was taken are expected to be block for block unchanged from the time of the snapshot, which can require some backflips to deal with.
This is exactly why the ACLU gets so much hate: they have to go to bat for civil liberties to try to prevent bad precedent, even though public opinion on the case is more like "Due process? Just lynch them!"
That this happens so often leads me to believe that a number of prosecutors pick these opportunities specifically to force judges to choose between civil liberties and looking like they support the Prime Evils.
Slashdot Mirror
When you are given a screw driver to drive a nail, blaming the tool makes sense!
If I was given a screwdriver to drive a nail, I'd be more apt to blame the tool that handed me the screwdriver, or perhaps the one that neglected to ensure a hammer was available for the task.
It looks to me like you'd need more gas-manipulation punch to pull off the Scorcher; at minimum (3rd) caster level, it's a roughly 5 foot wide by 30 foot long damage zone but producing only a brief flash of singeing flame.. As it is, it looks more to me like a first-level Zann Esu style Inferno, with maybe 10 foot range but higher and more sustained damage delivery.
So how is this much different from the situation of Microsoft's red-headed stepchild, the Compact Framework? No ASP.Net, no WPF, no binary serialization, no CodeDom or System.Reflection.Emit, no useful marshaling, worthless AppDomain support, a wimpy client-only WCF, even WinForms is half-assed. (I can only assume that because of space considerations, only half of an ass would fit!)
In any case, the real revelation for a lot of shortsighted developers is that you shouldn't use 32-bit sequence numbers for something so voluminous as tweets!
Think of it as follows. You are driving on the highway and somebody on the highway drives the speed limit exactly, stays in the center lane, and does not switch lanes at all. Even though that would seem to be right, it is actually quite wrong and it would make police suspicious.
Wonderful. Now using cruise control is suspicious?
I figure there's got to be protection against data loss built-in, but I'm not able to find details regarding any individual drive or manufacturer's approach to solving that problem. Does anyone know more about this subject?
Write-ahead would be one simple technique. Keep at least a spare block around, and don't blow away the old block until you've copied what you need to keep.
+1. Problem is, current CPUs themselves are buggy and exploitable, so you still need a verifier, and if you need that you may as well have a VM and a JIT. Unfortunately the major VMs that have the building blocks to be capability-secure -- such as CLR and JVM -- threw it all away with their standard library designs.
There's also a hidden side of capability security: preventing data, or more generally causality, from leaking in or out of a given piece of code. If there's an API exposed to untrusted code that allows it to detect its environment -- even so simple as the default object hash code or a way to get the current time -- you have a covert channel waiting to bite you.
Hey editors! Pull the other one, it's got bells on.
The crux of the difference between geek-think and law-think here is that typically the legal issues turn not on the assets themselves, but on their provenance -- which is not an intrinsic property of the assets, but rather a sort of implicit metadata that requires extra bookkeeping to track reliably.
The legality of a song-file depends on how you got it, not the fact that it's a song by a major label artist. Downloaded from a properly licensed online store? No problem. The same exact sequence of bits, downloaded from someplace shady? Problem.
Similarly, the legality of a stack of $100 notes likewise depends on how you got it. If you got it by, say, making and selling custom cabinetry, you're probably fine, but if you got it by unauthorized sale of controlled substances, and the law catches on, you'll have problems.
Compressors turn off while you're accelerating hard, so you don't notice.
It's a really annoying feature in America's southwestern deserts: in the summer, jump on the accelerator and you catch a blast of heat in the face for your trouble. Maybe they should disable the ventilation fan at the same time to mitigate the annoyance?
My old Zenith space command control does not work with apple's frontrow.
And I'm annoyed it doesn't work with the vinyl and CDs I already bought.
It doesn't fit in the protective case I bought for my iphone.
it does not fit in my itouch dock.
my old memory sticks don't fit in my new imac.
Damn you apple, always making my older gear obsolete. I think I'll blame it on DRM and post it on slashdot.
Those wood-cabinet Zenith sets are pretty robust, but count yourself lucky if your Space Command remote still works at all! I have a soft spot for older gear myself, but those things fall over dead if you so much as look at them funny, let alone bump them on something.
Anyway, that set will probably need a DTV converter box soon, which might further degrade the usefulness of the remote.
It's CO2 that was pulled out of the atmosphere when the vegetables it came from were grown, so in that respect it's carbon-neutral. The CO2 emitted by farming equipment, fertilizer production, and so forth would have happened anyway.
Yes, it is. But the DMCA still needs to go away.
The abusive parts certainly do, but there are a few gems of common sense in it, such as 17 USC 117. Per the USDoJ's gloss in the manual on prosecuting IP crime, chapter 2, pages 68-69, "... this allows the lawful owner of a piece of software to install it on his machine, even if doing so requires copying the program from a CD-ROM to the hard drive or loading it from the hard drive into RAM, both of which are considered reproduction under copyright law.", and cite some case law supporting this view.
The DMCA needs to go away.
Ummm... the DMCA is a US law. TFA is about a Canadian ISP.
Look closely enough, take things out of context and maybe squint a little, and you'll find scriptural evidence for any old idea. There's even a wiki page of scriptural evidence for eXtreme Programming.
I don't treat men and women differently when it comes to work, except maybe when it comes to the small talk.
I thought programming was supposed to be a matter of Smalltalk, so that's not saying much.
Have you considered reformatting to FAT32 instead of NTFS? (Yes, I know Windows will try to prevent you from formatting a sufficiently large volume as FAT32, but there are other ways.)
Belgian beer (Budweiser) and South African beer (Coors and Miller) suck.
I wouldn't say all Belgian beer sucks, though. I'm kind of partial to Lindemans lambics.
If you actually compare like to like, Dell is charging $608 for the following Linux machine vs. $669 if you buy with Vista installed.
Touché. It's been some time since I last compared.
Because the license costs a high volume OEM about $60 and they bundle -$70 worth of free trial crapware that only runs under Windows, so the Windows license comes at no cost to you and the OEM makes an extra $10 in the bargain. That's why a Linux box and a Windows box price out the same in practice.
I'm probably either preaching to the choir or feeding a troll, but I'll join in anyway. :-)
Quite true. The "cars and trucks" or "animal" kind of tutorial OOP metaphor, understandable as it seems, actually seems to be one of the worst abuses of OOP; people take the advice literally, and write all these hardcoded class hierarchies of their business objects.
Without realising that in the real world, a "customer" might morph into a "user" just by signing a document, but if they've been created as CustomerPerson and UserPerson entities by someone diligently following Object-Oriented Design methodology, there's no way the system can make that happen, because objects can't change their class at runtime.
Cats don't become dogs. Prospects do occasionally become customers. If you try to model that with inheritance on Person you're doing it wrong. Add a role or state or something to the Person instead. Better yet, add a collection of purchase transactions with timestamps, entitlements with validity intervals, or whatever else you need. (I say this because even experienced data modelers tend to make a mess when dealing with temporal data, regardless of the data representation paradigm.)
"However, in practice, you use object orientation to avoid zillions of "if" statements, special case code, large blocks of almost-but-not-quite duplicated code."
Method dispatch is the defining control structure of object-oriented code. It's supposed to replace conditionals.
And then in actual actual practice, what we often end up doing in OOP is the reverse: duplicating, for example, a SQL database schema in a ton of cut-and-pasted boilerplate 'business object' class definitions.
If you're treating the boilerplate as source code, you're doing it wrong. Use compile-time or run-time code generation and don't hand-edit the code generator output. It also doesn't help our sanity that using a database usually means connecting two languages with radically different type systems via remote calls; generated stubs are often used as a sort of transcription of the foreign types.
And then we compound the pain with that final abomination of OOP 'best practice', getter and setter methods. Whose whole reason for existence is to be a cause of almost-but-not-quite-duplicated code!
Properties are a weakness in an object-oriented design, not a best practice. Move that logic into the object that has the fields you need. With apologies to the U.S. military: "Tell, don't ask." Also, much of the ink spilled on 'best practice' is a waste, since much of it is motivated by a desire to replace thinking and comprehension with adherence to policy -- or to sell snake oil.
Oy. We do it to ourselves, and that's what really hurts.
And consultants still get to sell Object Oriented Analysis and Design as if it's *not* snake oil.
The unfortunate part of consulting is that it's mostly salesmanship, and if you don't have a real solution you still have to eat, so it's unsurprising that many consultants sell snake oil to make up the shortfall.
XP Embedded also offers a fast boot feature called HORM - Hibernate Once, Resume Many. With this enabled, an ordinary cold boot reloads the saved hibernation snapshot without removing it. The downside: any filesystems mounted when the snapshot was taken are expected to be block for block unchanged from the time of the snapshot, which can require some backflips to deal with.
With more modern designs, 400 acres of desert can get you 64 megawatts. Solar's come a long way.
This is exactly why the ACLU gets so much hate: they have to go to bat for civil liberties to try to prevent bad precedent, even though public opinion on the case is more like "Due process? Just lynch them!"
That this happens so often leads me to believe that a number of prosecutors pick these opportunities specifically to force judges to choose between civil liberties and looking like they support the Prime Evils.
Have you looked at Solitaire aka Pontifex? Workable by hand with some plausible deniability to boot.