I was not really that impressed by the examples -- I expected something much more sneaky. All of those would easily be caught by writing proper unit tests.
Place 3: Increases file size (easy check) Place 2: Does not zero out (easy check) Place 1: Uses ASCII format, would not survive conversion to binary. Any unit test against this would probably expect '0', not '00' or '000' and thus would fail.
1) So it can unexpectedly change look, remove "unpopular" features or add new "features"? 2) So it can suddenly start behaving differently, start crashing or not work at all anymore? 3) So it can start spying on me, or otherwise add features that were not in the initial version I installed?
No, thank you. I prefer to run the software *I* installed -- I already deal with enough stupid problems, and I donot want to deal with new ones when I arrive home and the stupid system decided to update itself.
Security updates be damned. Run a decent system to begin with and there will not be a problem.
1) Such a device cannot be fooled. Human ingenuity seems to be underestimated. 2) The "explosives" are actually in an "explosive" configuration during this scan. 3) There are no other means of causing havoc on a plane -- acids, poisons, bio-weapons.. but I guess if only all passengers are killed and the plane survives it doesn't really "count", after all there was no monetary loss.
I'm selling this piece of used chewing gum that will make "Everything you ever desired come true". It says so on the box I put it in. Just $20 for you.
Some games even require you to agree to the EULA each time you start it. Some of these are online games. I wonder if anyone would notice if the EULA had subtle changes for a few days where you agree to handover your firstborn after having pressed "I agree" for the 50th million time. This alone should make it pretty clear that a simple click cannot be legally binding. Or do they really expect you to read and check it fully every time?
So... I could buy 1 million copies, refuse to agree with the EULA 1 million times, and get 1 million refunds from the publisher? That would be interesting to see...
1) It means we need to support two languages instead of one, with all that that entails (a proper debugger, expert knowledge, etc) 2) Stored procedures cannot do ALL business logic -- there comes a point where the business logic requires something that is near impossible to do within a stored procedure -- better to just keep it all together in your LANGUAGE OF CHOICE, not in some crappy half-assed non-compiled script crap that database vendor X whipped up in an afternoon because it looks good on their feature list 3) Because you don't want to have to deal with Oracle's horrid error messages anymore than absolutely necessary
I was not really that impressed by the examples -- I expected something much more sneaky. All of those would easily be caught by writing proper unit tests.
Place 3: Increases file size (easy check)
Place 2: Does not zero out (easy check)
Place 1: Uses ASCII format, would not survive conversion to binary. Any unit test against this would probably expect '0', not '00' or '000' and thus would fail.
Automatic updates can break things.
Why would I want automatic updates?
1) So it can unexpectedly change look, remove "unpopular" features or add new "features"?
2) So it can suddenly start behaving differently, start crashing or not work at all anymore?
3) So it can start spying on me, or otherwise add features that were not in the initial version I installed?
No, thank you. I prefer to run the software *I* installed -- I already deal with enough stupid problems, and I donot want to deal with new ones when I arrive home and the stupid system decided to update itself.
Security updates be damned. Run a decent system to begin with and there will not be a problem.
I would not do it like that. I'd do:
350 * 3(00) = 1250(00)
1250(00) + 7(00) * 3 = 1271(00)
Then I'd substract 3570 and 357 (300 - 289 = 11 = 10 + 1)
It would still take me a while to do.
Well, a knife can only do minor damage to an airplane. Deodorant is much harder to get rid off.
Well, lives are expendable. Aircraft are not.
Yeah... I'd like to have 20 of those lying around instead of having 20 passwords...
Startup time? I don't think I would notice the difference when it is well below half a second.
[~]$ time java -jar /data/Backup.jar
error parsing commandline: Missing required option: [-c continue the last backup, -i create a new incremental]
usage: Backup [options] databasefile target dir|files...
-c,--continue continue the last backup
-h,--help display this help
-i,--incremental create a new incremental
real 0m0.163s
user 0m0.131s
sys 0m0.022s
...and how would it effect those languages when there's only a sub-standard free JVM available?
Many companies build their crap in their in-house-developed-tool-of-choice. It says nothing about whether they also want to support it publicly.
It's already been invented. It's called a Burka. It's popularity should shoot up once western society sees the benefits.
There are two now. There will shortly only be one that matters though, and it won't be Oracle's.
Microsoft, being a commercial entity, has some trouble catering to the people that don't want to be bothered by exactly those entities.
One would think that "work" usually being the most anal about "security" it would be the place where IE was seen least.
Oh good, so with PostgreSQL, you get just the bits you are in interested in then without any fluff?
There's a lot of genes. What are the chances of finding a gene that happens to match the political views of those tested given a sample size?
Assuming that:
1) Such a device cannot be fooled. Human ingenuity seems to be underestimated.
2) The "explosives" are actually in an "explosive" configuration during this scan.
3) There are no other means of causing havoc on a plane -- acids, poisons, bio-weapons.. but I guess if only all passengers are killed and the plane survives it doesn't really "count", after all there was no monetary loss.
Until such time they can get away with it again of course. They played their cards too early, and we now know what their hand is.
Not all developers. This developer will pack up and leave if forced to eat garbage.
All I have to say is... a GPU is like a CPU. We're gonna get patents for everything twice now, just like with handheld devices?
...informants, like the people watching the CCTV footage for example? I'm sure those still classify as regular people.
I'm selling this piece of used chewing gum that will make "Everything you ever desired come true". It says so on the box I put it in. Just $20 for you.
...what is this magic world you live in where people do other people's work for free because it was posted on a website?
Some games even require you to agree to the EULA each time you start it. Some of these are online games. I wonder if anyone would notice if the EULA had subtle changes for a few days where you agree to handover your firstborn after having pressed "I agree" for the 50th million time. This alone should make it pretty clear that a simple click cannot be legally binding. Or do they really expect you to read and check it fully every time?
So... I could buy 1 million copies, refuse to agree with the EULA 1 million times, and get 1 million refunds from the publisher? That would be interesting to see...
What's wrong with stored procedures?
1) It means we need to support two languages instead of one, with all that that entails (a proper debugger, expert knowledge, etc)
2) Stored procedures cannot do ALL business logic -- there comes a point where the business logic requires something that is near impossible to do within a stored procedure -- better to just keep it all together in your LANGUAGE OF CHOICE, not in some crappy half-assed non-compiled script crap that database vendor X whipped up in an afternoon because it looks good on their feature list
3) Because you don't want to have to deal with Oracle's horrid error messages anymore than absolutely necessary