1,450 karma · joined March 28, 2018
I think we could legislate some easy-to-understand, easy-to-enforce rules. Like, "you can't have more than N bets open at a time." (1?) Or, "you can't have more than $1,000 worth of bets open at a time."
True, addicts could skirt these rules by having different bets on different sites. But at least it would add a little friction, and it would be easy to monitor compliance.
Yes -- the main reason my wife and I stopped doing "Spaghetti Sundays" was because I hated cleaning up the house (for hours and hours!) before the guests showed up.
The Camden County police successfully brought the crime rate way down. And in the summer of 2020, when riots rocked the US, the CCPD was held up as an example of good policing.
[0]: https://www.nbcnews.com/news/us-news/new-jersey-city-disband...
(EDIT: corrected name of city)
Yes -- this phenomenon is somewhat gendered, but not overwhelmingly so. From the article's own statistic:
A 2025 Pew Research Center study found that 54 percent of women say they turn to a friend for emotional support but only 38 percent of men say they do.
So I think this is a problem that affects men somewhat more often than women, but happens plenty to both.
I will say that loneliness and depression go hand-in-hand. And if someone's husband is clinically depressed, that's going to look a lot like "they're not even trying."
F* is in the ML family of languages, so it looks pretty different from C*.
I know that's what the rhetoric focuses on, but is it the real issue? The people I know personally who are against "data centers" are really just against AI, period. "It takes jobs from artists, it's going to take my job, it's going to enrich a handful of oligarchs," etc.
I suspect that even if some magical breakthrough meant that AI usage could grow and grow without building a single new data center, these guys would still oppose AI.
And understandably so! "I'm worried that AI will take my job" is a reasonable worry, for many jobs! But I feel like "data centers" is, for many people, a pretext.
In the movie, America and the Soviet Union have both developed an AI. The two AIs are linked, and they rapidly shift from speaking human languages, to speaking in sequences of numbers that the onlooking humans can't understand.
Spoiler alert: this all goes horribly wrong for humanity.
[0] https://en.wikipedia.org/wiki/Colossus%3A_The_Forbin_Project
I figure that it's basically making notes for itself, when it has to revisit the same code in a fresh session.
It's a Substack that reports good things happening around the world, divided into sections like "Conservation and Restoration," "Climate and Energy," "Medicine," etc. And they also give part of their profits directly to projects in those categories.
(I'm not affiliated with them, I'm just a subscriber.)
Their pitch is like, "we take your COBOL code, and all the real-world data you can give us. Then we model your COBOL program as a graph, where each node has inputs and outputs. Then we use AI to port each node, making sure that it has the same (input => output) mapping for all the test data you gave us."
And that's not a problem that's solvable with military might! "Investors around the world are declining to buy US government bonds" can't be bombed the way an oil refinery can be.
For video stores, there's Retro Rewind: https://store.steampowered.com/app/3552140/Retro_Rewind__Vid...
There are also games like that for trading-card stores, video arcades, and record stores.
(I'm probably going to buy the record store one, "Wax Heads." Being a music-genre nerd and recommending bands to people is a fantasy that I was born 10 years too late to do in real life.)
IANA formal methods guy, but my understanding is: yes, you're shifting the correctness burden from the code to the spec.
So why is that better? Because the spec is much shorter and more focused -- it strips out all of the implementation details.
It's bad to say "you have to trust this 100,000 line program." It's much better to say "you have to trust this 100 line spec, and the code that verifies it."
It's a policy where, if you become disabled to the point where you can't work, it pays out $X per month, every year until you're 65. And if you're partly disabled and have to cut back your hours, some policies compensate you for those lost wages.
These LTD policies are expensive, but they DO give you peace of mind about this possibility.
* Medicare in the US (single-payer, private providers)
* Medicare Advantage in the US (government provides capitated payments to competing private companies, which then do all the administration work)
* The Singaporean system (complicated, but revolves around mandatory payments to HSAs)
etc.
It's interesting: 3 states (Vermont, Colorado, and Massachusetts) did recently try to make state-level single-payer systems. https://www.thirdway.org/report/single-payer-health-care-a-t...