There are 3.6M births per year in the US. If we assume a cost of 2B, then we get a cost of $555 in benefits per baby. That seems too low to fund a 4 week parental leave.
Another way of looking at it is the median wage of someone in their 30s is $65K. A month of parental leave at 67% wages is around $3.6K. Even assuming only one parent takes parental leave per 3.6M yearly births, that would be $13B.
Yet another way of looking at it: NYS has a parental leave program, which is funded by a payroll tax of 0.38%. There are ~10M workers in NYS, earning an average of 1,300 a week. Inflows into the parental leave insurance program are therefore around 2.5B, just for NYS.
Multiplexing would have a number of benefits. As you say, each client would only need a single connection regardless of the number of queries being sent. Resulting in:
On the client side, there is usually a local connection pool. When a burst of traffic comes in, the client needs to either wait for the pool to free up or establish a new connection, which adds latency. This latency hit wouldn’t occur with multiplexing.
With multiplexing, systems like pgbouncer would be unnecessary.
Also, even with a thread-per-connection, you can still quickly exhaust the servers resources when you have lots of connections because threads have a lot of overhead. Reducing the number of connections needed would greatly increase the number of clients that a database can serve.
While a thread-per-connection seems like an improvement, do you have any plans to allow query multiplexing over a single connection? That would be a huge improvement IMO.
> You may have heard that if you have an MTHFR variant, you should avoid folic acid and should take other types of folate, such as 5-MTHF. However, this is not true. People with an MTHFR gene variant can process all types of folate, including folic acid. Folic acid is the only type of folate shown to help prevent neural tube defects (NTDs).
Linking to a huge list of supplement guidelines, most of which cover labeling of nutrient content is not helpful. I did try to dig in, however, and found this:
> A qualified health claim is supported by less scientific evidence than an authorized health claim. FDA requires that qualified claims be accompanied by a disclaimer that explains the level of the scientific evidence supporting the relationship.
> Unlike authorized health claims, FDA does not issue regulations for qualified health claims.
That does seem to indicate supplement manufacturers have broad latitude to make claims provided they are disclosed as such.
1984 is a much better book. The writing is beautiful and the story is gripping. For that reason alone, it occupies a larger part of society’s psyche. I agree that many aspects of Brave New World were prescient, but 1984 isn’t entirely inaccurate either.
We were expanding our product to a new language that used non-ASCII code points. Part of the system involved invoking binaries using text as input.
Locally, everything worked great. Once deployed, we got corrupted text output. As soon as we SSH’d on to the server to inspect, everything started working again.
It turns out that SSH servers can modify the LANG environment variable. The default value on our servers didn’t support Unicode, but LANG was updated as soon as we connected via ssh. It was a head scratcher for sure.
I’m not going to pretend to be an expert here, but I remember a study that found gut bacteria composition predicted whether or not an individual was chocolate-craving or not in individuals eating identical diets: https://pubmed.ncbi.nlm.nih.gov/17929959
I don’t mean that expect should be used. But flags like —no-interactive are unnecessary. CLIs can just check `isatty == false` instead of requiring an explicit flag.
I also built a canvas-based, multiplayer product during the pandemic (ohyay).
The product was social-event focused (classes, festivals, etc.) so we focused on multiplayer audio-video experiences rather than general purpose browsing.
One of my favorite memories was when someone used our collaborative YouTube playback to set up a karaoke room. WebRTC added a little latency, but it was close enough to work.