News for hackers. Stuff that matters.
Re:Multithreaded toolkits: A failed dream? (2004) by dnautics on Monday November 02, 2015 @04:05AM (#10490790)
BeOS did this fairly well, although I would say the biggest problem is when you activate the UI and the underlying app has become unresponsive... When your app crashes, you want your UI to reflect the crashed state of the app and similarly become unresponsive.
Re:Multithreaded toolkits: A failed dream? (2004) by mike_hearn on Monday November 02, 2015 @05:52AM (#10491116)
The developers of BeOS went on to do Android and went with the single thread model, partly because BeOS had a big problems with buggy apps full of race conditions and deadlocks.

Though IMO the Android API is incredibly confusing for a lot of developers. I've found very often that some devs (the more junior ones) don't understand that services and activities are just objects all hanging off a single process and event loop. Bizarre hacks to let services "communicate" with activities when a simple static global would have worked fine tend to abound.

Re:Multithreaded toolkits: A failed dream? (2004) by pjmlp on Monday November 02, 2015 @06:06AM (#10491167)
Those bizarre hacks help the service don't crash when the service needs to talk back to an activity that just got replaced between request/response cycle, because the user had the strange idea to rotate the phone.
Re:Multithreaded toolkits: A failed dream? (2004) by kllrnohj on Monday November 02, 2015 @10:23AM (#10492236)
If you had just used a static there'd be no need to talk to the activity directly. The bizarre hacks tend to arise because Java devs seem to consider static globals as icky.
Re:Multithreaded toolkits: A failed dream? (2004) by pjmlp on Monday November 02, 2015 @10:29AM (#10492281)
Global variables are icky, regardless of the language.
Re:Multithreaded toolkits: A failed dream? (2004) by pflanze on Monday November 02, 2015 @11:20AM (#10492718)
> The developers of BeOS went on to do Android

I haven't heard of this before, so I went searching. The only pieces I could find are:

Several ex-Be employees went to work for Danger after the company told to Palm. Some of them moved on to Android, which was co-founded by Danger co-founder Andy Rubin and acquired by Google. Others stayed on at Palm, but ended up joining Google after PalmSource (which was spun out of Palm) was acquired by Access. (http://readwrite.com/2011/06/29/a-look-back-at-the-beos-file...)

Today (June 2004), Baron [Arnold] and a bunch of other ex-Be engineers are working at Danger. (http://www.osnews.com/story/7265)

So, "Baron Arnold and a bunch of others" went from Be to Danger Inc., which was acquired by Microsoft in 2008. Andy Rubin went on from there to become one of the four founders of Android, Inc., but I can't find any indication of Andy Rubin having worked for Be, and none that other people followed him from Danger.

Is there more to it?

Edit: a few more citations (still rather vague):

Many of Be's engineers moved on to a company called Danger, the company behind the Sidekick. When Danger founder Andy Rubin left the company in 2003 to found Android,[...] many of those developers went with them. (http://www.slideshare.net/newsworthy2457/this-os-almost-made...)

As for Android, Andy Rubin, the founder of Android inc and current head of Android at Google, also worked at Danger, a company where several Be employees such as Baron Arnold ended up. The Kin project, which largely inspired the UI of Windows Phone 7, was created by Danger after it became part of Microsoft. Unfortunately after Microsoft axed the OS Danger was working on, Project Pink, and the Kin was a dismal failure, nearly all of the Danger employees left Microsoft (including of course Andy Rubin), leaving little if any shipped code behind. (http://forums.sonicretro.org/index.php?showtopic=25221) (Not sure if calling Rubin "the founder" is misleading since they were 4 co-founders.)

Edit 2:

Danger were made up with more than just ex-Apple employees. A number of the engineers from Be Inc ended up there (Ficus Kirkpatrick, for example, and Baron Arnold also) and Danger was the genesis from which Android was born. (http://www.osnews.com/comments/27498?view=flat&threshold=0&s...) (Not providing details on what influence Danger had on Android other than Rubin, either.)

Re:Multithreaded toolkits: A failed dream? (2004) by dnautics on Monday November 02, 2015 @01:40PM (#10493987)
Romain Guy and Dianne Hackborn were both be engineers that are responsible for the intents model in android. I think. .
Re:Multithreaded toolkits: A failed dream? (2004) by dnautics on Monday November 02, 2015 @01:37PM (#10493957)
Right but that's the developer's fault for not understanding how to do multithreading correctly.