MurphyA/hacker-news huggingface dataset:
by adamzwasserman | 2025-11-04 02:41:58+00:00
You're proving my point. You know the word 'gravity' appears in texts about falling apples. An LLM knows that too. But neither you nor the LLM discovered gravity by observing reality and creating new models. You both inherited a pre-existing linguistic map. That's my entire argument about why LLMs can't do Nobel Prize-level work.
by a_t48 | 2025-11-04 02:42:55+00:00
Slightly interested if this makes it easier to install ROS on not-Ubuntu, or on "unsupported" Ubuntu versions, but I don't really want to be the one owning the infra behind running the source builds for ROS2, from my experience so far they're kind of slow. Side by side ROS1/2 for migration is kind of interesting, too.
by adamzwasserman | 2025-11-04 02:44:18+00:00
1. I don't need to define consciousness to point out that you're using an unproven claim ('consciousness is probably an illusion') as the foundation of your argument. That's circular reasoning.

2. 'It's a spectrum' doesn't address the point. You claimed LLMs approximate brain function because they have similar architecture. Massive structural variation in biological brains producing similar function undermines that claim.

3. You're still missing it. Humans use language to describe discoveries made through physical interaction. LLMs can only recombine those descriptions. They can't discover that a description is wrong by stubbing their toe or running an experiment. Language is downstream of physical discovery, not a substitute for it
by itake | 2025-11-04 02:44:24+00:00
> How many people retire with minor kids or even kids in college?

I think a lot:

avg age of first pregnancy (29.6) + marital age-gap (2.2 years) + 4 years (last kid) + 18 years + 5 years college (gap / delayed graduation) = 58.8 years old when the last kid finishes college. And then parents (probably) will need to help their kid's with their first home purchase.

> Our fixed expenses - money we have to spend to live - is around $8K a month all in and that’s going to go down some in 2028.

My fixed expenses when I was 25 was $2k/mo (living in ATL in 2012), I spend about $6k/mo (ignoring tax payments).

You obviously don't have to continue growing your expenses, but for many people they want the option to stay in their child-raising home (especially if there is rising interest rates and housing prices).
by yunnpp | 2025-11-04 02:44:56+00:00
I think you're getting lost in the weeds there. I do not see malice in the claim.

The irony is that it does not actually run on my GPU, nor much of other people's, judging by the comments. I don't know where people get this idea that WASM and WebGPU are the holy grail of portability; they are the opposite and the whole ecosystem is a fucking disaster. No offense to OP, though; I can understand the temptation to target that platform.

Anyway, I left more positive feedback in another comment.
by mgkimsal | 2025-11-04 02:45:07+00:00
My brother had an issue with Gusto, but I've not yet, after having used them for... probably at least 10 years now. Maybe longer. I was a refuge from quickbooks payroll which managed to screw up state filings such that I had 2 years of bad filings with the state where they were charging me late fees for things QP screwed up. Huge hassle, cost me days of time and a drive to the state capital to turn in paperwork in person. I swore off quickbooks payroll and have been happy with gusto ever since. But... I'm a single person who occasionally does payments to subcontractors, not dealing with payroll for dozens/hundreds.
by tvenkb | 2025-11-04 02:45:52+00:00
Location: USA

Remote: Preferred

Willing to relocate: Yes

Technologies: Python, Flutter/Dart, Powershell, Elastic/KQL, AI, grok parsing etc.

Résumé/CV:https://drive.google.com/file/d/1Gk3c8oz4GihfYygUpp2ZoU9s93m...

Email: On resume
by exclipy | 2025-11-04 02:46:51+00:00
I made a /split-commit prompt that automatically splits a megacommit into smaller commits. I've found this massively helpful for making more reviewable commits. You can either run this yourself or send this to your coworker to have them run it before asking you to re-review it.

Sometimes it doesn't split it among optimal boundaries, but it's usually good enough to help. There's probably room for improvement and extension (eg. re-splitting a branch containing many not-logical commits, moving changes between commits, merging commits, ...) – contributions welcome!

