Which practices in frameworks combined with which tools reduce (or eliminate) the cost of unused code? Which tools could we be building? Which asynchronous programming models help to delay the cost of code to the point where it's being used?
-
Show this thread
-
What different kinds of users are there and what size/CPU budgets do those users have?
1 reply 0 retweets 6 likesShow this thread -
As
@slightlylate said: "This will mean that many popular tools are relegated to prototyping. That’s OK." Rather than "disqualifying" frameworks for all uses, could figure out what use-cases a particular environment is useful for?1 reply 0 retweets 5 likesShow this thread -
Can we, as framework authors, do a better job of communicating which personas are appropriate for our frameworks, using quantitative measures that the community agrees on broadly?
2 replies 1 retweet 12 likesShow this thread -
Any analysis that lives or dies based "how many bytes is in a <Framework X> hello world" is a completely useless analysis that does nothing to promote the kinds of questions we really need to be asking.
2 replies 4 retweets 27 likesShow this thread -
Replying to @wycats
Right. I'm very much focused on end-to-end and how teams can adopt budgets to help them put tools in a more realistic perspective.
2 replies 0 retweets 4 likes -
Replying to @slightlylate @wycats
It's impossible to know if anything is "too big" or "too small" if it's going to be blended and whipped with webpack and browserify in a hard-to-reason-about way.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @wycats
This is why I've repeatedly asked frameworks to do exactly what you're saying: outline the situations where your framework will be under-budget (and, if possible, where it won't).
1 reply 0 retweets 0 likes -
Replying to @slightlylate
I think what we could really use from browsers (and especially Chrome, which has a fire in its belly about this stuff), is how different characteristics affect different scenarios.
1 reply 0 retweets 0 likes -
Replying to @wycats @slightlylate
I also think that assuming that every app is a content app targeting emerging markets is so far from the lived experience of many developers that this entire conversation goes over their heads.
1 reply 0 retweets 3 likes
Protip: these concerns are relevant, but at different magnitudes, in all markets. But only focusing on the markets with the most constraints makes many people think "why does this matter to me" and moralizing doesn't cause people to pay attention.
-
-
Replying to @wycats @slightlylate
I can't tell you how many people have asked me "why is Ember focusing on performance? Performance has never been an issue for me or my customers?" It's important that those of us who care about performance learn how to talk to all users in terms that resonate.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.