MurphyA/hacker-news huggingface dataset:
by zamalek | 2025-09-25 23:25:58+00:00
A $80 x86 mini PC is wildly more powerful than prior Pis - at least so far as my home assistant use-case goes (Pi 4). Of course, the Pi is still king of power consumption (where x86 has improved, somewhat) and form-factor.

- $200 PC: https://www.ebay.com/itm/266099800893 - Core i5 @ 3GHz

- $80 PC: https://www.ebay.com/itm/135697152406 - Core i3 @ 3.5GHz

So Pi is really filling a niche where you want form-factor, perf, and power consumption - but not necessarily price. This keyboard is firmly in that niche.
by hn_throwaway_99 | 2025-09-25 23:26:01+00:00
> They work from home or at an office, never at a clinic, and have zero interactions with the patient.

Generalizing this to all radiologists is just as wrong as the original article saying that radiologists don't spend the majority of their time reading images. Yes, some diagnostic radiologists can purely read and interpret images and file their results electronically (often remotely through PACS systems). But the vast majority of radiology clinics where I live have a radiologist on-site, and as one example, results for suspicious mammograms where I live in Texas are always given by a radiologist.

And as the other comment said, many radiologists who spend the majority of their time reading images also perform a number of procedures (e.g. stereotactic biopsies).
by sudosysgen | 2025-09-25 23:27:47+00:00
AN/TPY-2 has a 120 degree FoV, and CENTCOM operates them all across the ME, not just in Qatar, but also in Saudi Arabia, the UAE, and in Israel. The likelihood that none of those installations had the ALBMs in range is basically zero.

The chain of actions you're describing would have around 10-15 minutes to be executed.

The likelihood that neither THAAD nor any of the Patriot batteries were sufficiently ready to launch is also basically zero.

THAAD has an engagement range of over 100km, so the battery was undoubtedly in range; and it can cue Qatar's own Patriot batteries so they can launch the missiles; I find it hard to believe there were none in Doha.

So, this would not be a split-second decision - there was quite a bit of time given the proposed trajectory. It's very very unlikely the US didn't have the sensors to see the missiles given the intense concentration of long-range ABM radars in the region.

Is it theoretically possible the US legitimately couldn't do anything? Yes. But the odds are overwhelming that the US knew about the strike with minutes to spare before making a decision, and decided not to protect Qatar.
by baobun | 2025-09-25 23:27:51+00:00
Still, keys and sessions should all be managable from the client and not depend on a separate server/browser flow, no?

What I'm talking about so far is basically orthogonal to user-server authn/authz flows and mechanics (the scopes of MAS and OIDC). Tightly coupling user-user authn to client-server authz doesn't seem ideal.
by Hobadee | 2025-09-25 23:27:54+00:00
Am I using a different Gemini from everyone else? We have Google Workspace at my job, so Gemini is baked in.

It is HORRENDOUS when compared to other models.

I hear a bunch of other people talking about how great Gemini is, but I've never seen it.

The responses are usually either incorrect, way too long, (essays when I wanted summaries) or just...not...good. I will ask the exact same question to both Gemini and ChatGPT (free) and GPT will give a great answer while the Gemini answer is trash.

Am I missing something?
by andai | 2025-09-25 23:28:03+00:00
I've been wondering can't this be done p2p? Didn't we solve most of the technical problems in the late 90s / early 2000s? And then just abandoned that entire way of thinking for some reason?

If many thousands of people care about having a free / private / distributed search engine, wouldn't it make sense for them to donate 1% of their CPU/storage/network to an indexer / db that they they then all benefit from?
by herval | 2025-09-25 23:29:39+00:00
In most sane development cycles I've seen (from 2-people teams to 100k people teams), intermediate commits disappear as soon as you merge your branch (in other words, you do short lived branches + squash merge).

If you decide to do merges without squashing, then yes, you gotta have to have more hygiene on each individual commit. It creates a lot of unnecessary friction and it's guaranteed to be slower (devs can't use commits as checkpoints/savepoints on their work, but rather each commit becomes a fully fleshed out "intermediate final state"). The only situation where I see this making sense is if you share work on a branch with other engineers (which is also a bad idea).
by varispeed | 2025-09-25 23:30:05+00:00
I don’t dispute that we can dig up documents after the fact. That’s not the same as being transparent by design - that’s damage control.