You can install it as a Claude Code plugin here: https://github.com/KevinWuWon/kww-claude-plugins (or just copy out the prompt from the repo into your agent of choice)
by bmitc | 2025-11-04 02:47:50+00:00
> Moving from LABVIEW to a real programming language ... Switching from C++ to Rust? Probably not.

Weird. LabVIEW is a real programming language. And both LabVIEW and Rust make entire classes of bugs that you often hit in C++ go away, especially for concurrent programs.

> remotely modern development tooling

I would make the argument that it is the tooling, i.e., Git and Diff, that is ancient and not remotely modern. Continually demanding that anything worth source controlling is text-based, and even further line-based, is as antiquated as it gets.
by pseudalopex | 2025-11-04 02:49:24+00:00
> I never claimed it works for everyone

You claimed it worked for a huge fraction of

> I am doubting that it is a provable fact that it works for only a minuscule fraction of people

Nothing they wrote implied minuscule.

> You are effectively implying that firsthand experience and expertise are completely worthless

Individual experience is nearly worthless when making claims about populations. Individual experience and biased sampling do not make an expert.

> and people can only learn information from large scientific studies

Nothing they wrote implied this.

> Correct me if I'm wrong, but I get the impression that your comment isn't really about what I am actually saying, but a general anger towards anything that looks like "pulling yourself up by your own bootstraps"

Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize.[1]

> an anger you can see in other comments in this thread as well.

We read different comments seemingly. Or you inferred anger where it was not evident.

> I don't agree that using techniques that can help people overcome adversity in any way diminishes the challenges people face, or diminishes things like systematic injustice and addiction that certainly can be due to factors outside of one's control, and hard or impossible to overcome.

This misrepresented what you said and what others said.

[1] https://news.ycombinator.com/newsguidelines.html
by gantengx | 2025-11-04 02:49:41+00:00
Location: Singapore

Remote: Yes (open to hybrid/onsite in Singapore)

Willing to relocate: No

Technologies: Java, Golang, TypeScript, JavaScript, Rust, Node, PostgreSQL, Kafka, Ansible, Kubernetes, Terraform, React Native, Expo, React

Resume: https://ronaldsuwandi.com

Email: ronald@ronaldsuwandi.com

Engineer with 16+ years building scalable systems and leading technical initiatives. I've worked across banking, gaming, government, and startups, solving complex technical problems while mentoring engineers and working closely with product teams. Strong in Java, Golang, TypeScript, Rust, and Kafka. Open to remote work with Asia-Pacific timezone overlap.
by r3tr0 | 2025-11-04 02:49:52+00:00
yeet | Chicago, IL / Remote | Full-Time Building a dynamic runtime on top of the Linux BPF sub-system. Looking for extremely talented / passionate Rust developers / Product Managers with a deep interest in Linux internals, Dev Tools, Great Developer Experiences and Systems programming. Experience writing highly-concurrent, performant multi-threaded Rust is a must. Feel free to tell us all about your favorite GNU core utilities / Linux system calls / kernel sub-systems at: work [at] yeet.cx

You can visit us at https://yeet.cx/

Or try our interactive sandbox at https://yeet.cx/play

For more jobs check out https://yeet.cx/careers
by monero-xmr | 2025-11-04 02:49:59+00:00
I own a software business with hundreds of employees I built from nothing. I know all about tech security, hiring security guys, etc. It is a cost center, the directors / VPs / CSOs are overpaid salesmen, 99% of the products you want are features from cloud vendors or provided by standard tools like device management or password managers. I totally get the patina desired by large corporations who need to show wall street they care about security. When I box check I use a super cheap cut rate firm who can check boxes for me at the lowest cost because it is total bullshit. I'm sorry this is the reality
by initramfs | 2025-11-04 02:50:20+00:00
"What the ESL crowd missed was the massive gain that comes from compounding little gains. I am still somewhat blinkered by going for the big win (that would probably make me a bad gambler), but content recently gathered for a couple of articles has provided examples of how those small gains are a better use of time and money than gambling on the next big thing.

