I have a bunch of iOS devices and a Motorola XOOM 2. On paper, the XOOM 2 should kick the arse of, say, an original iPad but it does not. I have tried to browse developer.android.org on both, and only the iPad renders the API Reference correctly: the XOOM leaves the lower-right pane completely empty much of the time.
To be fair I should compare it to my iPad 2, in which case it looks even worse. Pages generally take an age to load, and the only way to get acceptable performance is to turn off the flash plugin. This means you don't get any videos on the majority of sites unless you enable debug mode in the browser and tell it to use the UAString of an iPad.
Now you can point out that the XOOM 2 is running Honeycomb 3.2.2 and not the latest greatest Ice Cream Sandwich 4.0.x, but this is not my choice: Motorola haven't issued an update for ICS yet so I can't have it.
Bigger range? Yes.
Better OS? No. What kind of retard thinks perpetuating a destination-information-free back button is a smart idea? I lose 80px at the bottom of the screen for that, and there are always 600px of blackness which could be used to hint where tapping it will take you, but no.
More Open? Maybe.
Lower Cost? If you don't value your time.
Programmable? Nowhere near as easily as iOS. On iOS I only need to care about the current release because everyone likely to purchase an app has 5.0.1. On Android I have to code for the archaic 2.2 to meet the same market share.
Basically if you buy an iOS device Apple can screw you over, but probably won't. If you buy an Android device Google, the device manufacturer and (if applicable) the carrier can screw you over, and 2 out of the 3 probably will.
I did a similar exam in, I guess, 1999; you could get an A+ in about 20 seconds without looking at the screen. The last sentence advised you to compare what you had done to sample.doc, so I typed:
Ctrl+O sample.doc Enter Alt+F A.doc Enter.
I then went through the paper to verify that there weren't any hidden extras or obvious flaws in the sample (there weren't) and delete any metadata (there was none).
When generating a 1024-bit random number which you hope is prime you take 1022 bits of random data and then put those bits in a 1-sandwich. For a 512-bit random probable prime you use 510 bits of random data. Having generated the probable prime you then test if it is very likely prime and if not you repeatedly add (or subtract, as long as your algorithm is consistent) two and retest until the test says you've found a winner. Because prime numbers are not perfectly evenly distributed (if they were we could find them very easily) there are sometimes large gaps between primes and random generation using this method will (over many attempts) pick primes following unusually large inter-prime gaps much more commonly than primes following unusually small inter-prime gaps.
So far as I know no-one knows what the distribution of 512- and 1024-bit primes really looks like: but supposing there were only 2^30 very-large gaps in the 1024-bit prime space it would be very worthwhile looking for common factors in 2048-bit RSA public keys.
Because http://en.wikipedia.org/wiki/Credit_card#Costs_to_merchants means the merchant owes the card company at least $0.40 (1% of two $20 transactions) and more likely $1.20. Add postage, packing and the cost of paying employees to unpack and refile the discs and record which customer has returned them and you're probably looking at $5 per cycle before you break even.
Frankly I'm amazed netflix et al are profitable at the prices they charge.
NTFS already supports paths longer than 255 bytes; you just need to use the right APIs to access them.
It used to really piss me off that the JVMs for Windows weren't using the long-path APIs. It stopped annoying me when I stopped needing to write Java programs.
If what you need documenting is at the level of comments within a file your problem is not that your programmers aren't writing comments it's that they are not sriting good software. If meaningful class, method and variable names and sensible expression constructs are used there is no benefit to be had from comments.
I'll make an exception for comments to explain why a given piece of code is not actually batshit insane but required to work with a third-party library you have to use.
Producing documentation that spans classes and discusses how things are designed to work at run-time is, however, part of the job.
If you're using precompiled software what does it matter? Unless you build from source you have no evidence that the source on offer in any way corresponds to the binary you're running anyway.
So how do the developers of the project move their families to France?
They just walk across the bridge near Strasbourg.
More seriously, it would be interesting to know the approximate geographic distribution of contributors to such projects. Most open source stuff I've downloaded has been in the origin-unknown category, or from european developers.
Doesn't work – you can modify the VM's memory contents and read/mutate its I/O operations from the host machine. It would in many respects make the attacker's job easier as they would only have one OS/browser version to go at.
Even better if you are a little technical, set up a "frugal" boot partition. This will unpack and boot a CD image much faster than booting from CD and when you power down it doesn't keep any state. No viruses survive the reboot.
Since it's on writable media, this is only true until someone writes a more sophisticated piece of malware. The same applies to a Live CD on a CD-RW to an extent. A Live CD on a finalized CD-R really is immutable.
UNLESS you forcibly close that session by closing your browser.
Doesn't help. Web servers do not (and cannot) know when your browser has been closed.
Besides, if the hijacker has done their job properly and you've only ever been communicating with the server you think you're connected to via their proxy, you can't disconnect unless they let you do so.
The relative error in a measurement is unaffected by multiplying it by a constant, however large. If your m is accurate to 1in 1.75e-7 the result of e=mc^2 is also accurate to 1 in 1.75e-7.
System i, formerly iSeries, AS/400 are minicomputers.
System z, formerly zSeries, System/390, System/370, System/360 are mainframes; some of which have longer uptimes than AS/400 (or indeed Sun) have existed for.
IEFBR14 is now about 30 years old, and in all that time there have only been 2 bugs reported: 1) IEFBR14 doesn't set a return code; this was reported and fixed about 25 years ago 2) IEFBR14 source contains no comments; this was reported and fixed about 20 years ago
Show me another product which has that kind of bugs/time ratio...
Slashdot Mirror
I have a bunch of iOS devices and a Motorola XOOM 2. On paper, the XOOM 2 should kick the arse of, say, an original iPad but it does not. I have tried to browse developer.android.org on both, and only the iPad renders the API Reference correctly: the XOOM leaves the lower-right pane completely empty much of the time.
To be fair I should compare it to my iPad 2, in which case it looks even worse. Pages generally take an age to load, and the only way to get acceptable performance is to turn off the flash plugin. This means you don't get any videos on the majority of sites unless you enable debug mode in the browser and tell it to use the UAString of an iPad.
Now you can point out that the XOOM 2 is running Honeycomb 3.2.2 and not the latest greatest Ice Cream Sandwich 4.0.x, but this is not my choice: Motorola haven't issued an update for ICS yet so I can't have it.
Bigger range? Yes.
Better OS? No. What kind of retard thinks perpetuating a destination-information-free back button is a smart idea? I lose 80px at the bottom of the screen for that, and there are always 600px of blackness which could be used to hint where tapping it will take you, but no.
More Open? Maybe.
Lower Cost? If you don't value your time.
Programmable? Nowhere near as easily as iOS. On iOS I only need to care about the current release because everyone likely to purchase an app has 5.0.1. On Android I have to code for the archaic 2.2 to meet the same market share.
Basically if you buy an iOS device Apple can screw you over, but probably won't. If you buy an Android device Google, the device manufacturer and (if applicable) the carrier can screw you over, and 2 out of the 3 probably will.
I can't; don't have mod points today.
I did a similar exam in, I guess, 1999; you could get an A+ in about 20 seconds without looking at the screen. The last sentence advised you to compare what you had done to sample.doc, so I typed:
Ctrl+O sample.doc Enter Alt+F A .doc Enter.
I then went through the paper to verify that there weren't any hidden extras or obvious flaws in the sample (there weren't) and delete any metadata (there was none).
Don't know about Premiere but I do this all the time with FCP X/Compressor. I understand not all players will play them, but my PS3 does.
There is another consideration.
When generating a 1024-bit random number which you hope is prime you take 1022 bits of random data and then put those bits in a 1-sandwich. For a 512-bit random probable prime you use 510 bits of random data. Having generated the probable prime you then test if it is very likely prime and if not you repeatedly add (or subtract, as long as your algorithm is consistent) two and retest until the test says you've found a winner. Because prime numbers are not perfectly evenly distributed (if they were we could find them very easily) there are sometimes large gaps between primes and random generation using this method will (over many attempts) pick primes following unusually large inter-prime gaps much more commonly than primes following unusually small inter-prime gaps.
So far as I know no-one knows what the distribution of 512- and 1024-bit primes really looks like: but supposing there were only 2^30 very-large gaps in the 1024-bit prime space it would be very worthwhile looking for common factors in 2048-bit RSA public keys.
Clearly the work of a Sith.
But which was it, the master or the apprentice?
No need to shoot it. I have a Mac: I'll upload a virus to take care of it.
I want to see people at least in one piece after a car accident.
I want to see people in at most one piece after a car accident.
Because http://en.wikipedia.org/wiki/Credit_card#Costs_to_merchants means the merchant owes the card company at least $0.40 (1% of two $20 transactions) and more likely $1.20. Add postage, packing and the cost of paying employees to unpack and refile the discs and record which customer has returned them and you're probably looking at $5 per cycle before you break even.
Frankly I'm amazed netflix et al are profitable at the prices they charge.
NTFS already supports paths longer than 255 bytes; you just need to use the right APIs to access them.
It used to really piss me off that the JVMs for Windows weren't using the long-path APIs. It stopped annoying me when I stopped needing to write Java programs.
If what you need documenting is at the level of comments within a file your problem is not that your programmers aren't writing comments it's that they are not sriting good software. If meaningful class, method and variable names and sensible expression constructs are used there is no benefit to be had from comments.
I'll make an exception for comments to explain why a given piece of code is not actually batshit insane but required to work with a third-party library you have to use.
Producing documentation that spans classes and discusses how things are designed to work at run-time is, however, part of the job.
causes damage to the posters reputation
If the poster wasn't AC, maybe
The story here is what?
If you're using precompiled software what does it matter? Unless you build from source you have no evidence that the source on offer in any way corresponds to the binary you're running anyway.
So how do the developers of the project move their families to France?
They just walk across the bridge near Strasbourg.
More seriously, it would be interesting to know the approximate geographic distribution of contributors to such projects. Most open source stuff I've downloaded has been in the origin-unknown category, or from european developers.
At most, all the fresh honey contained therein will come out. This may be less than all the fresh honey I want.
Doesn't work – you can modify the VM's memory contents and read/mutate its I/O operations from the host machine. It would in many respects make the attacker's job easier as they would only have one OS/browser version to go at.
Even better if you are a little technical, set up a "frugal" boot partition. This will unpack and boot a CD image much faster than booting from CD and when you power down it doesn't keep any state. No viruses survive the reboot.
Since it's on writable media, this is only true until someone writes a more sophisticated piece of malware. The same applies to a Live CD on a CD-RW to an extent. A Live CD on a finalized CD-R really is immutable.
UNLESS you forcibly close that session by closing your browser.
Doesn't help. Web servers do not (and cannot) know when your browser has been closed.
Besides, if the hijacker has done their job properly and you've only ever been communicating with the server you think you're connected to via their proxy, you can't disconnect unless they let you do so.
The relative error in a measurement is unaffected by multiplying it by a constant, however large. If your m is accurate to 1in 1.75e-7 the result of e=mc^2 is also accurate to 1 in 1.75e-7.
If it was e=cm^2 you'd have a point.
TwoGirlsOne.kp?
Just out of interest, do you work at IBM?
System i, formerly iSeries, AS/400 are minicomputers.
System z, formerly zSeries, System/390, System/370, System/360 are mainframes; some of which have longer uptimes than AS/400 (or indeed Sun) have existed for.
Not the same at all.
IEFBR14 is now about 30 years old, and in all that time there have only been 2 bugs reported:
1) IEFBR14 doesn't set a return code; this was reported and fixed about 25 years ago
2) IEFBR14 source contains no comments; this was reported and fixed about 20 years ago
Show me another product which has that kind of bugs/time ratio...
Why not split the difference with AC/DC's "For Those About to Rock"?
Well, the first valve-based stuff is probably what you're looking for.
I suspect that iron-core memory was denser than this stuff:
http://en.wikipedia.org/wiki/Core_memory