On this bridge you're always going to have someone occupying open space, but you can still maintain 5 seconds of visible leading distance. Alas, a lot of drivers on this stretch of freeway are insane.
Torque clockwise to lean more toward the left. Torque counter-clockwise to lean more toward the right. The bike follows a radius proportional to its lean angle.
In my own case, having a single toddler is about a 20% increase in expenses, and that's not even accounting for saving for college, or how much it would cost if we wanted more space. It's easy to imagine being relatively comfortable in the Bay Area but not feeling financially comfortable about having kids.
$15K/month of income only goes so far, that's the point of the article.
The math without a child isn't so bad. Take out $5K for taxes, $3K for rent, $3K for food/utilities/car/etc. If they're lucky to not have other non-discretionary expenses hanging over their heads and are frugal, then yeah, that's $4K/month leftover for spending, savings, etc.
How far does $4K/month go with a child? Well, first, the mom is very likely to face a disruption in income and/or income growth. Second, childcare will be necessary in order to continue bringing in dual income. That could easily run $2K/month. Third, they will have to either remain packed into an "affordable" 1BR apartment, or find more housing at some cost (either money or commute time). Fourth, for many people, the notion of starting a family is an expectation of multiple children.
People can and do make it work, but it's not easy, and at these tight margins any sort of disruption can spell disaster. That's why people who are doing ok without children can still feel like their financial position is too weak to support a family.
This is no longer the case. Now you instantiate a go module wherever you want by running “go mod init” (which just produces a trivial text file). Each module’s dependencies are now well encapsulated. There’s no longer a need for a messy globally shared GOPATH space.
In my codebase at work there are a few cases where code is (poorly duplicated) that would benefit from a proper generic solution. But I don’t expect go2 to significantly reduce our codebase size, even if we replaced the aforementioned components.
I agree that some form of static typing is critical to scale a codebase, or an ecosystem. Let’s also not forget the importance of a packaging system with robust version management. Go modules and proxy.golang.org are also critical to Go’s success at (code) scale.
Go makes arbitrarily large codebases feasible. I find Python to be exponentially more painful as codebase size increases. For personal projects this is fine, but for industrial use cases Go has a significant competitive advantage.
I'm not sure you're arguing in good faith. I suggested no such thing about pedophilia, and numerous articles about research into the cycle of poverty and crime are trivial to look up (e.g. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7234816/).
Should you hire someone with a criminal record? Hiring decisions are extremely contextual. Your examples are nowhere near specific enough to address without generalization. But consider that people who have committed white-collar crimes sometimes are hired for their security expertise (e.g. Kevin Mitnick), and I see nothing wrong with that.
Much of crime is driven by poverty. If the consequence of poverty-driven crime is more poverty, then this negative feedback loop turns society into an incarceral state.
The most significant reason why (manufacturing) jobs no longer exist in the US is our exorbitant privilege of being the global reserve currency. It has nothing to do with labor laws or taxes.
Sure, you don't have to go out of your way to challenge your type system, but it still means that you're a single typo away from sending your compiler and yourself on a wild goose chase.