The first example is from Marc Swinnen at Ansys, who talked about power optimization. I had asked about the amount of power being wasted in a typical design. “In the past, I have talked to customers about this very problem. I might tell them that using my tool will save them 10%, 15% power. Their response might be, ‘That’s not going to make my day. That’s not worth it to me. Then there is another technique. What will that save me? I tell them that it will save you 5% or 7%. That’s not worth my time.’ Every technique was shot down because it wasn’t worth their time. And at the end they say, how is it that my competitor can manage to get these really low-power designs? Because they pay attention to power at every single step along the way, even the small increments, it all adds up. You can disregard the small contributions at every step, but in the end, it’s like going on a diet. Any particular cookie, any particular walk, isn’t going to make a big difference, but it all adds up over time. And that’s how you achieve a result — by being conscientious at every step.”

Many others agree this is the only way to achieve a low-power design, except some add that it only takes one bad cookie to spoil the whole thing. A very power-efficient piece of hardware cannot provide the expected savings if bad software is put on it, especially if it doesn’t use the very features that the hardware inserted to make it power efficient. Lots of small improvements can make a very big difference."
by pksebben | 2025-11-04 02:51:18+00:00
This is just the typing debate all over again.

If you define the behavior of the system in an immutable fashion, it ought to serve as a guardrail to prevent anyone (yourself included) from fucking it up.

I want claude to tell me to fly a kite if I ask it to do something antithetical to the initially stated mission. Mixing concerns is how you end up spending time and effort trying to figure out why 2+2 seems to also equal 2 + "" + true + 1
by graeme | 2025-11-04 02:52:34+00:00
We have a ton of good, small models. The issues are:

1. Most people don't have machines that can run even midsized local models well

2. The local models are nearly as good as the frontier models for a lot of use cases

3. There are technical hurdles to running local models that will block 99% of people. Even if the steps are: download LM Studio and download a model

Maybe local models will get so good that they cover 99% of normal user use cases and it'll be like using your phone/computer to edit a photo. But you'll still need something to make it automatic enough that regular people use it by default.

That said, anyone reading this is almost certainly technical enough to run a local model. I would highly recommend trying some. Very neat to know it's entirely run from your machine and seeing what it can do. LM Studio is the most brainless way to dip your toes in.
by hatefulheart | 2025-11-04 02:52:37+00:00
As much as I like Delaney, the discord server and Datastar I find this question baffling.

If the Postgres team released PGPro, swore it just contained anti patterns and you can just write the code yourself if you needed that feature, you’d roll your eyes, no?

It’s about the fact they went there, not about the intentions.
by _-_-__-_-_- | 2025-11-04 02:52:40+00:00
I have a music folder 45000+ tracks and counting dating from as far back as 2003. I sync this 450 GB folder to two computers using syncthing and then use rsync to synchronize a subset of these albums (folders by format) to SD Cards inside iPod's. I use Strawberry player for listening (a fork of Clementine) and a combination of beets and MusicBrainz for tagging. Then, I scrobble my listens on ListenBrainz. When I'm in the car or on mobile, I use YouTube Music and it scrobbles to ListenBrainz as well.

I probably should use navidrome or a similar technology to serve the files. I already do this for audiobooks and podcasts and use Tailscale to access it when I'm not on my local network.
by bmitc | 2025-11-04 02:53:05+00:00
I generally agree with your sentiment.

> Rust: The "traits" system is an overreaction to Objects Are Bad.

It's interesting. Interfaces, traits, and mixins are all OOP concepts.

> "Async" is a nightmare

