MurphyA/hacker-news huggingface dataset:
by Isamu | 2025-11-25 17:44:01+00:00
Actually this should be a call-for-proposal for Y Combinator, demonstrating carbon fiber knitting.

Carbon fiber is typically woven in a simple fashion, to keep the strands straight because high tensile strength is the key.

But if it can be shown that knitted structures can preserve the tensile strength, that would be interesting indeed.

Think about the recent Titan submersible failure due to carbon fiber construction. What if instead of sheets of carbon fiber that could delaminate, you had a solid knitted carbon fiber shape? You might be able to demonstrate knitting that has more isotopic strength under both compressive and tensile loads.
by hbn | 2025-11-25 17:44:12+00:00
Windows 8 was fine if you used StartIsBack which just added the Windows 7 start menu back and you could happily ignore the big stupid fullscreen start menu that yanked you away from your desktop. But at that point, yeah no point in upgrading.

Interestingly whoever made StartIsBack is still developing a start menu replacement for Windows 11 (called StartAllBack for some reason), and it's made my usage far more tolerable. You can also get a normal file explorer again, with the normal native right click menu that doesn't hide a bunch of stuff behind a "more options" option
by leo_e | 2025-11-25 17:44:22+00:00
As someone fighting the C++ toolchain daily, there is a painful irony in seeing APT—the tool supposed to solve dependency hell—creating its own dependency crisis.

I sympathize with the maintainers of retro hardware. But honestly? Holding back the security and maintainability of a modern OS base layer just so an AlphaStation from 1998 can boot feels backwards.