The Ombudsman’s findings themselves show maladministration, secretive lobbying, and conflicts of interest. That’s not a healthy system keeping itself in check; that’s outsiders catching it after the harm is done.

Saying ‘it’s only the Commission’ is like saying ‘it’s only the engine’ when your car catches fire. The structure allows it, the culture rewards it, and the safeguards are paper-thin if not non-existent.

If the EU really is ‘the least corrupt in history,’ then why are Palantir and Thorn shaping surveillance laws (terrorism dressed as such) in back rooms while the public only finds out years later - and law enforcement looks away? That’s not just a bad apple problem - that’s systemic rot.
by citizenpaul | 2025-09-25 23:30:06+00:00
I don't think there has ever been a perfect time but I also think there has been an ever increasing weakness in the governments desire/ability to enforce regulation roughly since that time period.

I mean the reconstitution of AT&T was one of the IMO the biggest middle fingers to the public I've seen. It was broken up because it was a bad actor and now its back again as a worse than ever bad actor. That was kind my wake up call. I'm sure there is worse though that I don't remember because it was not tech related.

I could be wrong I'm not a huge politics person. Either way I don't think any response to me invalidates my opinion that the current government would not do a better job than cloudflare currently is.
by TeMPOraL | 2025-09-25 23:30:09+00:00
> The fact that people often use the tool wrong certainly begs some criticism of the tool, but when used correctly commits are certainly worth looking at one by one

What do you consider correct usage of git, and why? In this very discussion, I can see at least two distinct purposes that, more often than not, are mutually exclusive:

- To "tell a story" for other people

- To checkpoint units of work as individual perceives them, helping them deal with interruptions (which include running out of work day).

Storytelling is a skill in itself, doing it is a distinct kind of extra work, so you can't really have people use git for both at the same time. Which is where the whole commit history management idea comes from - it's to separate the two into distinct phases; first you commit for yourself, then you rework it to tell a story for others.
by hollerith | 2025-09-25 23:30:23+00:00
>the French like the Americans in Afghanistan, were not defeated on the battlefield. They lost because they got tired of fighting the natives and the war had become politically unpopular.

I don't see how your distinction is relevant. Since 1962, it has been the people the ALN wanted to have power (i.e., not anybody in Europe) who have made all the important policy decisions in Algeria. Since the Taliban took Kabul in Aug 2021, they've made all the important national decisions in Afghanistan. All the US's trillions in spending (and about 2800 American lives lost) gives it no say.
by DoctorOetker | 2025-09-25 23:30:33+00:00
I would really like to see the 270M but which also knows phonetic alphabetic pronounciation in sentences. Perhaps IPA?

I would like to try a small computer->human "upload" experiment, basic multilingual understanding without pronounciation knowledge would be very sad.

