MurphyA/hacker-news huggingface dataset:
by russdill | 2025-07-25 02:57:20+00:00
There's a huge range of chromosomal anomalies. You don't see the vast majority of them because the pregnancy self terminates. It's something the human body is already doing.

People with down syndrome are great people who live rich lives. But along with developmental disabilities they suffer from a great many health problems and have severely shortened life spans. Perhaps the future is such therapies will be able to initially focus on these secondary effects.

I don't think methods of preventing chromosomal anomalies are eugenics, since such anomalies are already not inheritable.
by ivraatiems | 2025-07-25 02:57:21+00:00
It's a shame, because it is a super nice gun to actually shoot.

But at this point, given how Sig has responded (the article has a nice summary), the cover-up is bigger than the crime, almost. The trust is broken at an organizational level.

I don't feel like all manufacturers would respond like this, and it isn't the response I expect from somebody reputable.
by strcat | 2025-07-25 02:57:30+00:00
Android 16 no longer provides device trees for Pixels as part of the Android Open Source Project. It's important to note it doesn't provide those for any other devices. There are no other OEMs providing similar AOSP support. A few OEMs publish more basic device trees for older Android versions. This was Pixels losing one of their advantages compared to non-Pixels but it was never one of our hardware requirements, which are listed at https://grapheneos.org/faq#future-devices. It isn't part of why Pixels are the only devices meeting our requirements. We're working with a major Android OEM to change that though, hopefully for 2026 or at least 2027.

GrapheneOS typically ports to new yearly Android releases in a couple days and tends to have it reach the Stable channel in under 2 weeks. We completed our initial port to Android 16 in a similar time period after the release on 2025-06-10. However, we then had to reimplement device support in a similar way to how we would support a non-Pixel device. Our initial production release based on Android 16 was published on June 30th. As usual, we had to spend around a week making a series of releases fixing regressions reported by users. It reached our Stable channel on July 8th.

Since our port to Android 16 took significantly longer than usual, we backported most of the Android 16 firmware, all of the kernel drivers and parts of the userspace device support to our now obsolete Android 15 QPR2 branch and did a few more releases based on Android 15 QPR2 where we were able to provide the full 2025-06-05 patch level which also turned out to be the full 2025-07-05 patch level due to no vulnerability fixes in the July 2025 Android Security Bulletin or Pixel Update Bulletin. This was an unusual approach and not generally a reasonable way of doing things. We were able to do it successfully.

It won't be nearly as much of an issue going forward since we dealt with building the new automation we needed. Our port to Android 16 QPR1, Android 16 QPR2, Android 16 QPR3, Android 17, etc. shouldn't be nearly as difficult and we should get back to our typical porting time for major releases.
by benreesman | 2025-07-25 02:57:46+00:00
The slot machine thing has a pretty compelling corollary: crank the formal systems rigor up as high as you can.

Vibe coding in Python is seductive but ultimately you end up in a bad place with a big bill to show for it.

Vibe coding in Haskell is a "how much money am I willing to pour in per unit clean, correct, maintainable code" exercise. With GHC cranked up to `-Wall -Werror` and some nasty property tests? Watching Claude Code try to weasel out with a mock goes from infuriating to amusing: bam, unused parameter! Now why would the test suite be demanding that a property holds on an unused parameter...

And Haskell is just an example, TypeScript is in some ways even more powerful in it's type system, so lots of projects have scope to dabble with what I'm calling "hyper modern vibe coding": just start putting a bunch of really nasty fastcheck and generic bounds on stuff and watch Claude Code try to cheat. Your move, Claude Code, I know you want to check off that line on the TODO list like I want to breathe, so what's it gonna be?

I find it usually gives up and does the work you paid for.
by BLKNSLVR | 2025-07-25 02:58:07+00:00
"Never meet your heroes". Also, the opening monologue to Tool's Third Eye[0].

The older I get the more examples I've come across of a person destroying their reputation by either self-over-exposure (social media) or just basic exposure via news of some outrageous or illegal behavior.

I don't have a problem with whatever line you choose to not cross, and I was once much more self-righteous, but I've more recently pretty much made the conscious decision to separate product from producer, art from artist, etc.

Theo Lengyel was recently arrested for murdering his girlfriend, and yet I will still listen to and enjoy Mr. Bungle's music.

