> Yes, i used AI to resort it,
It may be not "generated", as in it's a true story, but the writing is AI.
2,813 karma · joined August 16, 2022
> Yes, i used AI to resort it,
It may be not "generated", as in it's a true story, but the writing is AI.
Error is not binary, it's a statistic. Even perfectly trained pilots/programmers do make errors depending on the situation. What you should ask is what the error chance is, and if it acceptable.
As the accident report shows, the exact same pitot tube failure happened at least 15 times and recovered by the pilots. The 16th time, it killed more than two hundred people. Do you think a 1/16 chance of dying is appropriate in modern aviation safety?
I thought you were joking, unfortunately you weren't. Money really has no taste.
Does it mean botting there is just pay-to-win?
In those case you already lose time, but in the future you would also lose money.
Unfortunately you don't know how a company will react before submitting, especially if it's a small one.
Yes I know it comes from pirating/torrenting/scrapping. Are you saying you acknowledge your IPs come from malware, and that is OK because OpenAI is shady too?
> This is not a complaint about volunteer maintainers. It is simply one of the ambient risks of building serious systems on a smaller ecosystem.
And so instead of paying the lib authors who already have domain expertise and know their codebase, they chose to rewrite it from scratch/fork without contributing back. So classic.
> It’s probably the core reason developers choose GitHub as their main git forge. I get it. It does have it’s advantages of giving a better experience for reviewing a set of changes. Initially. But what if I told you there was a time when submitting email-based patches was the standard for version control?
The author explains well how you can bear with patches, but not why patches were chosen in the first place. What advantages do they have over PR? I see none, and I won't lose my precious time working-around an inferior process to Github's already subpar PR one.
This has downsides of course, moving further into the "everything rot so fast these days" trope, but we will in a adversarial world where the threat is constantly evolving.
Tomorrow (today) the servers and repo won't be scanned by scripts anymore but by increasingly capable models with knowledge about more security issues than many searchers.
Those are pervasive in any old and large project but in my experience especially so in compilers.
Is that ‘fair’ for everyone? No! Because no everyone has access to the same level of information. But no one forces you to bet either.
This is yet again a very US-centric view where you assume people are living in house with a garage.
Now for those wondering who would fork and maintain it for free, that is more of a critic of FOSS in general.