Yup. And we had to ship/get users to get apps. Hence many shortcuts we didn’t like
-
-
FFOS started in 2011. PWA were far from being a thing then.
-
@slightlylate,@annevk and I were pitching them to anyone who would listen *at the time*. I spoke with FFOS folks at the first Chrome Dev Summit.@annevk and I commiserated *at the time*. -
I wrote this in 2013, after running for TAG in 2012 overtly to fix the app cache mess: http://yehudakatz.com/2013/05/21/extend-the-web-forward/ … I wrote the Extensible Web Manifesto in 2013 in part to push back against the widely held belief that packaged apps were the only way forward.
-
FFOS engineers were aware of the PWA vision at the time, and just didn't believe it was worth prioritizing. Full stop.
-
You're laughable. full stop.
-
I'm laughable because...
-
because you pretend to know what we believed in, while it's clearly not the case. Your whole view of what happened in FFOS is an alternate reality
-
I was a Mozillian (such as the term makes sense) at the time, and have worked closely with Mozilla leaders and standards folks on web components, service worker, asm.js/wasm for years. More recently, I have attended literally every Mozilla all-hands.
- 2 more replies
New conversation -
-
-
This is a story I'd have fought for, including pitching clients and managers.
-
Some of us fought. It was ugly, and we lost.
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.