New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chat about dynamic import guards, asset references, and caching complications #5
Comments
Time is Thursday, December 19
via hangouts If anyone else wants to join, respond here. Will try to record. |
I'd like to join |
Can someone post the new link? :-) |
Sorry for my crap network connection. Thanks for bearing with me. I'm sure I missed a lot, but to capture some points discussed:
@ljharb You were saying something about my not having gotten committee-wide signoff on the appropriateness of brand checks for something related to this proposal. I didn't catch that. What was that case that I need to make? |
@mikesamuel to clarify :-) bradley mentioned past committee pushback on the concept of brand checks, and i'd clarified that the pushback was about coding in a nominal style (as opposed to a duck-typing/interface-checking style), and thus that pushback didn't likely apply to this proposal. What I was talking about more broadly was that it seems like these small pieces (that will be pieced together for TT) only sometimes make sense in isolation, and so for all of them to make sense, it might be more productive to find a simple way of teaching the committee how to understand TT as a whole - an understanding I personally still lack. |
@ljharb Thanks for explaining. Attending remotely, I have a hard time telling whether I'm only getting questions from the usual suspects because everyone else feels similarly or has checked out. @engelsdamien suggested a TT-background preso for next meeting. I'll see that it directly addresses how the branding enables the claims we think important. |
Will post time once we've agreement and recording of call post.
Scope for discussion is tentatively issue #3 and #4.
The text was updated successfully, but these errors were encountered: