Let me correct myself. I care that four U.S. nationals died, leaving behind grieving loved ones.
But Mr. Obama didn't kill them. Mrs. Clinton didn't kill them.Terrorists did.
Mr. Obama isn't running for president. Whatever was or wasn't done in Benghazi is insignificant compared to the war crimes of Bush, Cheney et al.
Who's more likely to start another needless war if elected president? Mrs. Clinton, or Jeb Bush?
Guess what Slashdot, people read other websites. I don't read
Of course, my Socialist-Totaltarian regime has a multi-pronged approach to addressing this:
1. All children will be confiscated from their parents and birth and raised in sanitary state-run facilities. Processes will be put in place to insure that no violent or sexual abuse of the children will be possible.
2. All children will be reversibly sterilized at puberty. Anyone wishing to breed will be required to pass a parental competency test.
3. For anyone unable to pass a parental competency test, the state will choose a partner based on specially-designed algorithms designed to insure the happiness of the couple.
4. All religion will be illegal except for the state-run one, which will involve Smurfs. Non-Smurfy behavior will be dealt with harshly.
I predict that my society would reach the "Utopia" stage within three generations.
I think my first programming attempt was recreating pong on a timex zx80 that I had checked out from the library.
I think 'being run over a truck' was loose way of saying 'dying in a traffic accident'
The deeper I get into OO, the more I start to understand that getters and setters are just as bad as exposing members of your object to the public. If you have to expose the working data of your objects that regularly, you're not working at the correct level of abstraction. A lot of the coding style I see in java is geared toward "I'll need this in the future" or "I have no idea what I'm going to need in the future, so I'll make this bit so generic that it can do anything." Both of these habits are incredibly bad practices that have been superseded by refactoring. A lot of inexperienced programmers think that once they've designed and coded some shit, it's carved in stone forever after that. I've seen countless cases of companies wringing their hands and working around problems in code that can be fixed with trivial changes to program design and adjustments to half a dozen or so objects.
I have much the same problem with introspection as I do with getters and setters. People say "Oh we have to use introspection because someone might want to write something new and drop it in there and we don't know how it'll behave!" Again, that's limiting your current design because you don't know what will happen in the future. Design a solid and maintainable interface NOW and if you need to change it in the future, change it in the future. Don't build some twisty maze of introspection that delegates any real work 10 objects away from the functions that initiate it just because someone in the future might want to write something else! And quite frankly, no one EVER WILL, because that would require knowing implementation-level details of the ball of shit you rolled up to support that.
I wasn't arguing that a contract with a professional photographer means anything to people attending, just that they have the ability to restrict vendors to these events. The student running around taking pictures and then selling them online could be construed as acting as a vendor.
I'd love to hold society to the standard that no child should have to risk death due to parental stupidity. That's just not California. If you really want to uphold this ideal, you'll have to crusade for myriad causes, including gun control, obesity-fighting measures, tighter distribution of driver's licenses, promotion of breastfeeding, etc, etc. On the list of annual deaths in California caused by parental stupidity, lack of vaccination is near the bottom of the list.
All of this is true. However, lack of vaccination will rapidly climb the lists if America's current anti-science, anti-education and anti-logic trends are allowed to continue.
Somehow I doubt that is going to work on my $70 Seagate 7200RPM hard drive plugged into my $50 motherboard or $20 SATA controller card. However, by all means let me know if it will.
Plus, COW filesystems offer a lot more than just data checksumming.