http://www.youtube.com/watch?v=lQnT0zp8Ya4

Така де, то търкаля някакви нишки и процеси.

Ама дет викат - не можеш да слушаш музика и да браузваш в нета едновременно. Бе то и аз трудно ходя и дъвча дъвка едновременно, ама не се продавам като хай-тек все пак

Абе това верно ли еднозадачно? Коя година сме?

Ама дет викат - не можеш да слушаш музика и да браузваш в нета едновременно.

Та ми е интересно мнението ви като програмисти, ако идеята
на сингъл-таскинга е с цел повишаване на надеждността.

Глуспости на търкалета са това, хич не ги слушай. Просто мултитаскинга
ще доведе до някои не толкова приятни неща за Епъл и мобилните оператори,
които пък ще доведат до изпускането на едни много кинти от завързания за сървиса потребител

> Microchip General Product Legal Information

Code Protect. Microchip products meet the specification contained in their particular Microchip Data Sheet.
Microchip believes that its family of products is one of the most secure families of its kind on the market today,
when used in the intended manner and under normal conditions. There are dishonest and possibly illegal
methods used to breach the code protection feature. All of these methods, to our knowledge, require using
the Microchip products in a manner outside the operating specifications contained in Microchip’s Data Sheets.
Most likely, the person doing so may be engaged in theft of intellectual property. Microchip is willing to work with
the customer who is concerned about the integrity of their code. Neither Microchip nor any other semiconductor
manufacturer can guarantee the security of their code. Code protection does not mean that we are guaranteeing
the product as "unbreakable." Code protection is constantly evolving. We at Microchip are committed to continuously
improving the code protection features of our product. Attempts to break Microchip’s code protection feature may be
a violation of the Digital Millennium Copyright Act. If such acts allow unauthorized access to your software or other
copyrighted work, you may have a right to sue for relief under that Act.

Пълно е с многозадачни системи търкалящи хиляди програми,
писани от различни програмисти без да се скапва сигурността и надежността .

> The iPhone Multitasking Myth

Wednesday, March 12th, 2008 at 4:00 PM - by John Martellaro

A few developers have complained about the wording in the terms of Apple’s SDK that restricts them to one iPhone application running at a time. Dan Dilger at Roughly Drafted on Thursday said it’s only partly true and some developers have misinterpreted the statement.

Everyone knows that the version of OS X in the iPhone is Unix. So why would Apple restrict developers, as they have, in the terms of its SDK, Mr. Dilger asked.

In order to explain what Apple is up to, Mr. Dilger took a look at the problems of WinCE and how, on paper, it looks good but fails in practice. "...WinCE proves that the general idea of having no limitations on third party background processes and concurrently running applications on a handheld device is a bad idea." The observations on Mr. Chris De Herrera, knowledgable about WinCE were cited.

"There are times when having multiple applications running at once causes the foreground application to slow down noticeably. This slowdown is due to the amount of time that the operating system is spending servicing background applications. In these instances, I recommend that users consider performing a soft reset."

The true operation of the iPhone is explained in a little more detail. In fact, applications can suspend and resume after a phone call and are not obliterated. In the current version, the iPod portion can continue to play music while one is surfing in Safari, so the iPhone certainly is using multitasking. The question really goes to the restrictions Apple has placed on developers to make sure the iPhone operates responsively.

The license Microsoft has given to apps in WinCE allow any app to hog the processor and bring a WinCE smartphone to its knees, and, basically, Apple wants to avoid that scenario by placing some minor restrictions on first generation iPhone native apps. The concerns of some developers are overblown, according to Mr. Dilger.