The transition pain is real, and Canonical handled the communication poorly. But the 'legacy C tax' is eternal. We have to move critical infrastructure off it eventually.
Show HN: SafeShare – Clean tracking params locally (PWA and bookmarklets
by safeshare | 2025-11-25 17:45:09+00:00
SafeShare is a tiny web app + bookmarklets that remove tracking params (utm_, gclid, fbclid, etc.) and unwrap common redirects – all locally in the browser (no accounts, no servers).

• What it does: clean URLs, unwrap t.co/google redirectors, team whitelist for allowed params. • How it works: client-only JS, PWA + service worker; no network calls to our servers. • Try it: https://j-ai-71.github.io/Supersystem/quickstart.html • Feedback welcome (edge cases, params/redirectors to add).
by temp0826 | 2025-11-25 17:45:20+00:00
I don't speak for everyone obviously but if they only provided search and it led to a lower price I'd be happy. I say this as a user of Orion (iOS); I really only use it because it's half-decent and supports uBO (though it feels pretty buggy and I'm not totally sure it's working most of the time...I really do wish more people were squashing bugs, it seems like a very small team).
by medvezhenok | 2025-11-25 17:45:21+00:00
The core premise (benchmarks are broken), might be correct, but the poverty benchmark he uses is a bad example. The OPM and SPM (supplemental poverty measure, developed in 2009-2012), disagree by less than 10%; and the latter takes into account many of the criticisms in the article.

The author uses MIT Living Wage numbers to argue that should be the new "poverty" benchmark - an absurd proposition. Those might be reasonable middle class numbers. He also implies that the benchmark historically represented what is now covered under that $140K calculation - also false; it took ~$9000 in 1966 to cover a "basic standard of living" for a family of 4 with 1 earner; inflation adjusted, that's around $90,000 today. If you add in SS/Medicare taxes (3% then, 15% today), that puts you at ~$100K-105K.

Using the same MIT Living Wage numbers and taking Essex-Princeton NJ as the area (roughly what the author used), you end up with $99,922 as the living wage for a single earner, 4 person household - almost exactly the same as the household back in 1966.

Were there more jobs in 1966 that paid $9000/year versus jobs that pay $100K today? That's the real story you're looking for.
by adastra22 | 2025-11-25 17:45:43+00:00
They are conflating unrelated things. Cargo is a downstream result of the thing that annoys them, not the cause. What they don’t like is that rust is statically linked with strong versioned dependencies. There are pros and cons to that, but one outcome (which some list as pro and some list as con) is that you need to recompile world for every project. Hence, cargo.
by parasubvert | 2025-11-25 17:45:45+00:00
Tbh making Roblox illegal feels like the same moral panic that our parents had around metal music, hip-hop, and arcades.

My kid plays Roblox, I prevent her from talking to others, and I police the Robux purchases. It really is a fun platform. The problem is for parents that aren't technical, or are negligent and don't know how to police it.
by antonvs | 2025-11-25 17:46:11+00:00
Much of the drive to rewrite software in Rust is a reaction to the decades-long dependence on C and C++. Many people out there sit in the burning room like the dog in that meme, saying "this is fine". Most of them don't have to deal at all directly with the consequences involved.

Rust is the first language for a long time with a chance at improving this situation. A lot of the pushback against evangelism is from people who simply want to keep the status quo, because it's what they know. They have no concept of the systemic consequences.

I'd rather see over-the-top evangelism than the lack of it, because the latter implies that things aren't going to change very fast.
by minimaxir | 2025-11-25 17:46:18+00:00
The issue with testing multi-image with Flux is that it's expensive due to its pricing scheme ($0.015 per input image for Flux 2 Pro, $0.06 per input image for Flux 2 Flex: https://bfl.ai/pricing?category=flux.2) while the cost of adding additional images is neligible in Nano Banana ($0.000387 per image).

In the case of Flux 2 Pro, adding just one image increases the total cost to be greater than a Nano Banana generation.
by Akronymus | 2025-11-25 17:46:25+00:00
I don't think it'd benefit HN at all at this time, as the country of origin just isnt relevant most of the time, and would just invite flamewars. I believe that flagging/downvoting is a good enough tool to deal with stuff, as the HN mod team puts in the work.

Maybe once the site gets 10x as big and the mod team gets overwhelmed, it could serve a purpose, but I doubt that to ever be the case.
by dpark | 2025-11-25 17:46:30+00:00
> but it’s hard to see why it is controversial

You’re probably consuming too much red pill nonsense if it’s hard for you to see why claiming that women who experience multiple sexual partners are mentally damaged is controversial.

The veneer of modern pop psych doesn’t change that this is just slut shaming, no different fundamentally from the claim that women who have multiple partners have loose vaginas. There’s no science behind these sorts of claims. It’s just a mask for insecurity.
by agreeahmed | 2025-11-25 17:46:31+00:00
Currently we're using Stripe to process payments, so you get all the benefits they provide for antifraud etc. baked in. You don't need to provide a Stripe API key, you just go through a Stripe Connect account creation through us. You're still the settlement merchant.

Over time, we'd like to go deeper on that layer of the stack. But it's a long journey and we're still super early.
by fjfaase | 2025-11-25 17:46:38+00:00
What do you mean with bad grammars? Do you mean grammars that are hard to parse (require a lot of backtracking) or do you mean that it leads people to creating bad languages?

My experience is that if a back-tracking parser list all the possible terminals it is expecting at the first location (with some additional information about the rules they occurred in) it fails to get passed, that this usually gives enough information to understand what is wrong about the input or the grammar.
by wtallis | 2025-11-25 17:46:48+00:00
It really comes down to which architectures you're porting to. The two biggest issues are big endian vs little endian, and memory consistency models. Little endian is the clear winner for actively-developed architectures, but there are still plenty of vintage big endian architectures to target, and it looks like IBM mainframes at least are still exclusively big endian.

For memory consistency, Alpha historically had value as the weakest and most likely to expose bugs. But nobody really wants to implement hardware like that anymore, almost everything falls somewhere on the spectrum of behavior bounded by x86 (strict) and Arm (weaker), and newer languages (eg. C++ 11) mean newer code can be explicit about its expectations rather than ambiguous or implicit.
by gadders | 2025-11-25 17:47:05+00:00
>>But I think that the modern historian can't just leave their own moral values, you know, at the library door.

But everyone knows what those values are, because largely (with a few nuances) we all share them. We don't need an historian to remind us that war or slavery is bad. I want to know what Romans think of slavery. I can probably guess what a modern historian thinks of it.
by observationist | 2025-11-25 17:47:15+00:00
If you tack on these faux-pen source VC licenses and complicate things, you're signaling dishonesty and dark patterns. It might not be the case, but it's not a good look imo. VCs don't seem to care, though - it's all about securing the future payoff, doesn't matter what principles or norms get trampled in the process, and it's only a small set of FOSS nerds that ever get bothered by it, anyway.

Thanks, lawyers, you make everything better!
by SpicyLemonZest | 2025-11-25 17:47:49+00:00
> This seems tautological to the point where it's meaningless. It's like saying that if you try to hire an employee that's going to challenge you, they're going to always be a sycophant by definition. Either they won't challenge you (explicit sycophancy), or they will challenge you, but that's what you wanted them to do so it's just another form of sycophancy.

I think this insight is meaningful and true. If you hire a people-pleaser employee, and convince them that you want to be challenged, they're going to come up with either minor challenges on things that don't matter or clever challenges that prove you're pretty much right in the end. They won't question deep assumptions that would require you to throw out a bunch of work, or start hard conversations that might reveal you're not as smart as you think; that's just not who they are.
by javier123454321 | 2025-11-25 17:48:04+00:00
It's not a given, but a personal anecdote is that there simply hasn't been a situation in my life prior to kids that required such a sustained focus on the happiness and wellbeing of another person before kids. It really is a type of growth that would be dare say impossible to duplicate without kids. But of course, I could say that I've never had to live through war and don't think that I could really say that I've built the fortitude that that experience gives you, so the point might be moot. Just to say, kids really give you a perspective, that choosing to be childless does not, while being childless is a perspective that all people with kids got.
by medvezhenok | 2025-11-25 17:48:22+00:00
The core premise (benchmarks are broken), might be correct, but the poverty benchmark he uses is a bad example. The OPM and SPM (supplemental poverty measure, developed in 2009-2012), disagree by less than 10%; and the latter takes into account many of the criticisms in the article.

The author uses MIT Living Wage numbers to argue that should be the new "poverty" benchmark - an absurd proposition. Those might be reasonable middle class numbers. He also implies that the benchmark historically represented what is now covered under that $140K calculation - also false; it took ~$9000 in 1966 to cover a "basic standard of living" for a family of 4 with 1 earner; inflation adjusted, that's around $90,000 today. If you add in SS/Medicare taxes (3% then, 15% today), that puts you at ~$100K-105K.

Using the same MIT Living Wage numbers and taking Essex-Princeton NJ as the area (roughly what the author used), you end up with $99,922 as the living wage for a single earner, 4 person household - almost exactly the same as the household back in 1966.

Were there more jobs in 1966 that paid $9000/year versus jobs that pay $100K today? That's the real story you're looking for.
by epolanski | 2025-11-25 17:48:22+00:00
My point had nothing to do with languages.

My point is against rewrites of critical software for the point of rewriting it *insert my favorite language*. Zig is also a safer language than C, so are many other alternatives, yet the Zig community is not obsessed in rewriting old software but writing new one. And the Zig compiler has excellent C interop (in fact it can compile C/C++), yet the community is more focused in writing new software.

There are many factors that make software reliable, it's not just a matter of pretty types and memory safety, there's factors like platform/language stability, skill and expertise of the authors, development speed and feedback.
by psychoslave | 2025-11-25 17:48:31+00:00
No, the web is now full of this bot generated noise.

And even when only considering the tools used in isolated sessions not exposed by default, the most popular ones are tuned to favor engagement and retention over relevance. That's a different point as LLM definitely can be tuned in different direction, but in practice in does matter in terms of social impact at scale. Even prime time infotainment covered people falling in love or encouraged into suicidal loops by now. You're absolutely right is not always the best
by iamnothere | 2025-11-25 17:48:34+00:00
> The games are complete brainrot - trying to find servers to get money measured in the billions to spend on rare items to collect to increase the money you earn per second to get more things, etc. And of course if you spend Robux - you can pointlessly accumlate fake billions even faster!

There’s at least two whole genre of games like this: idle games, and the more aggressive gacha games (which more often let you pay to win). I guess the differentiator with Roblox is the social aspect.

I do think pay to win is a problem, FWIW.

> So the games are completely pointless and are nothing like playing Counterstrike or Doom or starcraft at a LAN party.

Those games are pointless too though? As are nearly all games.

There’s legitimate criticisms of Roblox moderation and the business model. But games are games, and I feel like criticism of some Roblox-specific issues are getting entangled with normal gaming behavior. I get that you may not love to see kids who ignore you when they’re engrossed in a game, but that’s just how games are. Limit game time if it’s a problem, and/or make them earn their own money for pay-to-win junk. You’re the parent.
by def-to-explore | 2025-11-25 17:49:17+00:00
Tired of wasting hours on trivial PR issues? PR CheckMate is a zero-config Node.js CLI that automatically runs:

ESLint Prettier Dependency checks Spellcheck (cspell) npm audit

All in one command: npx pr-checkmate all

No extra setup, no installing ESLint/Prettier/cspell locally. Keep your pull requests clean and let reviewers focus on real problems.
by kstrauser | 2025-11-25 17:49:34+00:00
I agree with everything you've said here, except that the reality of speaking with a "rust first" developer is making me feel suddenly ancient. But that aside, the memory safety parts are a huge benefit, but far from the only one. Option and Result types are delightful. Exhaustive matching expressions that won't compile if you add a new variant that's not handled are huge. Types that make it impossible to accidentally pass a PngImage into a function expecting a str, even though they might both be defined as contiguous series of bytes down deep, makes lots of bugs impossible. A compiler that gives you freaking amazing error messages that tell you exactly what you did wrong and how you can fix it sets the standard, from my experience. And things like "cargo clippy" which tell you how you could improve your code, even if it's already working, to make it more efficient or more idiomatic, are icing on the cake.

People so often get hung up on Rust's memory safety features, and dismiss is as through that's all it brings to the table. Far from it! Even if Rust were unsafe by default, I'd still rather use it that, say, C or C++ to develop large, robust apps because it has a long list of features that make it easy to write correct code, and really freaking challenging to write blatantly incorrect code.

Frankly, I envy you, except that I don't envy what it's going to be like when you have to hack on a non-Rust code base that lacks a lot of these features. "What do you mean, int overflow. Those are both constants! How come it didn't let me know I couldn't add them together?"
by the_overseer | 2025-11-25 17:49:38+00:00
I care that it's made with React/React Native or other garbage web frameworks. By definition adding layers between native C/C++ Native Win32 will make it slower and use more RAM.

Stop justifying laziness and mediocrity. Microsoft does this just so they can hire cheap javascript monkeys out of colleges. AKA people who shouldn't be writing code and the reason a chat application now uses 1GB of RAM and nobody seems to care or understand why such waste is both bad and stupid.
by twosdai | 2025-11-25 17:49:42+00:00
This is anecdotal, I don't have proof but it's something I think is somewhat related. Is that obesity and nuerodegenerative diseases are somewhat related. So that's a guess as to why some people might have though a weight loss drug would potentially be related in some way with alzheimers.

This could just be false though, I can't recall where I heard this information. So do some searching before quoting me.
by PaulDavisThe1st | 2025-11-25 17:50:13+00:00
> for a long time and for the most part, they provided a better quality of life to many of the subjugated people and provided a path to citizenship. Further, they were adaptable about the places they governed, at least relative to other options at the time, keeping established powers in play, so long as they pledged allegiance to the Roman empire.

Sounds quite a lot like Ghengis Khan, who oversaw the largest empire in history until the British one.
by bradlys | 2025-11-25 17:50:15+00:00
It would only be beneficial to combat pedantry we get around “well, where I live this isn’t a thing. How dare you make an assumption about how others are living on a website dedicated to a Silicon Valley incubator.”

Always some European or flyover state resident wanting to not feel left out of discussions related to SV.

Otherwise, the call is coming from inside the house when it comes to all kinds of traitorous behaviors. Plus, many people who are on here are immigrants. So, they’re living in Silicon Valley but they’re from China/India/Israel/etc.
by _fzslm | 2025-11-25 17:50:22+00:00
This looks like a solidly built app, but having used React Native to ship production apps I really don't think its the way forward – nor spending development effort on making apps "look native" with Liquid Glass and the like. It's so much more brittle than building a web app, even with the impressive steps taken with e.g. the New Architecture.

When nearly everything today is a walled garden, I find it really hard to understand why we'd want to fortify those walls with any more platform-specific code. Though it's imperfect and still in development, I see much more of a future in the open web platform and wasm.
by jancsika | 2025-11-25 17:51:12+00:00
> The wording could have been better, but I don’t see it as a dig.

He created (or at least re-activated) a dichotomy for zero gain, and he vastly increased the expectations for what a Rust rewrite can achieve. That is very, very bad in a software project.

The evidence for both is in your next paragraph. You immediately riff on his dichotomy:

> It’s unfortunate that it would be the end of the road for them, but holding up progress for everyone to retain support for some very old platforms would be the definition of the tail wagging the dog.

(My emphasis.)

He wants to do a rewrite in Rust to replace old, craggy C++ that is so difficult to reason about that there's no chance of attracting new developers to the maintenance team with it. Porting to Rust therefore a) addresses memory safety, b) gives a chance to attract new developers to a core part of Debian, and c) gives the current maintainer a way to eventually leave gracefully in the future. I think he even made some these points here on HN. Anyone who isn't a sociopath sympathizes with these points. More importantly, accidentally introducing some big, ugly bug in Rust apt isn't at odds with these goals. It's almost an expected part of the growing pains of a rewrite plus onboarding new devs.

Compare that to "holding up progress for everyone." Just reading that phrase makes me force sensitive like a Jedi: I can feel the spite of dozens HN'ers tingling at that and other phrases in these HN comments as they sharpen their hatred, ready to pounce at the Rust Evangelists the moment this project hits a snag. (And, like any project, it will hit snags.)

1. "I'm holding on for dear life here, I need help from others and this is the way I plan to get that help"

2. "Don't hold back everyone else's progress, please"

The kind of people who hear "key party" and imagine clothed adults reciting GPG fingerprints need to comprehend that #1 and #2 are a) completely different strings and b) have very different-- let's just say magical-- effects on the behavior of even small groups of humans.
by genewitch | 2025-11-25 17:51:29+00:00
you just restated what i said. perhaps i could have been more clear.

by whatever mechanism, humans can breed at a much younger age than they can feasibly take care of their offspring. Up until maybe 75-100 years ago, "it takes a village" wasn't just a trite canard, it was actually how you raised children. I just finished watching a youtuber explain that raising children after having had to move away from your extended family because of affordability is suck and "maybe that's why young people are waiting to have kids, because there's no village anymore."
by xscott | 2025-11-25 17:51:33+00:00
> This is like complaining that in C [...]

It's really not. Only one of my examples has the equivalent of superfluous parens, and none are dereferencing anything. And I'm not defending C or C++ anyways.

When I was trying to learn Rust (the second time), I wanted to know how to make my own types. As such, the macro `vec!` mentioned elsewhere isn't really relevant. I was using `Vec` to figure things out so I could make a `FingerTree`:

let v: Vec<u32> = Vec::new(); // Awfully Java-like in repeating myself let v = Vec::new(); // Crap, I want to specify the type of Vec let v = Vec<u32>::new(); // Crap, that doesn't compile.

And so on...
by saltcured | 2025-11-25 17:52:06+00:00
> romantically distorted past

Amusing that it can lead to a romantically distorted future for those terminal users.

As someone who came up in that era, I would never want to regain those barrel distortions or incoherent pixels I saw in some of the heavy-handed retro terminals. I paid good money for flatter CRTs and also jumped to LCD with a digital input (DVI) as soon as it was a general option I could justify on a work computer order.

I'm also happy not to be hearing the constant whine of CRT coils, HDD drive motors, or even so many cooling fans these days.
by 0xeb | 2025-11-25 17:52:08+00:00
Hi, I made that port. Performance was not the goal. Just the C++ port mainly.

I also ported the Claude Agent SDK to C++, so fastmcpp is needed for that: https://github.com/0xeb/claude-agent-sdk-cpp

RapidJSON is a good suggestion, maybe I will switch to it at one point.