On Mon, Feb 23, 2015 at 4:26 PM, Jonas Sicking wrote:
> On Mon, Feb 23, 2015 at 4:01 PM, Robert O'Callahan
> wrote:
>> On Tue, Feb 24, 2015 at 12:09 PM, Jonas Sicking wrote:
>>>
>>> I think this would fall over more often than not.
>>>
>>> Most developers will not write their code to be resilie
On Mon, Feb 23, 2015 at 4:01 PM, Robert O'Callahan wrote:
> On Tue, Feb 24, 2015 at 12:09 PM, Jonas Sicking wrote:
>>
>> I think this would fall over more often than not.
>>
>> Most developers will not write their code to be resilient in the face
>> of being suspended for extended periods of time
> I think this would fall over more often than not.
>
> Most developers will not write their code to be resilient in the face
> of being suspended for extended periods of time. Upon reopening they
> would likely display error dialogs, or updated version of whatever was
> saved.
>
> In fact, I wou
On Tue, Feb 24, 2015 at 12:09 PM, Jonas Sicking wrote:
> I think this would fall over more often than not.
>
> Most developers will not write their code to be resilient in the face
> of being suspended for extended periods of time. Upon reopening they
> would likely display error dialogs, or upda
Le 24 févr. 2015 à 08:02, Robert O'Callahan a écrit :
> Also, there is a way to get "save for later viewing" to work with complex
> apps: serialize all the application state --- DOM, CSS, JS heap, workers,
> etc --- and revive it later, possibly in a jail that blocks it from
> accessing the netwo
On Mon, Feb 23, 2015 at 3:02 PM, Robert O'Callahan wrote:
> On Tue, Feb 24, 2015 at 10:57 AM, Gordon Brander
> wrote:
>>
>> It's funny: I have come to the opposite conclusion for the same reason.
>>
>> The Good: getting 60fps interactions and animations in web apps using a
>> proven approach (UI
On Tue, Feb 24, 2015 at 10:57 AM, Gordon Brander
wrote:
> It’s funny: I have come to the opposite conclusion for the same reason.
>
> The Good: getting 60fps interactions and animations in web apps using a
> proven approach (UI and interaction thread).
> The Ideal: also automatically serializing
It’s funny: I have come to the opposite conclusion for the same reason.
The Good: getting 60fps interactions and animations in web apps using a proven
approach (UI and interaction thread).
The Ideal: also automatically serializing those apps for offline use.
While I very much want the ideal to
On Mon, Feb 23, 2015 at 12:07 PM, Robert O'Callahan
wrote:
> On Tue, Feb 24, 2015 at 8:56 AM, Jonas Sicking wrote:
>>
>> On Mon, Feb 23, 2015 at 10:56 AM, Gavin Sharp
>> wrote:
>> > What does it mean to "save your for later viewing"?
>>
>> In gmail it would mean saving the set of emails that yo
On Tue, Feb 24, 2015 at 8:56 AM, Jonas Sicking wrote:
> On Mon, Feb 23, 2015 at 10:56 AM, Gavin Sharp
> wrote:
> > What does it mean to "save your for later viewing"?
>
> In gmail it would mean saving the set of emails that you are currently
> looking at.
>
> For facebook it would mean the news
On Mon, Feb 23, 2015 at 11:56 AM, Jonas Sicking wrote:
> On Mon, Feb 23, 2015 at 10:56 AM, Gavin Sharp
> wrote:
> > What does it mean to "save your for later viewing"?
>
> In gmail it would mean saving the set of emails that you are currently
> looking at.
>
> For facebook it would mean the new
On Mon, Feb 23, 2015 at 10:56 AM, Gavin Sharp wrote:
> What does it mean to "save your for later viewing"?
In gmail it would mean saving the set of emails that you are currently
looking at.
For facebook it would mean the news-feed content that's currently on
the screen, or the event invitation
A couple thoughts from the perspective of a web app dev who has struggled with
this problem:
I get excited when I hear a proven solution with well-understood scope like
“animations and user interactions on the same thread”. I get nervous about
ambitious and unknown solutions (async DOM). The we
What does it mean to "save your for later viewing"?
I don't think there's a lot of overlap between sites that would use
the functionality roc is proposing, and sites that make sense to "save
for later viewing".
Gavin
On Mon, Feb 23, 2015 at 10:36 AM, Jonas Sicking wrote:
> On Sun, Feb 22, 2015
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/20/2015 09:12 PM, Jonas Sicking wrote:
> On Fri, Feb 20, 2015 at 8:11 AM, Julien Wajsberg
> wrote:
>> Le 20/02/2015 04:25, Robert O'Callahan a écrit :
>>> On Fri, Feb 20, 2015 at 4:02 PM, James Long
>>> wrote:
>>>
>>> Personally I think what w
On Fri, Feb 20, 2015 at 8:11 AM, Julien Wajsberg wrote:
> Le 20/02/2015 04:25, Robert O'Callahan a écrit :
>> On Fri, Feb 20, 2015 at 4:02 PM, James Long wrote:
>>
>> Personally I think what we *really* need to be working on is making
>> all of the DOM APIs asynchronous. That's what Servo
Le 20/02/2015 04:25, Robert O'Callahan a écrit :
> On Fri, Feb 20, 2015 at 4:02 PM, James Long wrote:
>
> Personally I think what we *really* need to be working on is making
> all of the DOM APIs asynchronous. That's what Servo needs anyway.
> That's a step in the right direction for #
On Fri, Feb 20, 2015 at 3:20 AM, Jonas Sicking wrote:
> On Thu, Feb 19, 2015 at 7:11 PM, James Long wrote:
>> Note however that people in the native app world believe that it's
>> very important that whatever applies the animations is run on the same
>> thread that handles input. Otherwise it's v
On Thu, Feb 19, 2015 at 7:11 PM, James Long wrote:
> Note however that people in the native app world believe that it's
> very important that whatever applies the animations is run on the same
> thread that handles input. Otherwise it's very easy for animations to
> get out-of-sync.
Does that mea
On Thu, Feb 19, 2015 at 10:25 PM, Robert O'Callahan
wrote:
> On Fri, Feb 20, 2015 at 4:02 PM, James Long wrote:
>
> Personally I think what we *really* need to be working on is making
> all of the DOM APIs asynchronous. That's what Servo needs anyway.
> That's a step in the right dire
On Fri, Feb 20, 2015 at 4:02 PM, James Long wrote:
Personally I think what we *really* need to be working on is making
all of the DOM APIs asynchronous. That's what Servo needs anyway.
That's a step in the right direction for #3, and we can see much more
we can get out of the main
Sorry, I may have missed the last part of your email where you say
that you could provide touch positions as input too. This would be
neat research and I'd like to see more details.
Note however that people in the native app world believe that it's
very important that whatever applies the animatio
I'm not heavily involved in platform work, so take my input as a
somewhat naïve outsider. I've been tracking this kind of stuff very
closely, especially after I got to play with react native.
The place where this is most important is mobile, and I don't think #2
is going to cut it. It's not just s
23 matches
Mail list logo
