Aren't macros, especially proc macros these days in Rust having the same effect? Personally I feel like this is a tradeoff every language has to play with: you either limit to a special way of writing, or adding some sort of ad-hoc system that enables rewriting syntax and even to a degree, semantics.
114 unarmed Americans were killed by police in 2019. [1]
While any number other than zero is unacceptable, that is also 0.000035% of the US population, or a one in 2.8 million chance. If you are African-American, that goes up to a one in 1.5 million chance – also unacceptable, while at the same time a vanishingly rare occurrence.
You are 328 times – that's 32,800% – more likely to die of suicide than to be killed by police. You are 733 times more likely to die of diabetes than you are to be killed by police.
Police reform in the US is absolutely needed. But suicide prevention and healthy eating are objectively much greater problems that need solving, and are at very least worth as much of "a talk" with developing children.
[1] https://mappingpoliceviolence.org/nationaltrends [2] https://www.cdc.gov/nchs/fastats/deaths.htm
It seems like there is more than usual IPOs this August compared to previous years: https://www.nasdaq.com/market-activity/ipos
It's more like we're in the equivalent of the first or second inning of the post great recession recovery now.
This recession isn't broad, it's unusual in its disjointed hit. It's primarily hammering lower income labor and specific types of small businesses. 40% of low income households lost jobs just in the March and April shutdown. That's where most of the job damage was at:
CNBC "Households with income below $40,000 were hit hardest by the coronavirus pandemic. Almost 40% were laid off or furloughed by early April, according to the Federal Reserve."
Jobs in the top 2/3 have largely been unscathed, which is why the broad housing market continues humming along in most regards (whereas housing got smashed in every way in the great recession). It's also why hiring has been so ferocious and unemployment has recovered dramatically faster than during the great recession; it's specifically because the context isn't all encompassing. The great recession didn't spare the middle class and higher income groups nearly so much, it was a very broad recession.
Which all makes sense, this wasn't a normal recession, it was a temporary forced shutdown of some parts of the economy due to a pandemic (further, not all of the economy was shuttered during the second quarter, the majority of the economy kept functioning throughout the pandemic).
When a machine issues a ``docker build`` command, the program reads the relevant dockerfile to check for any base images that need to be pulled (a la "FROM:")
These base images are identified based on the image repository, image name, and image tag. The first thing docker does is it checks its local registry and tries to find a match for the base image the docker build is requesting. If a matching image is located in the local registry, it uses that one in lieu of downloading the image.
This is significant - if your organization only uses a few dozen base images from DockerHub, those images will only be downloaded by each build node _once_, then never again.
Many docker users erroneously believe that if their Dockerfile requests a "latest" tagged image, docker build will always download the newest version of the image. However, the "latest" tag is literally just a tag, it doesn't have any special functionality built in. If the docker build command finds an image tagged "latest" in the local registry, it stops there.
The only way to get docker build to always use the "actual latest" version of the base image is to add the "--pull" parameter to the docker build command. This arg will tell docker build to check the repository remote to see if the SHA hash of the image tagged "latest" has changed, and if so, re-download and use it. In the absolute worst case, this means each build node will pull 1 copy of each base image when the base image is updated. So unless you use 200 different base images that all have updates deployed to Dockerhub each and every day, you are fine.
Stoicism teaches us that all negative emotion is rooted in a lack of understanding. So when someone says they don't want to raise the minimum wage, or doesn't want universal healthcare, or whatever... it's helpful not to have that knee jerk reaction of "This person is bad and wants people to suffer." That's almost never the case.
Second, even if we granted the premise that UHC leads to less healthcare innovation, this doesn't mean that there's "infinite harm" in to people in the future. Unless you're claiming you have a crystal ball, there is absolute 0 epistemic basis on which to make this claim. For all we know, not having UHC leads to nuclear war and we all die. Or, having UHC leads to the singularity. Etc.
Third, even if we grant that there's an innovation advantage to for-profit medicine AND we grant that you can predict the future, that still doesn't mean that there's "infinite harm", precisely because "harm" is comparative. I would argue that we've picked most of the low-hanging fruit of human medicine and that the marginal utility produced by new treatments is far outweighed by the human suffering of our for-profit system.
Affine types in Rust are anything with move semantics; for example you can create a method that consumes itself like this:
Obviously it's not part of the type system itself, but doesn't the must_use attr get pretty close?