Don't know about Android but I was under the impression that Windows takes up more resources than iPhone OS (and Atom is more power-consuming than ARM).1. be slower than Windows or Android-based devices built on Atom
Don't know about Android but I was under the impression that Windows takes up more resources than iPhone OS (and Atom is more power-consuming than ARM).1. be slower than Windows or Android-based devices built on Atom
You do know that ARM chips can go up to Dual Core 2GHZ right? (Or the current specification can, either one. Cant remember)
http://en.wikipedia.org/wiki/ARM_Cortex-A9_MPCore
And Cocoa Touch has all the functionality of Cocoa. Its GUI functions just have been changed for touch format.
If the physical design is done by Apple (PA Semi), it can be a very fast chip indeed.
Cocoa Touch doesn't have all the functions of cocoa, but it does have many of them. A large percentage of the SDK is present, but not everything. And some of what is present is incomplete compared to full-blown cocoa. It does of course, have additional packages, like UIKit.
Such a device would:
1. be slower than Windows or Android-based devices built on Atom
2. have very limited API compared to full-blown Windows API.
3. have no support for Flash memory (would it even have a user-exposed file system?)
These "issues" perhaps could be compensated somehow but it is not obvious. If, on the other hand, it will have e-ink-like screen, be very thin and hav very long battery life then it could be useful (albeit as a niche product).
It has GUI based features removed according to my Obj-C book. I was talking about useful features though.
---
Remember those specifications are at 65nm, what if Apple used 45nm?
It's also missing a bunch of non-gui stuff, like support for rich text in nsstring, high-level coredata stuff, etc. The gui stuff is just the most obvious difference, but any mac programmer invariably runs into little non-gui gotchas any time they write any code for iphone.
I'll have to tell the author. Hes a local guy, I'm just going through it to see if it makes sense.
You got a definitive source for that?
Advantages of ARM/Cocoa touch: much better battery life, UI designed for touch, comparatively consistent UI without decades of cruft, 21st century SDK that is incredibly easy to code for, presumably some version of the app store makes it easy for people to go into business to sell their apps (of course the sdk and app store stuff works for a mac os-based approach, as well).
Well, I'm an iphone developer, so...
Here's just one of the examples to which I earlier referred (no rich text string on iphone):
http://stackoverflow.com/questions/729135/why-no-nsattributedstring-on-the-iphone
That's where things start to get interesting. While it's good to have easy-to-use API, inevitably this comes with some tradeoffs and in this case the tradoff is limited functionality. It might be fine for the phone but a tablet is a different matter. Would the customer prefer 130K amateurish applications or, say, 100 good ones. Will Google maps work there? (Well, we all know that's a totally different story) Well designed, content and GUI rich applications are important.
So the tablet is going to run iPhone OS I guess? Epic fail.
And if I was in the market for a tablet, I would take one that can run a full, regular copy of Windows 7 over one that runs the iPhone OS.
I know the iPhone OS is based off OSX...what I meant was the tablet should run a full version of Snow Leopard. The iPhone OS makes sense on a small screen, but if this is a full screen tablet, then it should run full OSX.
I have doing pc before it was cool.
The reason iphone apps aren't more functional has much more to do with lack of hardware resources and natural tradeoffs that come from having such a tiny screen. Of course, there are some important limitations to iphone that need not be present on the tablet. The most important, IMHO:
1) no shared filesystem, or any other reasonable method of communicating between programs or between machines (the url method doesn't cut it for anything other than simple messages, and having to create ad hoc connections constantly for each program that wants access to files on your desktop/laptop is dumb)
2) no multitasking/background apps
3) apple's arbitrary app store limitations (no replacing springboard, no web browsers, no interpreted code, etc.)
But what does full OS add that's useful.
Carbon legacy but that isn't going to pick up the touch screen controls like cocoa apps can so is it worth supporting.
They can add any of the rest the API's and built for LLVM.
So ARM or x86 is not much and issue in choosing between the two that is the joy of LLVM even the GPU can be used.
The last big difference is Cocoa vs Cocoa Touch UI elements?
Not there is much difference in the structure of those other than the important thing one works plug in mouse/keyboard the other touch screen.
Although adding window resizing to cocoa touch when on big screen could be really useful.
It would seem like a lot of the work Apple did with Snow Leopard was bring Mac and iPhone OS closer together so a device lie this can be added to the line up.
I get ya, but the ability to run Photoshop, office, etc is very valuable, and don't count on there being reasonable replacements any time soon. iWork and openoffice are not reasonable replacements for office for many people, and nothing on iPhone comes close. Likewise pixelmator, etc. is no Photoshop, and neither is Layers.
I said this a while ago and I'll say it again - the iPhone OS and the app store is the future of Apple computers. At some point OS X will be dropped and replace by a future version of iPhone OS.
But its not the iPhone OS that is limiting the ability to run applications like that; its the screen size, battery life and processor speed. Once those issues are resolved companies like Adobe and Microsoft will be all over it like a rash.
To quote Mr T, 'quit your jibber jabber, fool'. Honestly, you're not making any sense whatsoever. Come back when you can form a coherent sentence.
MS make plenty of hardware. People on this board call a lot of things failures, even epic failures. Doesn't make it true.
But its not the iPhone OS that is limiting the ability to run applications like that; its the screen size, battery life and processor speed. Once those issues are resolved companies like Adobe and Microsoft will be all over it like a rash.
I get ya, but the ability to run Photoshop, office, etc is very valuable, and don't count on there being reasonable replacements any time soon. iWork and openoffice are not reasonable replacements for office for many people, and nothing on iPhone comes close.
If you really need to run one of those legacy apps, some of which would likely suck a thin handheld device's battery dry in minutes, you can do that right now using a VNC or Remote Desktop app (there are over a dozen in the App store), and connect back to a much faster and really hefty server (quad core, 16 GB of DRAM, etc.) in the cloud somewhere (rent them for pennys a minute from Amazon or Rackspace), while waiting in line at the coffee shop, from your iPod Touch.
No reason that remote viewing of legacy apps wouldn't work even better from a hypothetical tablet device with a larger display area.
If this happens, I will gladly go back to Microsoft world.