The article mentions bronze production (thus indirectly mentioning copper and tin) not as a root cause, but rather a factor that spread the crisis from one region to another:
> What is clear is that once the collapse started, it was contagious, likely for two reasons: first that collapsing areas produced invading forces and refugee flows that destabilized their neighbors and second because as you will recall above, these states are interlinked and their rulers rely on trade to furnish the key military resource (bronze) as well as to acquire key prestige goods necessary to maintain the loyalty of the aristocracy.
> I design my code so that I always know which number will be larger than the other.
That’s good discipline, but with better tooling and languages such conditions could be enforced by the compiler such as with Dafny. But Dafny is overkill for those who only want to avoid underflow and overflow without verifying everything else about their program…
That’s what I mean when I lament the state of affairs for underflow. Subtracting numbers is such a basic operation, but for the tech stacks used by most teams it still requires a level of care to avoid errors or corruption. Our industry is building million line behemoth codebases but these basic operations still have to be designed around.
> Typically, in real algorithms, what you want is to not only know the delta, but also which number is larger.
I agree with you, and the article was more concerned about avoiding underflow than actually having a practical use for its various example idioms.
What I’d actually prefer is a guarantee that subtracting two (X) bit numbers results in an (X+1) bit number. A sort of compile-time-checked bignum implementation where the programmer never thinks about the integer sizes or which number is larger until the final step of a calculation. Obviously this gets wasteful when multiplying numbers several times. EDIT: and I’m referring to an abstraction of integer bit sizes in a programming language, I’m not expecting the instruction set or hardware to have arbitrary sized registers.
It’s pretty sad that after all these years, dealing with fixed size integers is still so complicated. Yes, many of the problems are specific to low level languages with undefined behaviour and numeric for loops. But the issue of subtracting two numbers and possibly having an underflow is both common and a bit absurd.
The code in the article for “safely” calculating the difference of two unsigned numbers, which is simpler than the equivalent for signed integers, is this little ritual:
> delta = max(x, y) - min(x, y);
Seriously??? Two function calls just for the difference of two numbers??
Why can’t such “safe” operations have some of the sweet syntactic sugar, and the underflow-rampant “ordinary” operations have the bitter medicine of ritual?
> Eventually someone important enough will force digital resales to become reality
Honest question: why? Why would anyone important enough to hold that power actually use it to force resales to exist? Who actually has the incentives to make this happen?
The problem of false advertising is resolved but the problem of consumer freedom remains. If all digital marketplaces for a particular art only offer rents, without any option to buy or any physical media to serve as an alternative, that would still be a problem even if the rents were presented honestly.
You could use separate tools for those tasks. JIRA/Bugzilla/etc. for issue tracking, Sublime Merge or equivalent for comparing a dev branch to a main branch, and CI/CD with Azure Pipelines or whatever the “modern” equivalent of Jenkins is.
That isn’t as convenient as an all-in-one tool, and might not be what the user you’re responding to is doing. But it’s doable.
With regards to interpreting the laws, I mostly agree with you, although I certainly haven’t delved as deep into the true meaning of law in society.
But I still don’t understand what you actually expect from maintainers of free and open source software. In prior comments you have used words like “empathy” but I’m wondering in more specific terms what you mean. What should be maintained, and what should be abondoned? What should stay stable and what should be updated?
I ask because when you say stuff like
> I am just deeply saddened how any attempt to suggest that there were and should still be some implied cultural norms regarding expectations
I’d feel very differently about that comment based on the “expectations” that are “implied”.
And perhaps your answers might help me out a bit, to be honest. There are plenty of times when I use an open source library and get annoyed by the decisions of upstream developers, but I often wonder if my annoyance should be directed at upstream at all, or at myself.
> I still really don’t understand what is so entitled about asking for a level of base empathy and care from maintainers.
> People now yell at you that their only obligation is whatever is spelled out in the license they attached to the code.
Let’s turn your implied question around: if a person wants to share code without any expectation of care and maintenance, what should they do? Is the entire concept bogus, and the developer should just keep the code to themselves forever? Or put a “DO NOT USE FOR YOUR BILLION DOLLAR COMPANY” in a README? What communication other than the license could reasonably be provided?
I think the person you’re responding to made a pretty good point that open-source is sometimes the passion of an unpaid 1-person “team” and sometimes the product of a VC-funded attempt to buy goodwill. The idea that asking for more from maintainers is entitled is clearly suitable for the former case but not the latter. Now that Bun has been bought out perhaps they are more deserving of scrutiny.
> Contributions from people from identities known and consistent before the AI-age are fine
Unfortunately, according to the article:
> Giovannini has participated in discussions at least as far back as 2018, and his activity in Bugzilla goes back to at least 2016. He does not appear to have been a particularly active contributor to the project, but his involvement clearly predates the agentic AI era. Whether his account is now being operated by a human attacker, an agentic AI, or a mix of both, it has a legitimate history prior to its recent activity.
So people would have to not only verify the age of Giovanni’s accounts, but judge whether his behaviour was normal.
Near the top, the page claims it’s about learning the difference between checking, saving and money market accounts.
In the entire linked article, where is the explanation for what a savings account is? Most of the early paragraphs are just waffling about how “Types of Accounts” are important. I’m pretty sure I read the phrase “money is emotional” before even getting to any description of any type of account. The word “savings” almost never appears and none of the instances seemed to define a savings account.
Honestly, is this content written by AI? In my opinion it’s acceptable to use AI to replace the boilerplate HTML, JavaScript and CSS of your site. But using AI for the actual writing risks turning your “educational tool” into a tool for misinformation.
EDIT: according to Pangram, 100% of the first two paragraphs are AI generated. Which is not a surprise at all, I don’t see how a human tasked with describing types of bank accounts would struggle this hard.
Point #5 seems near impossible and even furthermore undesirable. Unless we are envisioning an application with all the characteristics of a web browser, but using different layout languages.
When I first saw the 26k changes statistic I was shocked. It made me think a large chunk of code running on people’s machines was AI-generated.
But the knowledge that a lot of the changes might be testsuite changes made me change my perspective. If for instance 25k of the changes were test changes and only 1k of the changes actually affected the .so and other artifacts used downstream, that would be a lot less dramatic.
I haven’t reviewed the code, only the messages, so I don’t know if these changes were removing or adding test cases. And there are a minority of Claude-assisted changes which are not listed as tests.
> What is clear is that once the collapse started, it was contagious, likely for two reasons: first that collapsing areas produced invading forces and refugee flows that destabilized their neighbors and second because as you will recall above, these states are interlinked and their rulers rely on trade to furnish the key military resource (bronze) as well as to acquire key prestige goods necessary to maintain the loyalty of the aristocracy.