That's the reason I sigh :smile: I remember asking about packaged apps in the first Chrome Dev Summit. You told me they weren't the future, but Chrome would have to circle back around. Chrome leadership and FF leadership, on the other hand, were in love with packaged apps.
"packaged apps denied them" is not about people. I meant that people inside of Google who believed in SW has a hard time arguing against packaged apps internally when the other WebOSes were publicly saying the web is incapable and we need packaged apps to go fast.
-
-
OMG...the politics were brutal. We started w/ SWs because it was the thing that didn't require a UI fight -- it was "just web tech". It was only when Mike Tsao grokked the shape of the future that we were able to move; huge props to him for that.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
We needed offline support (but app cache was a nightmare, we tried and "shipped" at jsconf 2012 FxOS with appcache'd apps) and code signing to open access to some apis. To this day, the only hope is web packages for code signing + real urls afaik.
-
AppCache was a known nightmare in 2012. A bunch of us ran for TAG to fix it, and advocated for (and worked on) Service Worker. We could have used strong support from FFOS (for arguments w/ other browsers), but now I'm repeating myself.
-
I think Jonas had a proposal to replace appcache at the time (not SW though).
-
I spoke with Jonas at the time. His proposal was a new declarative manifest. I mentioned it in my 2013 post on SW: http://yehudakatz.com/2013/05/21/extend-the-web-forward/ … We really, really needed a primitive to avoid locking the web into another round of mistakes.
-
Relevant quote: "Something like Jonas Sicking's app cache manifest is a great companion proposal, giving us a nice starting point for a high-level API. But this time if the high-level API doesn't work, we can fix it by using the low-level API to tweak and improve the manifest."
End of conversation
New conversation -
-
-
(because that was exactly the same argument packaged apps proponents were making inside of Google, so they felt validated)
-
yeah, this was mostly an implementation issue badly mistaken as a fundamental issue. SW and appcache not fast enough + need to preload apps on a phone.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.