I have concerns of making such major changes implicitly in android.
For the developers who follow this thread they are safe, what about
the thousands of developers who wont be reading this thread? Any
possibility of making such major changes compile failures or deprecate
old api and create new api with forced selection of parallel/serial
executor.

Easier to fix failures at app compile time for all developers, not so
easy for each developer who is depending on current parallel asynctask
behavior to google search for related asynctask slowness problems and
find the cause of this six months down the road when 3.0+ is the
default android on majority of devices?

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to