I intend to make a sort of computer reflexive game, I want to compare different upload strategies (with/without analog or classic error correcting codes, empirical spaced repetition constants, a ML predictor of which parameters I'm forgetting / losing resolution on.
by kimixa | 2025-09-25 23:30:33+00:00
That's no guarantee it would succeed though - AMD64 also cleaned up a number of warts on the x86 architecture, like more registers.

While I suspect the Intel equivalent would do similar things, simply from being a big enough break it's an obvious thing to do, there's no guarantee it wouldn't be worse than AMD64. But I guess it could also be "better" from a retrospective perspective.

And also remember at the time the Pentium 4 was very much struggling to get the advertised performance. One could argue that one of the major reasons that the AMD64 ISA took off is that the devices that first supported it were (generally) superior even in 32-bit mode.

EDIT: And I'm surprised it got as far as silicon. AMD64 was "announced" and the spec released before the pentium 4 was even released, over 3 years before the first AMD implementations could be purchased. I guess Intel thought they didn't "need" to be public about it? And the AMD64 extensions cost a rather non-trivial amount of silicon and engineering effort to implement - did the plan for Itanium change late enough in the P4 design that it couldn't be removed? Or perhaps this all implies it was a much less far-reaching (And so less costly) design?
by bvrmn | 2025-09-25 23:30:40+00:00
If you could make a good "story by commits" I assure you: a combined single commit would be as much readable as multiple. Good story is a result of composable changes highly visible without artificial splitting.

Funny thing I never seen a good PR with meaningful multiple commits. At least you need to be quite proactive in history rewrite to make it presentable. Usually it's mere fix/fix/fix looking amazingly bad without squash.

If you want to comment on this matter, you are welcome to share your github examples.
by egypturnash | 2025-09-25 23:30:55+00:00
You don't add a new screen.

You plug it into the family TV. Just like you did in the eighties when you were a kid learning to program with your Speccy or c64 or whatever. Mom or Dad or your siblings can hang out and comment on what you're doing with it. That's the experience Raspberry has been claiming to want to reproduce since they first came onto the scene in 2012, despite them not getting around to stuffing a Pi into this form factor until 2022.
by aidenn0 | 2025-09-25 23:31:18+00:00
Last time I looked at DragonflyBSD, it was kind of an intermediate between a traditional kernel and a microkernel. There certainly was a lot more in the kernel as compared to systems built on e.g. L4.

There certainly is a continuum. I've always wanted to build a microkernel-ish system on top of Linux that only has userspace options for block devices, file systems and tcp/ip. It would be dog-slow but theoretically work.
by anotheronelost | 2025-09-25 23:31:30+00:00
I've bought pretty much all of the pis over the years, and was shocked at how capable the pi5 is at doing everything I need from a computer, including programming in a heavy IDE. Unfortunately, it's a non starter for doing anything serious on though as there's still AFAIK no support for full disk encryption in the installer, even if installing to SSD. Such a lost opportunity to be a 'PC' replacement.
by timschmidt | 2025-09-25 23:31:37+00:00
Add to that Qwen3-Omni which can run on a well spec'd workstation, and will happily carry on natural language spoken conversations with you, and can work intelligently with images and video as well as all the other stuff LLMs already do.

I don't think Paramount would look kindly on giving it Majel Barret's voice, but it sure feels like talking to the computer on the holodeck.
by imiric | 2025-09-25 23:32:08+00:00
> I personally don't care about git history - I read code not commit messages.

Honest question: why do you even use version control? What do you get out of it?

Based on your workflow, you could just as well not use it at all, and create zip files and multiple copies of files with names like `_final3_working_20250925`.

Change history is the entire point of version control. It gives you the ability to revert to a specific point in time, to branch off and work on experiments, to track down the source of issues, and, perhaps most useful of all, to see why a specific change was done.

A commit gives you the ability to add metadata to a change that would be out of place in the code itself. This is often the best place to describe why the change was done, and include any background or pertinent information that can help future developers—including yourself—in many ways. Adding this to the code base in a comment or another document would be out of place, and difficult to manage and discover.

You may rarely need to use these abilities, but when you do, they are invaluable IME. And if you don't have them at that point, you'll be kicking yourself for not leveraging a VCS to its full potential.

> I have tried to be more disciplined with commits and stuff like that but I find that it just slows me down and makes the work feel more difficult.

Of course it slows you down. Taking care of development history requires time and effort, but the ROI of doing that is many times greater.

I encourage you to try to be disciplined for a while, and see how you feel about it. I use conventional commits and create atomic commits with descriptive messages even on personal projects that nobody else will work on. Mainly because it gives me the chance to reflect on changes, and include information that will be useful to my future self, months or years from now, after I inevitably abandon the project and eventually get back to it.

Here is an example from a project I was working on recently[1]. It's practically a blog post, but it felt good to air my grievances. :)

[1]: https://github.com/hackfixme/sesame/commit/10cd8597559b5f478...
by rustystump | 2025-09-25 23:32:35+00:00
As mentioned in other comment, not all html which looks like a button is a button. It does in fact take extra work to make everything selectable. On native apps it is even harder because the frameworks do not have selection as built in.

To be clear, I HATE that almost everything isn't selectable. It is one of many reasons why I never use mobile apps. Still, somewhere there has to be a line to ship anything.
by UncleMeat | 2025-09-25 23:33:07+00:00
You can look to the writing of major political actors on the right and see that they just want to hurt people. People wrote that they want federal workers to be traumatized. They want to make life so unappealing for people working for institutions they hate (the bureaucracy and universities being the big two) that people simply leave and the institutions wither and die.

I have friends who work hard for the federal government to do things that people love. That curator who works at the museum of natural history to bring joy to a child who gets to learn something amazing about our world? That curator broke down sobbing at work multiple times this year. That's what they want.
by m000 | 2025-09-25 23:33:31+00:00
How about:

* squash into one commit * git reset HEAD~1 * git add -p * git commit -m commit1 * repeat until no changes are left * add any file deletions/additions

I use this because you can have several commits marked e.g. "commit1". Then you make a final interactive rebase to squash them together.
by darth_avocado | 2025-09-25 23:33:46+00:00
You can’t even do that. The number of samples vary across the years and the number of samples do not account for population size. Australia for a population of 27M has a sample size of 1000 meanwhile India with a population of 1.5B gets a sample size of 3000. At that point the data might as well be just an error. It’s like going to NYC and asking 17 people whether they like Katz’s Deli. You will not get a representative sample at all on whether NYC likes Katz’s Deli. Might as well ask the Ouija board at that point.
by jstimpfle | 2025-09-25 23:35:02+00:00
The idea that a language can handle any complexity for you is an illusion. A language can automate a lot of the boring and repetitive small scale work. And it can have some of the things you would have otherwise coded yourself as built-ins. However you still have to deal with the complexity caused by buying into these built-ins. The larger a project gets the more likely the built-ins are to get in the way, and the more likely you are to rewrite these features or sub-systems yourself.

I'd say, more fully featured languages are most useful for the simpler side of projects (granted some of them can scale quite a way up with proficient use).

Now go research how some of the most complex, flexible, and efficient pieces of software are written.
by aabajian | 2025-09-25 23:35:03+00:00
Well I do enjoy procedures. As for diagnostics, it’s very different when you come from a CS background.

On a basic level, software exists to expedite repetitive human tasks. Diagnostic radiology is an extremely repetitive human task. When I read diagnostics, there’s a voice in the back of my head saying, “I should be writing code to automate this rather than dictating it myself.”
by herval | 2025-09-25 23:35:16+00:00
that's the whole point.

A _branch_ is a unit of work that should be merged when done.

As the owner of a branch, an engineer has the ability to move into intermediate states. The larger the codebase, the larger the possibility of something unexpected breaking or not compiling. Just like editing a large body of text - you will have "incomplete sentences" through the process. It's part of writing. Expecting others to write their drafts the same way you like is just silly - it's putting rigid principles ahead of anything else that matters.
by jacobolus | 2025-09-25 23:35:55+00:00
What topic areas specifically are you interested in? I'm assuming you don't want a list of hundreds of bullet points of small legislative or administrative changes. The most newsworthy things are stuff like getting us out of the forever wars in the Middle East, standing up to Putin and rallying NATO and other allies to support Ukraine, making big investments in American manufacturing and alternative energy, working to reign in large corporations and protect consumers and the public in a wide variety of ways big and small, protecting workers' salaries and fair treatment, improving access to healthcare and keeping costs down, protecting women's access to healthcare despite a hostile misogynist Supreme Court, working to relieve punishing student loans (again with opposition from the Court), ...
by toast0 | 2025-09-25 23:36:23+00:00
> Apple was still selling the iPhone 3GS at the time, a device with 256Mb of RAM and a 600Mhz 32-bit processor.

That's a ton of ram. I recall spending a lot of time on flash websites in the early 2000s in college on the school issued laptop with maybe 64 mb of ram (and I think maybe pentium iii 650mhz so more cpu oomph)
by egypturnash | 2025-09-25 23:36:27+00:00
Give it to your kid. Plug it into the family TV. Let them learn to hack while you're around to answer questions. Just like when you were a baby hacker in the eighties.

Less software is good - it makes kludging up your own more appealing, and there's a guide to getting started with that right there in the manual.

(Or you could try plugging a goggle-mounted display into it and using it as your personal cyberdeck.)
by chasing0entropy | 2025-09-25 23:36:49+00:00
I buy 10 "recertified" versions of it to use until I die. A dozen T470 laptops which are the last to support dual method charging, would have cost 15k when new, about $1500 to buy 12 now. VIZIO non smart lcds connected to anycast receivers. Android 7(IMO the peak of android os) devices that require no online activation. original apk files, core 9 and under CPUs, DDR3 and DDR4 RAM.
by vlovich123 | 2025-09-25 23:37:34+00:00
> However you do have to be careful in critical code because things like integer overflow can also raise a panic.

This is incorrect. Only in debug builds does it raise a panic. In release Rust has to make the performance tradeoff that C++ does and defines signed integer math to wrap 2’s complement. Only in debug will signed overflow panic. Unsigned math never panics - it’s always going to overflow 2’s complement.
by debo_ | 2025-09-25 23:38:05+00:00
I'm adding the rest of the context from the post I linked since it's clear almost no one is reading it:

"Mandatory spending includes entitlement programs like Social Security, Medicare, and Medicaid, which are legally required to provide benefits to eligible recipients. Even if DOGE wanted to, this spending can’t be cut. To change these programs’ funding, eligibility, or benefits, Congress must vote to amend the laws, a daunting task in the current polarized political climate.

Compounding the issue, President-Elect Trump recently stated his unwillingness to touch Social Security or Medicare. In addition, the Republican Party included protecting these programs as one of twenty promises in its 2024 GOP Platform.

If the incoming administration follows along party lines, that leaves discretionary spending (26%) as the only realistic target to trim spending."
by xyst | 2025-09-25 23:38:20+00:00
better off using your own mail server. Stalwart collaboration server makes this stupid simple. Although dealing with poorly configured mail servers and draconian mail server policies can become tedious.

If really concerned about deliverability of transactional or marketing email messages, then relay through one of the many bulk senders.

adding yet another cf product as a single point of failure is not good.
by 9front | 2025-09-25 23:38:31+00:00
The Itanium was a new 64bit architecture. AMD64 is just addition to the 32bit Intel architecture. Itanium didn't make it, so we're stuck with backward compatibility all the way to 8080 in today's x86 processors. That's all in the past! What I'm looking forward is to the future SoC releases with Intel cores and Nvidia graphics.
by hn_throwaway_99 | 2025-09-25 23:39:44+00:00
As someone with a family member in radiology, I thought an important thing was missing from the article and comments I've seen here:

> In 2025, American diagnostic radiology residency programs offered a record 1,208 positions across all radiology specialties, a four percent increase from 2024, and the field’s vacancy rates are at all-time highs.

One reason I hear (anecdotally) that vacancy rates are so high is that fewer top quality people are going into radiology. That is, when med students choose a specialty, they're not just choosing for now, but they need to choose a specialty that will be around in 35-40 years. Many med students see the writing on the wall and are reluctant to invest a huge amount of blood, sweat, tears and money into a residency when tech may potentially short circuit their career eventually.

So what you see is that even though AI is not there yet (I'd really highlight this from the article: "First, while models beat humans on benchmarks, the standardized tests designed to measure AI performance, they struggle to replicate this performance in hospital conditions." For the programmers in the room, it's like AI that can solve all the leetcode problems but then falls over when you get into a moderately complicated situation) but there is a shortage of radiologists now because med students are worried what will happen in 10/15/20 years.
by kevinfiol | 2025-09-25 23:40:07+00:00
I would say if you're looking for a photo management open-source alternative similar to existing solutions like Google Photos, yes.

However, I've been using it for about 6 months and have experienced all sorts of weird bugs/performance issues between the server app and the mobile app. I'm now considering a more barebones solution of using Syncthing + copyparty (as a web UI) to just sync photos from my phone to a RPi, and then running backups to another server with a cron job.