It's a huge issue, and a source of great technical inequity. The assumption that everyone carries a $500+ device does much to embed and exascerbate these biases.
-
-
Replying to @slightlylate @kragen and
I don't blame the React team for anything more than the usual sins of wealth and privilege. Is it grotesque bordering on obscene? Absolutely. Will FB ever do anything more than duck responsibility for pervasively poor results? TROLOLOLOLOL
3 replies 1 retweet 10 likes -
I think wealth and privilege are, if not exactly virtues, at least good things that everyone should have more of. The sin is using them thoughtlessly. But we can't expect every hacker to quit their well-paying job and move to a third-world country for decades
1 reply 1 retweet 1 like -
Replying to @bahstgwamt @kragen and
They're relative measures. Everyone should have a higher standard of living. Higher relative weather?

3 replies 0 retweets 1 like -
Replying to @slightlylate @kragen and
I like this conversation. The perspective I would add is that of course white dudes in wealthy nations aren't going to solve far away problems for people without wealth. That's not an expectation any of us should have.
1 reply 0 retweets 2 likes -
Replying to @polotek @slightlylate and
Instead I think there are a couple of issues that keep these people from solving their own problems (the preferred solution IMO). One is the pressure to centralize the market, e.g. the bigs monopolize and suffocate upstarts.
2 replies 0 retweets 2 likes -
Replying to @polotek @slightlylate and
The other is what *I think*
@slightlylate is kind of getting at. Hardware is still expensive and also controlled by the bigs. The bigs leverage that to also peddle their monstrous frameworks, and don't support a wider OSS community in solving more localized problems.1 reply 0 retweets 4 likes -
I observe as much "well, <BigCo> uses X..." in NBU markets as I do here, usually coupled with an ignorance of *actual* BigCo practice.
2 replies 0 retweets 1 like -
Replying to @slightlylate @polotek and
BigCos have staffed up perf teams and custom infrastructure to support minimal bundle generation (MSS, Big Pipe, etc.). Bundle size regressions can cause a presubmit to fail.
1 reply 0 retweets 3 likes -
Replying to @slightlylate @polotek and
The big products gate marginal feature rollout on perf and many have strict latency budgets
1 reply 0 retweets 2 likes
Nobody working on a consumer product at Google experiences Closure or Polymer or Angular or GWT the way external developers do. The layers of abstraction and tooling mandated to get decent perf prevent it
-
-
Replying to @slightlylate @polotek and
This doesn't keep a lot of these products from being poor mobile experiences, but the mobile question is also approached differently: when you can afford to make multiple versions, you often do.
2 replies 0 retweets 1 like -
Replying to @slightlylate @polotek and
Meanwhile, I see smaller firms pervasively misread the BigCo OSS framework marketing and fail to adopt minimum necessary support infra and tooling. The results are predictably poor, and they hurt those without money most.
1 reply 0 retweets 3 likes - 9 more replies
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.