In what way? I do agree though, that it's annoying to yet again have a new language not have concurrency baked into the language. In some ways, Rust has excuses, because they want their concurrency primitives to support microcontroller, real-time Linux, and general purpose programming.
by ActivePattern | 2025-11-04 02:53:44+00:00
I agree it’s worth comparing beef sources! That was my point about within-category differences and harm reduction. Saying "tofu is cleaner" doesn’t make beef comparisons pointless - just like the existence of bicycles doesn’t make car fuel economy comparisons pointless. We should compare across categories and within them, so people who aren’t switching today still choose the lower-impact option.
by etothet | 2025-11-04 02:54:01+00:00
This is often the real driver in these decisions. A previous company I worked at had an API written in modern PHP with Laravel. Traffic wasn’t very heavy on most days and we could autoscale when it was required. It worked great and we hadn’t encountered business problems that couldn’t be fairly easily solved within the ecosystem. However, one of the execs on the business side knew some other exec at a big tech company who told our guy that “PHP can’t scale”. So then we get questions if we should we consider rewriting, if we’re using the “best” language for our needs, etc. They wanted to plan for some theoretical future that they couldn’t even define from a business sense.

Sure, it’s good to be aware of future business needs so that we, as technical people, can be asking the right questions to prepare for what that future may look like, but that almost never means a decision about language x over language y. It’s much deeper than that.
by JSR_FDED | 2025-11-04 02:54:27+00:00
I think the ideas behind HTMX are cool, and Carson’s advocacy around Hypermedia is great.

I came from SPA-land and was tired of the fundamental architectural issue of having to keep the front-end and back-end state in sync.

I’ve compared Datastar and HTMX and decided on Datastar. There’s overlap between the two libraries in that they both support the request/response model, but with Datastar my learning investment takes me further and opens up new possibilities.

In one project I was able to remove a bunch of polling code and simply push a signal from the server to the browser when an external event occurred. The reduction in complexity was crazy.

On an internal tool I noticed I didn’t need Alpine.js anymore, and while anytime I can remove a dependency is a good time, the conceptual simplicity is what really makes me happy.

Now I’m doing a small app where I decided to make a streaming connection between browser and server and simply regenerate and send the entire view over that connection anytime something changes. Intuitively this felt wasteful but it turned out that with compression this works beautifully. There’s just less code in my app, and the code that’s there is less “fiddly” not having to deal with partial updates of the page.

If you’re coming from the world of SPAs, definitely check out both.
by xwolfi | 2025-11-04 02:54:42+00:00
Who is "we" ? I certainly don't spend trillions on frivolities. I think the Saudis via Softbank do, and these people build fake cities in the desert, they are by definition dumb money.

They earn so much from oil and are so keenly aware this will stop, they'd rather spend a trillion on a failure, than keep that cash rotting away with no future investment.

No project, no country, can swallow the Saudi oil money like Sam Altman can. So, they're building enormous data centers with custom nuclear plants and call that Stargate to syphon that dumb money in. It's the whole business model of Softbank: find a founder whose hubris is as big as Saudi stupidity.
by MikeNotThePope | 2025-11-04 02:55:01+00:00
How about this?

“This PR is really long and I’m having a hard time finding the energy to review it all. My brains gets full before I get to the end. Does it need to be this long?”

Force them to make a case for it. Then see how they respond. I’d say good answers could include:

- “I really trieeld to make it smaller, but I couldn’t think of a way, here’s why…”

- “Now that I think about it, 95% of this code could be pushed into a separate library.”

- “To be honest, I vibe coded this and I don’t understand all of it. When I try to make it smaller, I can’t find a way. Can we go through it together?”
by ryao | 2025-11-04 02:55:34+00:00
> On the spiritual side, I think it is somewhat calming. I face this at times when you have patients that pass away and you talk their families; you have to be the bearer of bad news. Right now, we don't know anything about what happens to their loved one’s brain when they're dying. I think if we know that there is something happening in their brain, that they are remembering nice moments, we can tell these families and it builds a feeling of warmth that in that moment when they are falling, this can help a little bit to catch them.

I do not see any connection between this and spirituality. I also see no reason to think that they must be remembering nice moments. It is possible to be remembering painful moments. This seems especially likely in cases of PTSD.
by kathrynloving | 2025-11-04 02:56:29+00:00
Transfyr | AI/ML Software Engineer | Cambridge MA | Full-time | ONSITE or REMOTE (US)

