1) Yes. A lot better.
2) Because of the way both solutions are architected. Appcache uses
many many cross-process calls, packaged does not. cjones said that at
the beginning of the project they had to make a choice between fixing
appcache and doing packaged, and they chose doing packaged. I only
found out about this last week.
3) Not sure. We're obviously not fixing it for b2g v1... Because of the
way cjones has talked about it, I assume there are fundamental
architectural flaws or something, or I assume they just would have
fixed it instead of replacing it.
Personally I would like to know the real reason it is hard to fix
appcache, because appcache would be a hell of a lot more convenient
than packaging the third party apps, but we need all the performance
help we can get.
On Wed Dec 5 15:52:12 2012, Dietrich Ayala wrote:
I keep hearing statements like "Any real app should switch to packaged, because
performance is far better".
1) Is this true? And how much better?
2) Why?
3) What's the Web platform plan for fixing this? Is there one?
Thanks!
Dietrich
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
