Thoughts
The real problem with time as a resource is that your time budget is determined by your architecture (instead of the other way around).
One of the interesting takeaways from *High Conflict* was that sometimes you’ll have a group with shared values and objectives. And there
will be some disagreement within the group about how to approach a particular issue. And in that moment, describing the issue by slicing the group in half and referring to “those on this side” vs “those on that side” is incorrect and harmful. That is, the binary framing does not exist as soon as there is a problem, the binary framing is actively created. And the binary framing itself is harmful. This is important because a lot of people that are interested in addressing the problem of political polarization approach it with an implicit binary framing.
The reason I'm talking about this is that people are talking about this and the reason that people are talking about this is because
GitHub's backend is falling over so people are taking the opportunity to dump on the fact that GitHub has 14MB of JavaScript. And I'm like. That's not why their backend is falling over. And these commenters are like "it's all connected to the fact that they're incompetent engineers" and I don't think it is.
It just ticks me off that we're on year 10 of "JavaScript uses a lot of memory and pages are so bloated."
"If throttle my browser to 3G speeds and disable caching then it takes GitHub 20 seconds to load."
Don't do that.
"Developers should combine their CSS and JS into one file to save requests"
What are you talking about. Have you heard of this technology from 2015, it's called HTTP/2?
"This page takes 62MB of RAM on my computer with 48GB of RAM"
Oh the horror. Whatever will we do.
Hey new season, let's keep the depression seasonal and not do any depression posting this season okay?