And that's why Apple's private API's are private, and that's why the App store rejects apps that use private API's. Some things are just too dangerous to let people have programmatic access to them, in spite of geeks with a high overdeveloped sense of "can" and a highly underdeveloped sense of "should" screaming about how unfair the engineering tradeoff is.
"Qapla mates and welcome to the caves. I'm Gorvok and I'll be your guide today. Gakh and bloodwine are available at the concession stand on the surface, and if you truly have the stomach of a klingon, we also have Fosters. Just like a bird of prey, the caves also don't have bathrooms so make sure to hit the loo before we start. If you happen to get lost in the caves, just remember it's a good day to die and I'll see you in Stovalkor."
1. Shortages of people who patch their systems 2. Shortages of companies who are willing to pay security specialists a decent wage 3. Shortages of CTO's willing to pay for migration away from IE6 to something standards-compliant 4. Shortages of armed services who'd take overweight computer professionals over 30 5. The tooth fairy 6. Unicorns
But a shortage of cyberwarriors? That seems a bit far fetched.
Re:Oh God, A GNUFreak...
on
R In a Nutshell
·
· Score: 2, Funny
The letter R is under the GPL license, therefore any derivative work that uses the letter R, such as Hamlet, the US Constitution, the Forums section of Penthouse magazine, and this post grant the reader the same rights and privileges afforded to a three year old putting a single magnetic letter R on a refrigerator.
Nice try, but the North Koreans will just send wave after wave of their own men at the killbots until they reached their pre-programmed kill limit of 999,999.
Couldn't they harness all that energy that blows up manhole covers into some kind of renewable energy? Feed the sewer gas back into natural gas lines, attach pistons to manhole covers, etc
Open a database book's index. Look up "natural key". If the author presents natural keys as a viable alternative to surrogate primary keys, then the author doesn't know what he or she's talking about and you should move on to the next book. Especially if they pull the whole "meaning" schtick.
On the other hand, if the author gives you great real-world examples as to why you should use surrogate primary keys over natural keys in ever possible situation, then you've got a winner.
The proper logo for a Cybercommand that could do its job well would be a PHB skull wearing a military cap with the motto "Defending against all enemies foreign, domestic, and corporate."
If the anti-smoking app only gets 10 people to quit smoking and the drinks tracker only prevents 10 serious DUI accidents, the entire app foray would still pay for itself tenfold.
So you want to build 100 doodads using 10 sub-assembly widgets you've already built plus 90 more identical widget sub-assemblies you have to make but you only want to have to purchase enough parts to build the 90 taking into account the 10 you've already built, and you have to comparison shop between 10 different vendors who all have different names for the same part, and half of whom have changed the part number for the part since the last time you've bought it, and the doodad you're trying to build has a bill-of-materials hierarchy 10 levels deep. Add vendor traceability just for kicks so you know who sells you bad capacitors for only the other 90 you have to build.
Simple spreadsheet/plastic boxes ain't gonna cut it at this level.
Slashdot Mirror
Is that Apple gives you a real bonafide OS disc with the computer you buy.
If there are mutant boar running around that ruminate (i.e. chew their cud), you'd have the beginnings of a kosher pork industry.
And that's why Apple's private API's are private, and that's why the App store rejects apps that use private API's. Some things are just too dangerous to let people have programmatic access to them, in spite of geeks with a high overdeveloped sense of "can" and a highly underdeveloped sense of "should" screaming about how unfair the engineering tradeoff is.
Billions of dollars are also wasted every year in the manufacturing and transporting of fire extinguishers, 99% of which will probably never be used.
"Qapla mates and welcome to the caves. I'm Gorvok and I'll be your guide today. Gakh and bloodwine are available at the concession stand on the surface, and if you truly have the stomach of a klingon, we also have Fosters. Just like a bird of prey, the caves also don't have bathrooms so make sure to hit the loo before we start. If you happen to get lost in the caves, just remember it's a good day to die and I'll see you in Stovalkor."
I think of Porn a huge malware vector for 14 year-olds to pwn your phone. Does that count as "thinking of the children"?
iPhone has fart machines. Android counters with bigger and better and beefier fart machines. That's progress for you.
I'd believe in stuff like
1. Shortages of people who patch their systems
2. Shortages of companies who are willing to pay security specialists a decent wage
3. Shortages of CTO's willing to pay for migration away from IE6 to something standards-compliant
4. Shortages of armed services who'd take overweight computer professionals over 30
5. The tooth fairy
6. Unicorns
But a shortage of cyberwarriors? That seems a bit far fetched.
Russia can shoot down the moon!
The letter R is under the GPL license, therefore any derivative work that uses the letter R, such as Hamlet, the US Constitution, the Forums section of Penthouse magazine, and this post grant the reader the same rights and privileges afforded to a three year old putting a single magnetic letter R on a refrigerator.
He'd make a amazing Davros.
It's like Salt Potatoes without all the extra work of adding salt.
Because I believe strongly that the truly competent are doing LAPP. In my experience MySQL's a freaking code cowboy magnet.
Because doing that would make farting both a socially acceptable behavior and a viable industry.
Nice try, but the North Koreans will just send wave after wave of their own men at the killbots until they reached their pre-programmed kill limit of 999,999.
Maybe first tutorial has the student print "Hello Kitty."
Especially if it's like papyrus and you substitute water for a pitcher of vinegar.
Couldn't they harness all that energy that blows up manhole covers into some kind of renewable energy? Feed the sewer gas back into natural gas lines, attach pistons to manhole covers, etc
Open a database book's index. Look up "natural key". If the author presents natural keys as a viable alternative to surrogate primary keys, then the author doesn't know what he or she's talking about and you should move on to the next book. Especially if they pull the whole "meaning" schtick.
On the other hand, if the author gives you great real-world examples as to why you should use surrogate primary keys over natural keys in ever possible situation, then you've got a winner.
The proper logo for a Cybercommand that could do its job well would be a PHB skull wearing a military cap with the motto "Defending against all enemies foreign, domestic, and corporate."
If you can put up with an uncomfy concrete floor in your bathroom you could save a fortune in the long run on matches and glade plugins.
If the anti-smoking app only gets 10 people to quit smoking and the drinks tracker only prevents 10 serious DUI accidents, the entire app foray would still pay for itself tenfold.
So you want to build 100 doodads using 10 sub-assembly widgets you've already built plus 90 more identical widget sub-assemblies you have to make but you only want to have to purchase enough parts to build the 90 taking into account the 10 you've already built, and you have to comparison shop between 10 different vendors who all have different names for the same part, and half of whom have changed the part number for the part since the last time you've bought it, and the doodad you're trying to build has a bill-of-materials hierarchy 10 levels deep. Add vendor traceability just for kicks so you know who sells you bad capacitors for only the other 90 you have to build.
Simple spreadsheet/plastic boxes ain't gonna cut it at this level.
The other white meat.
According to Dr Dan Streetmentioner's Time Traveller's Handbook of 1001 Tense Formations, this is the grammatically correct use of the present future tense.