Bye bye pharo on the iPhone
Locked
Bye bye pharo on the iPhone
 
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
On 2010-04-10, at 9:08 AM, Stefan Marr wrote: > There are rumors, that this change is motived by technical reasons related to multitasking. > I could imagine some nice tricks related to the efforts Apple is putting into LLVM, to actually have a 'smart' C/C++ runtime system which allows to assess what kind of activity profile an app is going to exhibit. > This is already hard enough with C, prohibiting any VM technology seems to be a reasonable step, if they are actually going to employ any analysis techniques to get their multitasking stuff 'right'. > > But this is pure speculation. > > In the light of Steve Job's remark: "We just shipped it on Saturday, and we rested on Sunday." everything is possible, even that he is just going... > >>> http://www.macrumors.com/2010/04/09/fallout-from-apples-exclusion-of-flash-to-iphone-export-continues/ > The primary reason for the change, say sources familiar with Apple's plans, is to support sophisticated new multitasking APIs in iPhone 4.0. The system will now be evaluating apps as they run in order to implement smart multitasking. It can't do this if apps are running within a runtime or are cross compiled with a foreign structure that doesn't behave identically to a native C/C++/Obj-C app. > > "[The operating system] can't swap out resources, it can't pause some threads while allowing others to run, it can't selectively notify, etc. Apple needs full access to a properly-compiled app to do the pull off the tricks they are with this new OS," wrote one reader under the name Ktappe. > << An hour with some unix internals book and reading a bit about suspend/resume, and reflect on what happens when you sleep your unix based laptop shows there is no magic involved, just a bit of change to how Processes are managed. -- =========================================================================== John M. McIntosh <[hidden email]> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com =========================================================================== _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
smime.p7s (3K)
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
See
http://en.wikipedia.org/wiki/Kill_(command) for discussion of kill suspend/resume. The simple case is likely the unix process scheduler sends you a suspend, later a resume if it chooses to wake you up, otherwise a resume and quit. The more complex cases are when you want to do audio, voip, or location. In this case you are setting up an agreement between the app and the scheduler to wake you when audio needs servicing, a socket requires keep-alive & traffic in processing, or a change to location is made. Part of that agreement is restrictions on what you can do in the background, like no UI or openGL work, no listening sockets, etc.. Again the unix process manager here may re-nice you to a lower priority if you do too much, or decide you are a nuance and kill you. Obviously Apple may when testing decide that your app uses too much CPU as a background process and not approve. You can ask for a limited amount of time to run as a background task when you are shoved to the background, but that is finite. In general the idea is that you are waken to processes audio, location, and socket interrupts, from an event driven expectation and you go back to sleep once the chore is done. On 2010-04-10, at 10:27 AM, Stefan Marr wrote: >> Nonsense. >> >> An hour with some unix internals book and reading a bit about suspend/resume, and reflect on what happens when you sleep your unix based laptop shows there is no magic involved, just a bit of change to how Processes are managed. > Ehm is it that easy? I don't know the internals of their new stuff. But when I read the announcement, it sounded more like they want you to provide 'kind of services', so that only part of your app needs to stay alive in the background, for instance to play music, or track location data. But you cannot just swap out/deschedule the whole process, at least not in a model which uses threads instead of processes. > > But I am just guessing... -- =========================================================================== John M. McIntosh <[hidden email]> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com =========================================================================== _______________________________________________ Pharo-project mailing list [hidden email] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project |
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
Re: Bye bye pharo on the iPhone
|
|
| Free forum by Nabble | Edit this page |