or Connect
New Posts  All Forums:

Posts by TheOtherGeoff

 well my electrical engineering glasses were on when I read this and the referenced articles and the fact that the a7 chip has both 64bit and 32bit cores makes 'compatibility mode' somewhat spurious.  Obviously you need better glasses, as you don't see the basic architecture of the a7.   Out of the box,  if it was compiled in 32bit, you run in 32bit.  and obtw, the next run through Xcode, create a universal binary, send to AppStore, and you're running 64 bit.   Apple's...
 4s... yep... it will go to that $299 level... or lowerRemember a lot of carrier/gov't contracts have 'minimum number of production/replacement years'  My guess is we have at least 2 full years to cover a 4 year iPhone 4 coverage [gotta to have the same formfactor... specifically the cable support] the 5c... my guess is it will:be updated every 6-9  months Will incrementally add 5s capabilities first A7 Chip/M7 (the May 14 5c) Then camera (the October 5c... oh then the 5s...
  'requiring a quota' can or can't be illegal... but 'stipulating a quota for discounts' is not. Typically quotas are for a discount rate.  Apple wants a defined production rate, and Docomo wants to get as much 'profit' as possible per iphone sale, and therefore will commit to receiving X devices per month at a net discount on a 24 month schedule.    Perfect for Apple in reducing production variance risk, and good for docomo, as it can lower it's short term risk (more...
 Apple by nature (since it's NeXT days) has fully supported universal development [at one point RS6000,HP-RISC, Intel, 68K, and rumors of MIPS binaries for OpenSTEP existed as 'fat' binaries].   That's now over 20 years of experience.   It's the reason why moving OSX  to Intel went relatively smoothly.  And once off Carbon , moving to 64bit was even easier. The closer you are to the iron the harder the port.  with iOS, it's REALLY hard to get down to the silicon, so...
 And who has better control of their operating system?
 64 bit _is_ the obvious progression... However the timing of their announcement reeks of FUDishment.    And really... how many people buy a phone because of its internal datapath bandwidth?    eventually, all phones will have a fingerprint reader... just like [almost] every keyboard is QWERTY [or Kanji or whatever]... It's an expected interface standard. Natural selection in the consumer marketplace.
 you forget that Samsung can take the open source code and convert themselves.   The don't have to wait for Google to do it. The bigger issue is that what about all those fragments and developers cross supporting across 3-5 versions of OSes,  8 or nine geometries, and now 2 CPU register architectures. Most people who buy a Samsung phone buy for nothing but the screen size.   I know quite a few who say 'You should try my Samsung iPhone.'  I doubt anyone will even remember...
"ya awl is on mah propty... I gahn ta shu you"   Tennessee:  "you are on my property... I am going shoot you"   Texas:  "Your Oil is on my property... I am going sue you"
 what bugs?  It's a Mavericks timing issue.   While I doubt they planned on simultaneous release, they had to a) announce and b) test it.  Now they just have to get the back end deployed (your desktop).
If the passwords are for logging into cloud/internet services... Does your point even matter? 
New Posts  All Forums: