MurphyA/hacker-news huggingface dataset:
by xg15 | 2025-12-16 22:04:19+00:00
> Social media gives you the feeling of social connection without the obligations of actual friendship.

Pornography gives you sexual satisfaction without the vulnerability of partnership.

It feels weird how after a very good explanation of why thick desires are in the end more rewarding, she focuses on the (ostensible) negatives here, like some sort of obligatory tax or payment that you're evading by focusing on "thin" desire.

Formulated like this, the obvious retort would be "yeah, so what? - why should I bother with obligation and vulnerability if I can have the same rewards without them?"

Of course everyone who has 100 online friends but no one to go to a party with knows why this is bullshit - but it's not following from this paragraph.

Maybe a better way would be to explain that the "negatives" are in fact positives: e.g. The obligation is what lets one build upon a friendship - both for you and your friends - but you do have to explain it, you can't just take it for granted.
by Someone1234 | 2025-12-16 22:04:39+00:00
I really enjoy how they list the price PER MINUTE to make it sound like this isn't absurdly expensive. A lot of people leave their self-hosted runners running 24/7 because, after all, they're self-hosted.

This is $2.88/day, $86.4/month, $1051.2/year. For them to do essentially nothing.

Most notably, this is the same price as their hosted "Linux 1-core" on a per-minute basis. Meaning they're charging you the same for running it yourself, as you'd pay for them to host it for you...
by pizlonator | 2025-12-16 22:05:26+00:00
The sanitizer runtime is not nearly as complex as the Fil-C runtime.

Sanitizers don't have to deal with:

- https://fil-c.org/fugc

- https://fil-c.org/safepoints

Oh and it's not clear if the current revision of the capability model would work with memory mapped IO: https://fil-c.org/invisicaps
by vel0city | 2025-12-16 22:05:42+00:00
> Suppose you pay a 25% income tax and then a 10% sales tax. You're paying the same amount, almost a third of your income, as you would with a 47% sales tax.

No, I don't, because I don't spend 100% of my income every year on income-tax applicable goods. A good chunk of my income, even that which is taxed with income tax, goes to other things (like my mortgage, other investments, groceries, savings accounts, charitable donations, etc.) that either defer paying sales taxes or have no sales tax applied.

Meanwhile other purchases have extra sales taxes applied such a liquor or hospitality taxes.
by drdaeman | 2025-12-16 22:06:08+00:00
I'm not sure it makes sense to classify desires as "good" or "bad" desires, or "thick" and "thin" (or however we may want to label it). One can make such a binary distinction, but it could be just as much as harmful as it could be helpful. There's always a nuance, a hidden variable that makes the whole thing moot.

If there's anything meaningfully binary, I think it's only an internal conflict between one's self-perception (who-I-think-I-am) and one's ideal/goal self-image (who-I-want-to-be) past some arbitrary threshold. Not transforming and not changing is not an issue until there's a desire to transform and become someone else that one has, but that isn't happening (or they don't see it) and that desire is strong or goes for a while and causes some non-negligible grief or stress or something that is not in one's own best interests.

Sure, in stressful modern-day environments, we're especially biased towards more immediate gratification than postponed one. Especially if the postponed one may never happen - modern times are crazy unpredictable. But naively suggesting to dismiss "thin" desires and pursue "thick" ones is dismissive of rest. I mean, people go to beaches and spend literal week doing absolutely nothing. Or binge watch giant series. Or just play games for the sake of it, all day long. And no one has to hate themselves afterwards - all we really need to do is to periodically pause and ask "would it be best to do something else now?" and ponder over that question for a little bit rather than dismiss it with immediate "no I want more".

And there should be a realization brief 5-minute "rest" to check some feeds is unlikely to give any meaningful rest. A non-rest masquerading as resting may be a thing to watch out, but I doubt there's any criteria, except for doing a retrospective observation and questioning oneself "does it satisfy my goals/needs, or am I just wasting my time on this needlessly?".

YMMV, but if there's some meaningful conclusion to be taken out of the article it should be more along the lines of "budget your time mindfully of its value and your long-term goals" than some desire classification model. I'm afraid this "thin vs thick desire" concept unnecessarily obscures the core idea, possibly to the extent it can become sort of a red herring.

Whenever a letter is written on paper or only exists in a digital form shouldn't matter, after all. Neither should a format of resting matter, be it making bread or watching reels, as long as it actually provides rest.

Just my thoughts. I can be wrong about it all.
by joshstrange | 2025-12-16 22:06:22+00:00
I can assure you WarpBuild has Mac runners that work very well. When I first switched GH only offered 1 Mac runner and it was horribly slow. Literally cut my build times in half by changing 1 line in my workflow file to use the WB runner.

Nowadays GH has more sizes by WB continues to beat them in price and performance.

It’s highway robbery what GH charges for the crap they provide. I can highly recommend WarpBuild for Mac (and Linux) runners.
by flohofwoe | 2025-12-16 22:06:29+00:00
A simplified API means higher programmer productivity, higher robustness, simplified debugging and testing, and also less internal complexity in the driver. All this together may also result in slightly higher performance, but it's not the main goal. You might gain a couple hundred microseconds per frame as a side effect of the simpler code, but if your use case already perfectly fits the 'modern subset' of Vulkan or D3D12, the performance gains will be deep in 'diminishing returns area' and hardly noticeable in the frame rate. It's mostly about secondary effects by making the programmer's life easier on both sides of the API.

The cost/compromise is dropping support for outdated GPUs.
by 1718627440 | 2025-12-16 22:06:45+00:00
> Like not being able to change the default shortcuts?

Sure, I would also love if Firefox would work like Emacs or some configurable KDE program, but at least I can access most things without needing to touch a mouse and bulk operation actually work unlike Thunderbird where they basically broke the whole UI a few years back and haven't fixed it since.

Do you know another browser that supports somewhat up-to-date non-Chrome-specific Web features and is better on the features I listed?
by bikenaga | 2025-12-16 22:06:48+00:00
Abstract: "The climate is already changing. The present study shows that these changes have already affected the U.S. economy. It develops a formal framework that accounts for how climate change has affected each county’s economy by altering current and past weather, both locally and elsewhere around the country. The results show that climate change is already reducing annual U.S. income by 0.32% [95% CI: −0.17 to 0.82%] by altering counties’ current, local temperatures, with losses concentrated in the Great Plains and Midwest. Accounting for effects on past temperatures and on temperatures in other counties increases income losses to 12% [2.0 to 22%] and makes them more widely distributed, with suggestive evidence that trade networks propagate effects around the United States. Central estimates can change with different indices of nonlocal weather or models of cross-county heterogeneity. Calculations like those developed here could be updated annually as a way of measuring and communicating the progress of climate change."
by gaigalas | 2025-12-16 22:06:54+00:00
If you do it all, you can optimize the whole supply chain. Maybe you can put some expensive capacity you built to use and leverage it when otherwise impossible, etc.

Maybe it's bad business dealing with lots of non-standardized external hosts, and it drags you down.

Maybe people are abusing the free orchestration to do non-CI stuff and they're compromising legitimate users.

Look, I understand it's frustrating to some consumers. However, it's not irrational from GitHub's point of view.
by ur-whale | 2025-12-16 22:07:14+00:00
> Question: with copyright and authorship dead wrt AI, how do I make (at least) new content protected?

Question: Now that the steamboats have been invented, how do I keep my clipper business afloat ?

Answer: Good riddance to the broken idea of IP, Schumpeter's Gale is around the corner, time for a new business model.
by infecto | 2025-12-16 22:07:52+00:00
I had to go back and look. The quote you have does not seem correct. That 165 is coming from an audit for a trial of both flock and axon patrol car cameras. Only 40 flock cameras. Flock has pretty transparent pricing it’s about $3k per camera for cities. So let’s call it $150k for that test. They installed patrol car cameras in 500 cars. On volume alone the cost is with the cars not flock.

Again I don’t know where that 1.2 million number is coming from. That should get you over 300 cameras deployed in the first year.
by rurban | 2025-12-16 22:07:53+00:00
> Although it was basically the most common language to create dynamic webpages in like, 2000, a higher-level framework never emerged, and Perl therefore lost share to Python and Ruby. Python and Ruby were also, in different ways, easier to use than Perl.

No, 3 major perl web frameworks emerged. One is Dancer, the Sinatra equivalent. Then Catalyst, the old MVS monster. And then the modern slim version of it, Mojolicious.

Perl is also easier to use and deploy than python and ruby, as upgrades don't break your scripts and dependencies. In ruby it's better, but native extensions still break all the time. And python is just too broken to be fixable ever. Worse is better.
by steveklabnik | 2025-12-16 22:07:53+00:00
A specific example: for some reason, when working on Playwright scripts, Claude really likes to inject

await page.waitForLoadState('networkidle');

But this isn't good, and is not encouraged. So much so that there's an eslint that suggests removing it. This means that by running the linter, if Claude does decide to inject this, it gets taken out, because the linter runs and then tells it so.
by mullingitover | 2025-12-16 22:08:52+00:00
I'd contrast this with Flickr. Flickr was the original social network. They have a modest loss leader, a reasonable free tier, but nothing like the permanent money bonfire that the big tech firms operate.

They were kinda the first real Web 2.0 social media site, with a social graph, privacy controls, a developer API, tagging, RSS feeds.

I feel that they never really got to their full potential exactly because these big VC-backed dumping operations in social media (like Facebook) were able to kill them in the crib.

If we're going to accept that social media is a natural monopoly: great. Regulate them strictly, as you should with any monopoly.
by yuppiemephisto | 2025-12-16 22:08:55+00:00
I vibe code extremely extensively with Lean 4, enough to run out 2 claude code $200 accounts api limits every day for a week.

I added LSP support for images to get better feedback loops and opus was able to debug https://github.com/alok/LeanPlot. The entire library was vibe coded by older ai.

It also wrote https://github.com/alok/hexluthor (a hex color syntax highlighting extension that uses lean’s metaprogramming and lsp to show you what color a hex literal is) by using feedback and me saying “keep goign” (yes i misspelled it).

It has serious issues with slop and the limitations of small data, but the rate of progress is really really fast. Opus 4.5 and Gemini were a huge step change.

The language is also improving very fast. not as fast as AI.

The feedback loop is very real even for ordinary programming. The model really resists it though because it’s super hard, but again this is rapidly improving.

I started vibe coding Lean about 3 years ago and I’ve used Lean 3 (which was far worse). It’s my favorite language after churning through idk 30?

A big aspect of being successful with them is not being all or nothing with proofs. It’s very useful to write down properties as executable code and then just not prove them because they still have to type check and fit together and make sense. github.com/lecopivo/scilean is a good example (search “sorry_proof”).

There’s property testing with “plausible” as a nice 80/20 that can be upgraded to full proof at some point.

When the model gets to another jump in capacity, I predict it will emergently design better systems from the feedback needed to prove that they are correct in the first place. Formal Verification has a tendency like optimization to flow through the system in an anti-modular way and if you want to claw modularity back, you have to design it really really well. But ai gives a huge intellectual overhang. Why not let them put their capacity towards making better systems?

Even the documentation system for lean (verso) is (dependently!) typed.

Check out my Lean vibe codes at https://github.com/alok?tab=repositories&q=Lean&type=&langua...
by Analemma_ | 2025-12-16 22:09:07+00:00
I don't really buy it. IMO, the biggest reason formal verification isn't used much in software development right now is that formal verification needs requirements to be fixed in stone, and in the real world requirements are changing constantly: from customer requests, from changes in libraries or external systems, and competitive market pressures. AI and vibe coding will probably accelerate this trend: when people know you can vibe code something, they will feel permitted to demand even faster changes (and your upstream libraries and external systems will change faster too), so formal verification will be less useful than ever.
by frou_dh | 2025-12-16 22:09:14+00:00
Hopefully it gets added to this comparison:

https://htmlpreview.github.io/?https://github.com/python/typ...

If that table is anything to go by, Pyright is not to be underestimated.

I have briefly tried ty (LSP) in Emacs and it seems to work well so far. The only questionable thing I've encountered is that when the signature of a method is shown, the type annotations of some parameters seem to be presented in a particularly verbose form compared to what I'm used to - maybe they're technically correct but it can be bit much to look at.

Anyway, odds are pretty good that ty is what I will end up using long-term, so thanks and congrats on releasing the first beta!
by Glyptodon | 2025-12-16 22:09:24+00:00
So I sort of agree that there's a narrower version of employment that we should care about more than the top-line number. I'd define as maybe "households with at least one dependent under 20 and ~hours worked by household members." I would then break that down into several groups: fine (have healthcare, make enough to cover typical costs for their area, household works < 55 hours/week/adult, and can save 15% for retirement on a household basis), the struggling (make less than this, but work, or work > 55 hours/week/adult, but can cover housing and most basic expenses), and the hopeless (income too low to cover basic costs or not employed). IE If someone is working 60/hrs a week @ $10/hr, and has a kid, maybe not "unemployed" but IMO categorically, almost the same. Same thing if they just do gig work to net $20k/yr. Or are actually unemployed.

All that said, the main issue with the health insurance metric is that it would end up being a forcing function for the continued coupling of work and healthcare, which is bad and toxic.
by apercu | 2025-12-16 22:09:48+00:00
I guess I am luddite-ish in that I think people still need to decide what must always be true in a system. Tests should exist to check those rules.

AI can help write test code and suggest edge cases, but it shouldn’t be trusted to decide whether behavior is correct.

When software is hard to test, that’s usually a sign the design is too tightly coupled or full of side effects, or that the architecture is unnecessarily complicated. Not that the testing tools are bad.
by brailsafe | 2025-12-16 22:10:28+00:00
By your response, it really seems like you read their first sentence as advocating for vibe coding, but I think they were saying something more to the effect of "While it's exciting to reach those milestones more quickly and frequently, as it becomes easier to reach a point where everything seems to be working on the surface, the easier it then is to bypass elegant, properly designed, intimately internalized detail—unavoidable if written manually—and thus when it comes time to troubleshoot, the same people may have to confront those rapidly constructed systems with less confidence, and hence the maintenance burden later may be much greater than it otherwise would be"

Which to me, as a professional SWE, seems like a very engineer thing to think about, if I've read both of your comments correctly.
by kazinator | 2025-12-16 22:10:31+00:00
I don't know now, but for the longest time, Google made a much better Japanese IME for Windows than Microsoft ("Google Japanese Input"). I started using it when running into reliability issues, like disappearing kanji dictionary, or frozen switching between roman and hiragana.

Assuming Microsoft's Japanese IME is still a dumpster fire, and the Google one has not succumbed to Googleshitification, that would be a way to go.

To enable the Microsoft IME there are some rituals to go through like adding the Japanese language and then a Japanese keyboard under that. It will download some materials, like fonts and dictionaries. A reboot is typically not required, I think, unless you make Japanese the primary language.

Once you have the keyboard, LeftShift + LeftAlt chord goes among the input methods. Ctrl + CapsLock toggles hiragana/romaji input. I think these are the same for Google or MS input.
by tetha | 2025-12-16 22:10:45+00:00
Luckily, at work we are this layer of bureaucracy and compliance. I'm very much pushing the agenda and idea that managing a stateful, mutable linux VM is a complex skill on it's own and incurs toil that's both recurring and hard to automate. The best case to handle that is to place your use case into our config management and let us manage it.

Most modern development workflows should just pickup a host with some container engine and do their work in stateless containers with some external state mapped in, like package caches. It's much easier for both sides in a majority of cases.
by senthil_rajasek | 2025-12-16 22:10:48+00:00
The title is "How geometry is fundamental for chess." but 60% of this article is about how animals don't have a sense for numbers or bad at geometry.

Only a couple brief mentions about how chess piece moves are lines and transforms of lines. Other than that the author never establishes the title.

I was actually looking for some insight about chess and did not get any.
by 1718627440 | 2025-12-16 22:10:53+00:00
I am maybe part of the crowd you describe, but I don't disagree so much with you.

I just think, that:

> I happen to believe that barriers to collaboration results in less software for everybody.

is not a bad thing. There is absolutely no lack of supply for software. The "market" is flooded with software and most of it is shit. https://en.wikipedia.org/wiki/Sturgeon%27s_law
by suburban_strike | 2025-12-16 22:11:46+00:00
Can confirm, we're dealing with one right now.

They coast for a while on passable work but it isn't sustained through multiple warnings. The day after we hit him with a PIP he performed a mass exfiltration.

Two weeks after we let him go, systems he had previously had access to were compromised from outside.

With remote workers, if they start underperforming, start revoking whatever access you can at the first warning. Most of the events were set in motion once he saw the writing on the wall. This one was a textbook case with such predictable timing it's absurd that he got as far as he did.

He also raised every red flag in the book during the hiring process (interviewers noted suspicions of AI use) and presented as too good to be true with perfect skills alignment and low salary requirements. At every point in the process we knew better.
by JohnMakin | 2025-12-16 22:11:53+00:00
> We're hungry for more, but we have more than we need.

I do not have more than I need. Very much the opposite - despite making a decent living, I cannot afford the bulk of my medical care that makes my life a lot more comfortable and extends my lifespan. making ends meet is sometimes difficult.

> We're hungry for less, while more accumulates and multiplies.

See above.

> We're hungry and we don't have words to articulate why.

I can articulate why, and a lot of it has to do with the protestant work ethic hell we've decided runs the entire world.

> We're hungry, and we're lacking and we're wanting.

Ok, finally I agree.

> We are living with a near-universal thin desire: wanting something that cannot actually be gotten, that we can't define, from a source that has no interest in providing it.

I am pretty sure what I am wanting - security, healthcare, housing, food, reliable work/career can be defined, and can be gotten.

> The person who checks their notifications is, afterward, exactly the same person who wanted to check their notifications five minutes ago.

Trivial counterexample and one that has happened to me - "Your father has had no pulse for 30 minutes, you need to get to the ER immediately." Definitely wasn't the same person 5 minutes after that. Or even, "Your role has been made redundant, please return your equipment to IT staff." Can probably think of many others.

This seems like fluffery that ultimately isn't saying much or anything at all really. Of course, in an economy full of thin fulfillment supply (such as the examples given in the writing here - porn, social media, etc.) and lacking in thick fulfillment (loneliness epidemic, bad economy if you're not on the tippy top of it, etc.), people will reach for thin ones. You can't wish or grind or hustle your way out of some of this, it is systemic, and in that, I agree with the conclusion here. I just don't believe it really accomplishes much of anything. There are those of us alive who aren't really even that old that remember the world when it was not this way.
by garciansmith | 2025-12-16 22:12:18+00:00
This is very neat, though the difficulty and time it took to get all this material speaks to the problems with subscription services and game preservation. As more and more services and games move to subscription-only models where individuals do not own or even control local copies of the games they play, once those services shut down (or specific titles are pulled) more and more games will be locked away, forgotten, and then lost forever.
by rtkwe | 2025-12-16 22:13:15+00:00
That amount of change over 200 years is vastly different from the supposed timeline for AI to 'change everything' is the core of the difference. Over that long there's time for people to retrain into other jobs and there's enough people not significantly affected by the change that society as a whole can roll on and support the affected people. Mass disruption and joblessness is extremely destabilizing.
by junar | 2025-12-16 22:13:25+00:00
Using the example from the top-level comment, you would install an IME, switch to hiragana mode, start typing "kouen" and convert to kanji when you see the right suggestion.

It might sound complicated at first, but you can do it pretty fast once you get used to it.

https://learn.microsoft.com/en-us/globalization/input/japane...