Gary Glitter... I still like the song Rock n Roll Part Two.

J.K. Rowling has some controversial views on transsexual women, but that doesn't mean that the Harry Potter series is any less worthwhile reading than it was before.

ReiserFS

I still buy Nestle Quik occasionally

Steve Jobs, Bill Gates, Mark Zuckerberg, name almost any tech bro... (but not Steve Wozniak, he's a treasure)

Sports stars.

Musicians.

I wonder how many other things are worthy of protest if we knew all the facts about all the people who were involved in it's creation.

(I'm attempting to respond to the general concept of "he/she/they bad = it bad", not commenting on GrapheneOS vs CalyxOS or anyone's personal choice over where / what they choose to apply "he/she/they bad = it bad" to, other than saying that it should be a conscious decision not a reflexive reaction)

[0]: https://genius.com/Tool-third-eye-lyrics
by oblio | 2025-07-25 02:58:23+00:00
$200h * 8 * 5 * 4 * 12 = $384 000 per year.

You're like in the top 0.05% of earners in the software field.

Of course, if you save 10 hours per month, the math starts making more sense for others.

And this is assuming LLM prices are stable, which I very much doubt they are, since everyone is price dumping to get market share.
by vips7L | 2025-07-25 02:58:24+00:00
Yeah I’ve writen about error handling syntax here a bit: https://news.ycombinator.com/item?id=44551088

https://news.ycombinator.com/item?id=44432640

It’s actually my #1 issue. I hate not knowing about error conditions and no one in Java uses checked exceptions because the language syntax for dealing with them sucks. Brian had a proposal for handling exceptions in switch but it seems to have died in the water.

Part of me secretly hopes Swift takes over the world because they have a typed throws that works and handling errors is a breeze.
by iotamigrator | 2025-07-25 02:59:06+00:00
Any suggestions on the best crypto law firms to engage on keeping the IOTA Foundation accountable and liable for any and all damages, losses, or expenses incurred as a direct or proximate result of their actions or omissions in this regard: https://news.ycombinator.com/item?id=44543184

Based on Tokenomist data (https://tokenomist.ai/iota), this potentially impacts 3.8% of all IOTA tokens in existence which amounts to about 30 million dollars in damages at the current market capitalization.
by pks016 | 2025-07-25 02:59:48+00:00
I'm a daily user of R with R studio (academia) and also use Python in VS code. Tried posit a couple of months ago, but it wasn't stable as daily driver. Not all packages were there. Might have to try again soon.

I have different specific habits for R and Python. Think it'll take a bit of time for people like me to switch. For a week, I also tried R in VS code, but something wasn't feeling right. I excited for the connections-pane if it works smoothly
by iotamigrator | 2025-07-25 03:00:11+00:00
Any suggestions on the best crypto law firms to engage on keeping the IOTA Foundation accountable and liable for any and all damages, losses, or expenses incurred as a direct or proximate result of their actions or omissions in this regard?

Based on Tokenomist data (https://tokenomist.ai/iota), this potentially impacts 3.8% of all IOTA tokens in existence which amounts to about 30 million dollars in damages at the current market capitalization.
by GolDDranks | 2025-07-25 03:00:16+00:00
The problem with computables is that equivalence between them is only semi-decidable. (If the two numbers are different, it is decidable, but if they are not, it isn't. The problem is that you don't know if they are different a priori, so you might get lucky and find difference, but you might as well not.)

We know for sure that algebraic numbers behave nicely in terms of equivalence, and there are other, bigger number systems that are conjectured to behave nicely ( https://en.wikipedia.org/wiki/Period_(algebraic_geometry) ), but the problem with these and computers is that they are hard to represent.
by voidhorse | 2025-07-25 03:01:01+00:00
This is completely true, of course—the only reason I'm being a bit hyperbolic is because some rebalancing is still in order.

I agree that once the field matures what we will really (hopefully) finally see are people adopting different modes of organization based on the second order systems properties they support, rather than ideology or personal experience—but we aren't there yet.

I think there are certain cases in which using an object oriented approach makes sense, but man, it has led to so many bloated, needlessly complicated systems in which the majority of the work is dealing with inanities imposed by OOP discipline and structure rather than dealing with the actual problem the system is supposed to solve.
by aworks | 2025-07-25 03:02:00+00:00
I recently made a purchase in an Ontario used book store that only took debit cards and cash (and the clerk was behind a COVID shield). Today I went to a used book store in Buffalo, NY that took credit cards (and the clerk was roaming around the store). Somehow that openness and lack of friction got me to buy more books for much more money. And I would gladly return...
by SAI_Peregrinus | 2025-07-25 03:02:20+00:00
Unfortunately many languages treat exceptions as a primary control flow mechanism. That's part of why Rust calls its exceptions "panics" and provides the "panic=abort" compile-time option which aborts the program instead of unwinding the stack with the possibility of catching the unwind. As a library author you can never guarantee that `catch_unwind` will ever get used, so its main purpose of preventing unwinding across an FFI boundary is all it tends to get used for.
by smeej | 2025-07-25 03:03:07+00:00
Here are a couple:

- Parents: https://pmc.ncbi.nlm.nih.gov/articles/PMC3353148/pdf/nihms37...

- People who have DS: https://pmc.ncbi.nlm.nih.gov/articles/PMC3740159/pdf/nihms37...

- Siblings of people with DS: https://doi.org/10.1002/ajmg.c.30101
by 9rx | 2025-07-25 03:03:51+00:00
> They are expected to write go.

Like who? Outside of Go itself, which is really more of a community project — albeit with the chief maintainers still on Google's payroll, almost nothing at Google is written in Go. In fact, Pike once gave a talk reflecting on why it didn't succeed in that space, and noted that it was the "Python and Ruby programmers" who actually ended up adopting it.

Google makes money selling services (i.e. Google Cloud) that run Kubernetes, Docker, etc. If it weren't for that, it is unlikely that Google would even be continuing to maintain it at this point. It was an interesting experiment, perhaps, but ultimately a failure within Google. As before, it was the Python and (probably most especially) Ruby communities that ended up leaning into it.

Which isn't surprising in hindsight. Go offered those who were using Python and Ruby a language that was in the same kind of vein, while solving many of the pain points they were experiencing with Python and Ruby (awful deployment strategies, terrible concurrency stories, trouble with performance, etc.) These developers were never going to use Haskell. They wanted Ruby with less problems.

And that's what Go gave them — at least to the extent of being better than any other attempt to do the same. Since it solved real problems people had, without forcing them into new programming paradigms, it was adopted. Choosing a technology based on starry-eyed fandom and arbitrary feelings might be how you go about navigating this world, but that doesn't extrapolate.
by AzzyHN | 2025-07-25 03:04:23+00:00
On the consumer side...

Smart people know to choose AMD. OEMs heavily favor Intel for the brand recognition. It's the same on the workstation side, though AMD's market share has been rising quite fast (it's apparently at a 36.5% share) so I'm unsure if system integrators will keep pushing their Intel SKUs so heavily.

So they're not cooked, but they're certainly not doing well and barring a massive jump in performance or efficiency, they're not going to be making a recovery any time soon.
by deepsun | 2025-07-25 03:04:38+00:00
> it fills RAM/cache with extra Object stuff

But it has much lesser impact than in, say, Rust, where it's really an allocation (asking kernel for more RAM). Java's Object "allocation" happens in its own heap, which is a big chunk of RAM already pre-allocated from kernel. So in JVM boxing is really cheap, often just a pointer increment. Also oftentimes the wrapper object and its value are located near each other in the same memory page, so we're not adding a RAM access, more like L2 access.

PS: In some cases it can be even faster than Rust or C++, because it pre-allocates larger pages and drops them in chunks within generational GC (e.g. all values "allocated" to process one HTTP request can be GCed immediately after), while C++ is eager to destruct each object immediately. Also, a GC swipe can happen in a separate thread, not bothering the main thread user is waiting for. One can do the same in Rust and C++ using Arenas, of course.
by asa400 | 2025-07-25 03:04:41+00:00
This is not exactly what you’re referencing but I bring it up to show just how complicated things can be: Minnesota recently ruled that you do not have the right to use deadly force if you have the opportunity to escape.

And this is the crucial bit, quoting the article: “The court decided the principle also applies to people who merely use the threat of force — meaning one cannot pull a weapon in self-defense if there are other means to escape, even if the person is threatening them with death or bodily harm.”

https://www.cbsnews.com/amp/minnesota/news/minnesota-supreme...
by AndyKelley | 2025-07-25 03:05:42+00:00
Is that building Go with Go? Or actual bootstrapping? Check this out...

Building Zig with Zig:

andy@bark ~/s/zig (master)> time zig build ________________________________________________________ Executed in 11.67 secs fish external

Bootstrapping with only a C compiler dependency (not even make or shell!):

andy@bark ~/s/zig (master)> time cc -o bootstrap bootstrap.c; and time ./bootstrap ________________________________________________________ Executed in 55.10 millis fish external gcc -o zig-wasm2c stage1/wasm2c.c -O2 -std=c99 ./zig-wasm2c stage1/zig1.wasm zig1.c gcc -o zig1 zig1.c stage1/wasi.c -std=c99 -Os -lm ./zig1 lib build-exe -ofmt=c -lc -OReleaseSmall --name zig2 -femit-bin=zig2.c -target x86_64-linux --dep build_options --dep aro -Mroot=src/main.zig -Mbuild_options=config.zig -Maro=lib/compiler/aro/aro.zig ./zig1 lib build-obj -ofmt=c -OReleaseSmall --name compiler_rt -femit-bin=compiler_rt.c -target x86_64-linux -Mroot=lib/compiler_rt.zig gcc -o zig2 zig2.c compiler_rt.c -std=c99 -O2 -fno-stack-protector -Istage1 -Wl,-z,stack-size=0x10000000 -pthread ________________________________________________________ Executed in 305.06 secs fish external
by skydhash | 2025-07-25 03:05:47+00:00
> We’re so unaccustomed to working with non-deterministic computer tech

The whole history of computer history is about making computing deterministic, after we found out that having generative anything (Recursion, Context-Free grammar,...) is a double-edged sword. So for any known set of inputs, you want the output to be finite and non-zero, and all items having the correct properties.
by bionhoward | 2025-07-25 03:06:48+00:00
Anthropic goes hard on the virtue signalling but I still don’t get how anyone manages to satisfy “Customer may not and must not attempt to (a) access the Services to build a competing product or service”

So I just avoid it and generally think the whole thing isn’t serious, because nobody seems to care enough about the safety implications of building AGI with legal terms which are logically impossible to satisfy to demonstrate appropriate attention to detail (aka, yall are noobs)
by tw061023 | 2025-07-25 03:06:53+00:00
LLVM is basically a resource pool for C++ compiler development. As such, it is highly C++ specific and leaks C++ semantics everywhere.

It's especially funny when this happens in Rust, which is marketed as a "safer" alternative.

Would you like a segfault out of nowhere in safe Rust? The issue is still open after two years by the way: https://github.com/rust-lang/rust/issues/107975
by antonvs | 2025-07-25 03:07:02+00:00
Time to read "Debunking the 'Expensive Procedure Call' Myth, or, Procedure Call Implementations Considered Harmful, or, Lambda: The Ultimate GOTO":

https://dspace.mit.edu/handle/1721.1/5753

The point is there's a closer connection between functions and gotos than you might imagine.
by AdieuToLogic | 2025-07-25 03:07:42+00:00
> Right now, the only thing that makes credit cards a better proposition is being able to pay without having enough money in the bank, and maybe enjoying greater protection from fraudulent merchants.

This is the entire value proposition of credit cards and is what undergirds the issuer (bank) justification for interest rates assessed. To be able to defer card-holder immediate payment for some period of time and/or to put the onus of proof-of-purchase on the merchant instead of the card holder.

The last point is non-trivial when considering debit or debit-like networks result in funds being transferred during settlement (often performed daily), thus making the customer responsible for proving they did not perform the transaction post hoc.
by zer00eyz | 2025-07-25 03:08:26+00:00
Data centers are cap ex

Except the power and cooling demands of the current crop of GPU's means you are not fitting full density in a rack. There is a real material increase in fiber use because of your now more distributed equipment. (because 800gbps interconnects are NOT cheap).

You can't capitalize power costs: this is now a non-trivial cost to account for. And the more power you use for compute the more power you have to use for cooling... (Power density is now so high that cooling with something other than air is looking not just attractive but like it is going to be a requirement.)

Meanwhile the cost of lending right now is high compared to recent decades...

The accounting side of things isnt as pretty as one would like it to be.
by analog31 | 2025-07-25 03:09:26+00:00
I've played jazz for about 45 years, and admittedly I'm not steeped in theory. I do know a massive number of tunes.

The people I've known who have made practical use of theory, mainly used it to help them streamline composition and arrangement. This I appreciate because I enjoy playing original material. Of course theory isn't telling them what to write, but perhaps it helps them come up with more coherent ideas more quickly.
by akomtu | 2025-07-25 03:09:30+00:00
Most of your monthly active users don't want to read your articles. They want to get their questions answered with as little effort as possible. This is what Google's Overview is doing: it's transforming your articles into a form-factor that the users want. This is what you could be doing as well: rather than creating food for AI, create a mini-AI yourself that answers user questions. It doesn't have to fabricate answers, rather it can quote your memos in a format tailored to users, while your memos will remain private. This will also stonewall Google's AI, for now it would have to interrogate your mini-AI.
by throwaway-0001 | 2025-07-25 03:09:35+00:00
I know you talking about my hidden profile. But let say you have a banking account you don’t want people to find out.

Currently you can only keep it on the main profile or any other secondary, which are easily visible.

With my approach you can minimise 99% of the risks for most users.

And even so, you can have 2 hidden profiles. So you can always show the decoy hidden profile.
by spauldo | 2025-07-25 03:09:35+00:00
There's also the fact that most people don't want to hear new music. You go to the bar and there's a band, it's not the original or two they slip into the set that gets people listening - it's the covers of songs people already know.

The Beatles were one of the first British bands who had mostly original music on their first album. The Stones had only one original song on theirs. This was record company policy at the time - who would buy a record of songs they didn't know?
by isodev | 2025-07-25 03:11:29+00:00
The EU (the ECB) is actively working towards a system similar to SEPA (Single Euro Payments Area) but for cards [0]. This would enable card transfers to also become faster (SEPA is instantaneous even cross-border within the EU) also allow for operations not depending on Visa or Mastercard.

There is a major EU effort to develop an alternative 'instant payment' system that doesn't depend on Visa or Mastercard called Wero [1].

[0] https://www.ecb.europa.eu/press/pubbydate/2019/html/ecb.card...

[1] https://wero-wallet.eu
by nonhaver | 2025-07-25 03:11:47+00:00
this is great. i think extensions that detect generated music, speech, video, or text will become really important. im curious how light and performant these detection models can get. maybe a single extension could handle multiple media types.

one concern (speaking as someone who doesnt know what these internal pipelines look like) is that suno/udio could tweak their model weights just enough to change the fingerprint, making a detector obsolete with each new release (or even more simple - maybe just apply post processing? id imagine a small reverb could diffuse the content enough to make the fingerprint difficult to detect). that turns it into a cat‑and‑mouse game. if its cheaper for them to mutate models/tweak post processing than for others to train new detectors, they could spin up a new fingerprint every day.
by marifjeren | 2025-07-25 03:12:33+00:00
Text-to-text LLMs can only do one thing: output text.

These other capabilities that chat tools provide are actually extras built on top of the output sequence:

- reading and editing files

- searching the web

- executing commands

If your favorite chat tool (ChatGPT, Gemini, Claude, Cursor, whatever) already has all the tools you want, then you don't need to add more via an MCP server.
by 9rx | 2025-07-25 03:12:35+00:00
> Unfortunately many languages

Just Java (and Javascript by extension, as it was trying to copy Java at the time), really. You do have a point that Java programmers have infected other languages with their bad habits. For example, Ruby was staunchly in the "return errors as values and leave exception handling for exceptions" before Rails started attracting Java developers, but these days all bets are off. But the "purists" don't advocate for it.
by wonderwonder | 2025-07-25 03:12:47+00:00
Last year? Its just a house in a residential neighborhood. Neighbors obviously did not want to interact with them very often, limited to a wave if one of them was taking out the trash. The segregation is pretty much desired by the neighbors and understood by the nurses. No one raising a family really wants to have to interact with mentally challenged non family people every day of their lives. Keeping the interaction limited means complaints don't happen.