Transfyr is building the API layer for science. The business model of science is broken, leaving meaningful innovation and novel treatments lost in translation. Funding alone isn’t enough to solve the problem; we need a new paradigm for making scientific knowledge that is robust, reproducible, and transferable. At Transfyr, we are building the infrastructure to enable the exchange of scientific know-how between individuals and organizations, just as APIs create interfaces for software systems to seamlessly integrate. We build advanced multimodal and self-evolving AI tools to wrestle with the complex physical realities of science, enabling scientists to fully capture and translate what it really takes to move science beyond the lab.

Key domains of expertise we’re looking for (hiring from entry level to senior leadership): * Computer Vision - take messy real-world images and video and make sense of them * AI / ML Research & Engineering - build the best digital brains to support the best physical brains on the planet * Full Stack Engineering - integrate our AI and data into tools that solve real customer problems

If you're interested, apply here! https://transfyr.typeform.com/to/P5wmbK0V
by johnnyanmac | 2025-11-04 02:56:59+00:00
excuse me, 9000? If that isn't mostly codegen, including some new plugin/API, or a fresh repository I'd reject it outright. LLM's or not.

In my eyes, there really shouldn't be more than 2-3 "full" files worth of LOC for any given PR (which should aim to to address 1 task/bug each. If not, maybe 2-3 at most), and general wisdom is to aim to keep "full" files around 600 LOC each (For legacy code, this is obviously very flexible, if not infeasible. But it's a nice ideal to keep in mind).

An 1800-2000 LOC PR is already pushing what I'd want to review, but I've reviewed a few like that when laying scaffolding for a new feature. Most PR's are usually a few dozen lines in 4-5 files each, so it's far below that.

9000 just raises so many red flags. Do they know what problem they are solving? Can they explain their solution approach? Give general architectual structure to their implementation? And all that is before asking the actual PR concerns of performance, halo effects, stakeholders, etc.
by mulmen | 2025-11-04 02:57:11+00:00
> It's very important to park the engine close to the fire but not too close. Ask me how I learned this.

I was a farm hand as a summer job to cover beer and books in my college years. We harvested wheat which carries a high fire risk. Most farms kept a tractor with a large plow hooked up so it could quickly encircle and contain any fires.

Pulling a 40’ wide plow is hard. Tractors can do it because they have huge engines that suck in huge amounts of oxygen.

Just like fires.

If you get a tractor too close to a fire it starves for oxygen and stalls out. The plow becomes an anchor. There’s just enough time to bail out before the tires catch fire. After a few minutes the whole thing is a pile of ash and melted steel.
by throwawayffffas | 2025-11-04 02:57:12+00:00
> How would you go about reviewing a PR like this?

Depends on the context. Is this from:

1. A colleague in your workplace. You go "Hey ____, That's kind of a big PR, I am not sure I can review this in a reasonable time frame can you split it up to more manageable pieces? PS: Do we really need a DSL for this?"

2. A new contributor to your open source project. You go "Hey ____, Thanks for your interest in helping us develop X. Unfortunately we don't have the resources to go over such a large PR. If you are still interested in helping please consider taking a swing at one of our existing issues that can be found here."

3. A contributor you already know. You go "Hey I can't review this ___, its just too long. Can we break it up to smaller parts?"

Regardless of the situation be honest, and point out you just can't review that long a PR.
by sjsdaiuasgdia | 2025-11-04 02:57:24+00:00
FYI, this kind of garbage truck has been around for >50 years [0], so any wide-scale impact on employment from this technology has likely already settled out.

The waste collection companies in my area don't use them because it's rural and the bins aren't standardized. The side loaders don't work for all use cases of garbage trucks.

[0] https://en.wikipedia.org/wiki/Garbage_truck

>In 1969, the city of Scottsdale, Arizona introduced the world's first automated side loader. The new truck could collect 300 gallon containers in 30 second cycles, without the driver exiting the cab