105 karma · joined March 18, 2009
One of the reasons/theories I've heard for this, is that if you've had Chickenpox, you are at-risk for Shingles -- which is often extremely painful and difficult to overcome. However, if you are regularly exposed to Chickenpox, your immune-system gets "reawakened" to the virus, therefore can more-quickly recognise and fight-off a recurrance, before it becomes Shingles.
One of the easiest ways to aid this exposure is to keep the virus active, but under-control, in the community. This has a useful side-effect of the community also being aware and more-knowledgeable about the disease, too.
Another argument I've heard against the vaccine is that it's simply not possible to get rid of Chickenpox totally -- it's _highly_ infectious, and the infectious stage is before symptoms appear, etc -- but the vaccine gives a false sense of security of protection, perhaps in the same way as everyone thinks they're safe from Smallpox, Hepatitis, Ebola, etc because we worked so hard to get rid of or control it.
TBH: If you want all your relational logic in your app, NoSQL systems make an awful lot more sense these days -- esp. if you've got a decent API/wrapper-layer that can automatically manage the freshness of locally cached data for you.
Almost as if they think because an awful lot of people have accepted it on iTunes, a similar number accepted it from Microsoft for such a long time (and still do) that it's simply a matter of waiting until the public are too jaded to care any longer.
The usual effect of such misdirected management behaviour is most of the good/talented/valuable people leave earlier than later, as they smell blood in the water.
Now, even though the core language hasn't changed, there seem to be all sorts of clever Perl modules appearing which take advantage of a lot of Perl's highly flexible nature.
I really like Ruby myself, and really hate Python (even though I have to use it at work) but when the other languages fail me, I can almost always turn to Perl in a pinch and get it to do what I want. I also have to admit that the potential power of Perl6's syntax is a little astonishing; I think I would pick Perl6 over Ruby, for example.
It seems to me non-"internet" piracy cases are largely based on hard evidence, and when they try to include evidence for "potential to do" it's also based on some other hard-evidence, e.g. a large-scale CD-copying machine, a pallet of 100,000 blanks.
If you'd been convicted before for the same offence, then you're more likely to get more jail-time for repeat offending, i.e. a predilection for continuing that proven behaviour, but the punishment meted-out for copyright offences seems massively, unbelievably out-of-scale. Probably because they're often compensation paid to the copyright owner, rather than punishment for breaking the law.
I also view the ability to sell the copyrights themselves (patents, etc, etc) to a third-party as very distasteful -- as opposed to allowing someone to use your copyrighted item(s) for compensation -- as it seems very against the spirit of the law to give up your original right as the author.
Once someone has made it possible for the idea to be shared -- even if they wrote it down and locked it in their safe -- then the information is already potentially accessible!
Breaking-in to someone's home to steal the paper you wrote your idea on is explicitly the theft, and getting the idea written on it is a side-effect.
This popularity seems to have been the big catalyst for trolls trying to make a buck, which means the whole blasted thing is deeply mired in a lot of people's long-term interests.
To me, this means the whole thing is going to be completely lacking a sensible view for decades -- both POV's that support "in the public good" (e.g. being able to use excerpts of copyrighted material for publication/research/etc, make digital backups of your property) as well as being compensated for the service (e.g. selling copies of your music to pay the bills so you can write more songs).
"Depriving" is a somewhat loaded term that implies a "take" behaviour to you, but it's just not strictly true.
In reality, most end-user corp's have an in-house support team of a size and skill that's comparable to their level of reliance on the systems. And when you try to lay blame or get compensation from the "creator", they always have excuses to avoid paying for it.