Yep, that or some RPC type setup. XPC on macOS for instance. Isolate the extensions into their own processes, and keep the database on a thread model. Allows you to strike a balance between fast and safe.
Note that Rails was built as a framework for making blogs, I'm having trouble understanding what 78,000 lines of ruby in the context of a Rails blog could ... do.
I'm sure there's some powerful ugly stuff in Office but in a good code that's calcified kind of way. It got that way over like 30 years of releasing to the public across platforms, not over a weekend.
I'd be surprised if microsoft.com is shipping their entire test suite unminified and their back-end posting rich text editor with index.html (with two title tags in the head) and rendering the entire DOM for desktop and mobile regardless of your platform.
I'm not critiquing Garry or the site. I think it's great people are using AI to build things that bring them joy, or that they find useful. I certainly do.
I am opposed to the idea that we've decided to go back to measuring work in terms of lines of code. It has always been the worst metric on earth as a proxy for productivity. Every line is a liability, and it always was. AI has not changed that, if anything it's amplifying it.
The best PRs remove code, not add, and the only companies that seem to have exponentially grown their revenues in line with AI-generated LOC are OpenAI and Anthropic. Everyone else seems to be rummaging around for an ROI.
If I wanted someone taking a look at all the stuff in my home, I'd just pay a cleaner here instead of one behind a desk in what I assume is a low-labor-cost locale. For $50/hr I can have them come in every day for 160 days, and they can manage stairs.
... did you think that's what I was implying? I'm not even American my guy. I was adding clarification because the commenter I responded to claimed they had to be a US citizen to ride.
Companies over-hired in 2021 assuming that their COVID metrics explosion would persist, but they didn't. We saw low attrition for years, and a low-hire/low-fire employment environment. Then the time came to pay the piper.
The tech everything's-hypergrowth era is, for now, over. Most of the low-hanging fruit that we've collected for the last 20 years of bull market (putting tech into every business) is gone, and companies hired in advance of having the next business to overlay on their current ones. For many that didn't materialize.
One of the study authors, Ara, tweeted that they control for that by comparing early adopters against firms who haven't yet, and built like-for-like control groups with similar pre-adoption growth trajectories. (This is a rough quote).
Also, note, everyone assumed it was going to be limited to citizens, but that's not what the government said. They put it under ITAR/EAR's US person definition which includes citizens, permanent residents, refugees and asylees. Basically only visa holders in the US were banned, and of course, people in foreign countries.
At least the top 4, unclear about the 5th, are strongly associated with obesity. That would make someone high-risk and testing potentially warranted in like 70% of the population. Asymptomatic and low-risk is what I said. The incidence of hypertension is so high in the general population it’s almost always statistically supported (even though basically every doctors office takes it wrong, even cardiologists, amazingly).
On the other end of the spectrum, what doesn’t make sense is testing a random person off the street for Ebola. The prevalence approaches zero and symptoms are fairly noticeable, so any positive test is definitely wrong.
Most diseases are in between and have to be evaluated case by case, not buckshot.
You may be particularly interested to hear that there’s little evidence to support regular checkups in most adults beyond blood pressure testing and cervical cytology.
> Given the lack of favorable evidence and the potential adverse effect, primary care providers should consider the fact that general health checks, beyond the screening interventions shown to have benefit, likely have little or no effect on important health outcomes. Some of the interventions with demonstrated benefit have sufficiently large effects that a uniform application is warranted (blood pressure measurement and cervical cytology screening). In others, the trade‑off between benefits and harms is so close that patients should be involved in fully shared decision making regarding their participation (breast and colon cancer screening).
And blood pressure is especially pernicious, basically every doctors office measures it wrong so the results aren’t particularly useful. Many use the wrong size cuff for example, or don’t give people time to relax before a reading. A ton of people have white coat hypertension, high BP only because they’re in a doctors office.
You’re dealing with populations here. Literally the odds of a positive being false would be over 90%. Much higher in the more rare conditions. I’m not exaggerating. That means every almost every follow up you do is a waste of time, money and limited resources, denying care to those who need it. Including you when you actually do need it. It also exposes you to the risks of unnecessary follow-ups like infection. Your expected outcome is worse this way.
The chance a positive is real is so low you may as well just point to a body part and get it biopsied.
A positive from this kind of test is statistically meaningless.
There’s a very good reason we don’t test asymptomatic people in low incidence populations. Basically all positives are false positives when you do that, no matter how accurate the test is.
When you’re testing healthy randos for everything the odds of a positive being false have so many 9s it would make an SRE weep.
Unless this is accurate to a degree previously unheard of in medical science it’s a boondoggle, and I can’t help but notice there’s no mention of accuracy.
If you’re UV sensitive and at a higher risk then you’re already in a high incidence population making the tests valuable statistically speaking. That test is wildly more accurate for you than it would be for me, and even still you’ve been the unfortunate recipient of many false positives. There’s no reason for me or most people to do that since practically 99% or more of the positive tests would be wrong.
Biopsies are expensive, waste time, hospital resources and carry risks of infection and scarring that do not net out positively for people who aren’t in your risk group.
Getting a totally random positive doesn’t put you into a higher incidence category so whatever follow up test you take will be just as inaccurate as the first one.
The reason to avoid them is the tests would be a waste of time, statistically, and expose you to a bad risk-reward profile.
If you knew apriori 99% of the positive tests are false positive why are you taking the test?
It’s literally just math. Sometimes the right thing for you on average is to do nothing, which feels bad, but it’s still the right thing to do.
False positives are important because of Bayes theorem. Even a test that’s 99% sensitive in a high incidence population can be indistinguishable from noise in a low incidence population.
If it has a 1% false positive rate but the incidence is 1%, the vast majority of the positives are false. Then you have to deal with the consequences, including invasive procedures for further diagnosis.
If you’re searching for tens or hundreds of low incidence conditions in the general population at a time it’s absolutely worthless because basically every positive is a false positive. At that point save the scan fee, spin a wheel of body parts and go get a biopsy of that.
This is why doctors are confused why companies are offering periodic full body scans in normal people. They only test people who are high risk or symptomatic to confirm a suspected diagnosis. That extra signal is what makes the test useful.
Go down to the medical diagnosis section for a worked example.
Regarding cancers every human has all sorts of weird lumps that are generally meaningless.
In order for this to not be a boondoggle it would have to be spectacularly accurate to a degree previously unheard of. Just from a statistics perspective.
I looked into it some more and it's actually worse.
For static or thread storage, in C11 and later, ={0} will guarantee padding is zeroed. For automatic storage, per C11 6.7.9, only subobjects are required to be zeroed. Padding is not. [1]
In C23 initializing with ={} will give you zeroed padding, initializing with ={0} will not.