Re: Executing script-inserted external scripts in insertion order

>> Regardless of whether the script is inserted by the parser or by another
>> script, if you want a set of scripts to behave "asynchronous" (that is,
>> execute each in the set "as soon as possible") then you set `async=true`. If
>> you want them to behave "non-asynchronous" (that is, execute each in
>> insertion order), you set `async=false`.
>> 
>> That seems quite logical and defendable to me, and is far more intuitive to
>> me than introducing other attributes. What's *not* logical to me is that
>> script-inserted scripts currently ASSUME `async=true` behavior (but yet do
>> NOT expose such a property), and moreover give no way to override that
>> behavior.
> 
> Legacy behavior is often illogical.
> 
> As well as being declarative, the waitFor proposal also supports more
> use cases than the other proposal because it doesn't force a linear
> dependency graph.

It seems like a lot of additional complexity, and it still doesn't fix unintuitive behavior of async that Kyle explained.

-- 
regards, Kornel

Received on Monday, 18 October 2010 09:02:01 UTC