MurphyA/hacker-news huggingface dataset:
by LorenPechtel | 2025-12-11 16:38:17+00:00
I'm not remotely at that level but I can see the difference between my performance in local terrain vs Death Valley. There's a decent amount of stuff down there bumpy enough to be interesting but not so bumpy as to make it hard to get through. But, on the flip side, I have never been able to find a good, sustainable pace in the mountains.
by Terretta | 2025-12-11 16:38:18+00:00
Just as enterprise software is proof positive of no intelligence under the hood.

I don't mean the code producers, I mean the enterprise itself is not intelligent yet it (the enterprise) is described as developing the software. And it behaves exactly like this, right down to deeply enjoying inflicting bad development/software metrics (aka BD/SM) on itself, inevitably resulting in:

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
by jasonjmcghee | 2025-12-11 16:38:27+00:00
IIUC this is only true if you "Allow full access"

From 3rd party keyboard agreement:

> If you do not enable Full Access, developers are not permitted to collect and transmit the data you type. Any unauthorized collection or transmission of this data without your permission would be a violation of their developer agreement. Furthermore, there are also technical limitations in effect to prevent unauthorized access.
by otterley | 2025-12-11 16:38:35+00:00
I don’t see the similarity here.

When music piracy was facilitated by corporate entities like Napster, the rights holders sued them out of existence, after which piracy evolved into a highly distributed problem that was too costly to prosecute (you can’t sue everyone using BitTorrent one by one). Yes, eventually the music rights holders did facilitate commercial distribution, starting with the iTunes Store, and it was successful because they satisfied the market’s key demand that customers be able to buy one song as a time for 99c, as opposed to the whole album, which would often cost upwards of $10. Also, they didn’t let customers modify the songs or make derivative works.

Generating Disney-derived content with AI, on the other hand, requires massive resources that most individuals don’t possess, thus making corporate entities all but essential players in the game. (This may change in a few years as technology improves, but we shall see.) And we’re talking about derivative works here, not mere copies.
by skavi | 2025-12-11 16:38:39+00:00
> Rust closures that capture data are fat pointers { fn, data }

This isn’t fully accurate. In your example, `&mut C` actually has the same layout as usize. It’s not a fat pointer. `C` is a concrete type and essentially just an anonymous struct with FnMut implemented for it.

You’re probably thinking of `&mut dyn FnMut` which is a fat pointer that pairs a pointer to the data with a pointer to a VTable.

So in your specific example, the double indirection is unnecessary.

The following passes miri: https://play.rust-lang.org/?version=nightly&mode=debug&editi...

(did this on mobile, so please excuse any messiness).
by array_key_first | 2025-12-11 16:38:42+00:00
I don't think it was a misdirection, but I do think it was an obviously bad idea that should've never materialized, and it didn't. I'm arguing it wouldn't have materialized anyway, and if it did, it wouldn't have been necessary.

Things did work out for Japan in the long run, but I still believe a conditional surrender + no atomic bombs should have been the solution. The US was very greedy with its demands, and I think a large part of that is our history of militarism and our desire to use new weaponry. The atomic bomb was already made, and I think realistically we were just itching to use it.
by WorldMaker | 2025-12-11 16:39:09+00:00
I've had it stuck in my head for months now that "LLMs are Legacy Code as a Service". A lot of what they ~~plagiarize~~ produce is based on other people's legacy code. A lot of vibe coding is producing "Day 0 Legacy Code" that is hard to debug/maintain in a lot of the exact same ways Legacy Code always is. (It was written by a developer who is not currently around. It's probably poorly commented/documented in the hows/whys rather than the whats. If it was fast tracked into production somewhere it is probably already in a "not broke, don't fix it" state where the bugs are as much a part of the expected behavior as the features.)

As a developer that has spent far too much of my career maintaining or upgrading companies' legacy code, my biggest fear with the LLM mania is not that my skills go away, but become in so much higher demand in an uncomfortable way because the turn around time between launch and legacy code becomes much shorter and the management that understands why it is "legacy code"/"tech debt" shrinks because it is neither old or in obviously dead technologies. "Can you fix this legacy application? It was launched two days ago and nobody knows what it does. Management says they need it fixed yesterday, but there's no budget for this. Good luck."
by nonethewiser | 2025-12-11 16:39:26+00:00
>You pay for advertisement and product placement.

Well, no. Disney does not pay Hasbro or Mattel to use their characters. It does not pay clothing producers. So no, you dont have to pay people to use your IP because it's just advertising. Disney's IP is their core product.

You can make the argument they should let Sora use it to advertise. But that's not necessarily how it works. And for good reason - fan content doesnt necessarily benefit Disney in a measurable, controlled way. Furthermore, the IP is the thing they themselves are trying to sell you.
by CodingJeebus | 2025-12-11 16:39:49+00:00
> While not perfect

Yep, Disney was also a leading producer of racist tropes and content during Jim Crow. Historical clips of Mickey Mouse characters putting on minstrel shows with blackface alongside other racist stereotypes like crows can easily be found online[0]. Not to mention Song of the South[1], a film Disney produced based on Uncle Remus stories following slaves who happily live on a Georgia plantation. Disney has, of course, done their best to scrub these entries from history, but they played a major role in depicting racist tropes to kids for decades.

0: https://www.youtube.com/shorts/b5j4T9E8PuE

1: https://en.wikipedia.org/wiki/Song_of_the_South
by scarmig | 2025-12-11 16:40:36+00:00
Universities believe that constantly putting out pieces that sound like some research is revolutionary and will change everything increases public support of science. It doesn't, because the vast majority of science is incremental and mostly learning about some weird, niche thing that probably won't translate into applications. This causes the public to misunderstand the role of scientific research and lose faith in it when it doesn't deliver on its promises (made by the university press office, not the researcher).
by coldpie | 2025-12-11 16:41:38+00:00
I agree with your overall point (and I'm pretty confident improved infrastructure will fix the problem for non-homeowners... eventually), but I didn't understand this part:

> usually not the only vehicle either

It doesn't seem like EV or not would make a difference for whether to have more than one vehicle? My wife and I have shared one car, first ICE and now EV, for more than a decade and it didn't make a difference in our habits.
by css_apologist | 2025-12-11 16:41:40+00:00
I've used these things. IME, nowadays it's not worth the bundle size to bring in these libraries. map/filter seems quite optimized, {...obj} is fast since its only shallow. Yes it does come down to practices vs better libraries, but in practice, it's fine IME

One thing to note, i was very excited that we have a bunch of lazy methods on Iterator protocol, but they are slow as shit as of earlier this year.

I wrote a parser a year ago with extreme use of .map (every step of processing was cloning the tokens), and i thought, let's migrate it to lazy iterator - it got ~10x slower :(. The compile time was fine for my use cases, so i didn't give immutable-js a try, but it was a surprise

I did some benchmarks on map+filter vs mutable for of + push, and on firefox up to 200-300 elements map+filter is actually faster (unforunately not on chrome).

Of course, its not the best, but my experience is that modern js engines are fast enough for most use cases to not have to bring in any libraries anymore
by stego-tech | 2025-12-11 16:41:44+00:00
The proposal in question: https://public-inspection.federalregister.gov/2025-22461.pdf

These timelines are dangerously close to the background investigation I had to go through to get a security clearance as a US Citizen. The fact they want this from tourists is appalling.

Non-Americans: Do not come here. America is not safe.

Americans: The proposal is up for public comment at the moment. The document asks for comments to be sent to CBP_PRA@cbp.dhs.gov.
by eric-burel | 2025-12-11 16:41:49+00:00
Related: https://news.ycombinator.com/item?id=46223311 Switching to paid version was already problematic as it uses GCP account system which doesn't have a spending limit, and API keys do not have an expiration date. So the free offer was great for freelancers and SMEs and yet the paid version was the worst possible scenario you can imagine for same freelancers and SMEs. OpenRouter + free models and the increased rate limit you get after buying 10 credits (10€) is my current favourite choice for learning/teaching.
by spwa4 | 2025-12-11 16:41:54+00:00
Pretty sure Youtube is constantly being sued for copyright violation by now.

The question is what will happen when "the platform" is a model downloaded on torrent sites and just generates movies from a prompt. On the plus side: excellent compression ratio. On the down side: discussion with your kids about how at the end Snow White did not transform into a gigantic mech and blew up the Evil Queen with rockets. Must be your old memory, dad!
by mjr00 | 2025-12-11 16:41:56+00:00
> That's why you treat it like a junior dev. You do the fun stuff of supervising the product, overseeing design and implementation, breaking up the work, and reviewing the outputs. It does the boring stuff of actually writing the code.

I am so tired of this analogy. Have the people who say this never worked with a junior dev before? If you treat your junior devs as brainless code monkeys who only exist to type out your brilliant senior developer designs and architectures instead of, you know, human beings capable of solving problems, 1) you're wasting your time, because a less experienced dev is still capable of solving problems independently, 2) the juniors working under you will hate it because they get no autonomy, and 3) the juniors working under you will stay junior because they have no opportunity to learn--which means you've failed at one of your most important tasks as a senior developer, which is mentorship.
by Pingk | 2025-12-11 16:42:19+00:00
This isn't a good idea regardless of why it's being deprecated.

If it's no longer being maintained then put a depreciation warning and let it break on its own. Changing a deprecated feature just means you could maintain it but don't want to.

Alternatively if you want to aggressively push people to migrate to the new version, have a clear development roadmap and force a hard error at the end of the depreciation window so you know in advance how long you can expect it to work and can document your code accordingly.

This wishy-washy half-broken behaviour doesn't help anyone
by nosianu | 2025-12-11 16:42:30+00:00
> Agentic code tools have a significant bias to add versus remove/condense.

Your point stands uncontested by me, but I just wanted to mention that humans have that bias too.

Random link (has the Nature study link): https://blog.benchsci.com/this-newly-proven-human-bias-cause...

https://en.wikipedia.org/wiki/Additive_bias
by mixmastamyk | 2025-12-11 16:42:54+00:00
Big packages shouldn’t be imported until the cli has been parsed, and handed off to main. There’s been work to do this automatically, but it’s good hygiene to avoid it anyway.

A modern machine shouldn’t take this long, so likely something big is being imported unnecessarily at startup. If the big package itself is the issue, file it on their tracker.
by amarcheschi | 2025-12-11 16:44:03+00:00
Just a few days ago I was doing some low paid (well, not so low) Ai classification task - akin to mechanical turk ones - for a very big company and was - involuntarily, since I guess they don't review them before showing - shown an ai image by the platform depicting a naked man and naked kid. though it was more barbie like than anything else. I didn't really enjoy the view tbh, contacted them but got no answer back
by hombre_fatal | 2025-12-11 16:44:13+00:00
Maybe I didn't make it clear, but I didn't build the software in my comment. A clanker did.

Vibe-coding is a claude code <-> QA loop on the end result that anyone can do (the non-experts in his claim).

An example of a cycle looks like "now add an Options tab that let's me customize the global hotkey" where I'm only an end-user.

Once again, where do my 20 years of software experience come up in a process where I don't even read code?
by Festro | 2025-12-11 16:44:22+00:00
“Every single piece of the ad has been hand-held and art-directed—almost as though the AI is an animation tool,” Saunders said. “…It actually has required more work.”

...then just make a normal filmed ad?

If you're spending more time and money on a (currently) lower quality, poorly received result then you're wasting your time.

McDonalds and Coca-cola Christmas ads being the prime examples here.
by mbesto | 2025-12-11 16:44:41+00:00
> There's a significant blind-spot in current LLMs related to blue-sky thinking and creative problem solving. It can do structured problems very well, and it can transform unstructured data very well, but it can't deal with unstructured problems very well.

While this is true in my experience, the opposite is not true. LLMs are very good at helping me go through a structure processing of thinking about architectural and structural design and then help build a corresponding specification.

More specifically the "idea honing" part of this proposed process works REALLY well: https://harper.blog/2025/02/16/my-llm-codegen-workflow-atm/

This: Each question should build on my previous answers, and our end goal is to have a detailed specification I can hand off to a developer. Let’s do this iteratively and dig into every relevant detail. Remember, only one question at a time.
by jsheard | 2025-12-11 16:44:54+00:00
It's a delicate subject but not an unprecedented one. Automatic detection of already known CSAM images (as opposed to heuristic detection of unknown images) has been around for much longer than AI, and for that service to exist someone has to handle the actual CSAM before it's reduced to a perceptual hash in a database.

Maybe AI-based heuristic detection is more ethically/legally fraught since you'd have to stockpile CSAM to train on, rather than hashing then destroying your copy immediately after obtaining it.
by zug_zug | 2025-12-11 16:45:08+00:00
Well you need to actually think about what you're saying here. Suppose for example China/Israel/whoever is the first to invent really, really great drones (like the size of a bird or even a bumblebee) that are lethal.

So then China could, at any point, call up the US president and say "Look there's a drone in the room with you right now. Shut down all your nuclear facilities or I hereby declare war and you're dead within 10 seconds." Then failing that they could hit the VP next, Secretary of state, etc etc.

Point being the idea of sticking with WW2 "rules" with current and future technology is laughably implausible.

And I guarantee you the citizens of Israel would NOT think it's perfectly legit, legal, and fair if Netenyahu got assassinated with a drone along with his military commanders.
by mschuster91 | 2025-12-11 16:45:19+00:00
> Probably because many are purists. It is like how anything about improving Electron devolves into "you shouldn't use Electron."

The Electron debate isn't about details purism, the Electron debate is about the foundation being a pile of steaming dung.

Electron is fine for prototyping, don't get me wrong. It's an easy and fast way to ship an application, cross-platform, with minimal effort and use (almost) all features a native app can, without things like CORS, permission popups, browser extensions or god knows what else getting in your way.

But it should always be a prototype and eventually be shifted to native applications because in the end, unlike Internet Explorer in its heyday which you could trivially embed as ActiveX and it wouldn't lead to resource gobbling, if you now have ten apps consuming 1GB RAM each just for the Electron base to run, now the user runs out of memory because it's like PHP - nothing is shared.
by xhkkffbf | 2025-12-11 16:45:20+00:00
Passes the test of my freelancer friends. They said at lunch that the long term change has been dramatic. What cost $300/m before the ACA turned to $3000/m today. These are all through the local Blue Cross. We talked about the junk policy idea. Certainly the post-ACA policies have some improvements like no pre-existing conditions, but it's pretty much a tangerine-to-oranges comparison.

Maybe yours dropped immediately, but I'm sure it's up quite a bit since then. You may say that's just inflation and that's part of it, but I think the deeper point is that the ACA is not containing the inflation. And that was one of the promises.
by kazinator | 2025-12-11 16:45:38+00:00
> It’s no wonder GCC is trying to add -ftrampoline-impl=heap to the story of GNU Nested Functions; they might be able to tighten up that performance and make it more competitive with Apple Blocks.

[disclaimer] Without brushing up on the details of this, I strongly suspect that this is about removing the need for executable stacks than performance. Allocating a trampoline on the stack rather than heap is good for efficiency.

These days, many GNU/Linux distros are disabling executable stacks by default in their toolchain configuration, both for building the distro and for the toolchain offered by the system to the user.

When you use GCC local functions, it overrides the linker behavior so that the executable is marked for executable stacks.

Of course, that is a security concession because when your stack is executable, that enables malicious remote execution code to work that relies on injecting code into the stack via a buffer overflow and tricking the process into jumping to it.

If trampolines can be allocated in a heap, then you don't need an executable stack. You do need an executable heap, or an executable dedicated heap for these allocations. (Trampolines are all the same size, so they could be packed into an array.)

Programs which indirect upon GCC local functions are not aware of the trampolines. The trampolines are deallocated naturally when the stack rolls back on function return or longjmp, or a C++ exception passing through.

Heap-allocated trampolines have an obvious deallocation problem; it would be interesting to see what strategy is used for that.
by potato3732842 | 2025-12-11 16:45:50+00:00
It's not the overall range that gets you. It's when all the chargers in the work parking lot are taken and you need to go somewhere that doesn't have chargers after work and it's also winter that results in an inconvenient stop or cutting it uncomfortably close. It's absolutely surmountable but it requires planning you didn't have to do before.

IMO what you save by not going to the gas station is a wash if you have to habitually charge more than just at home. You're replacing one habit with another.

I still think they're worth it since you basically never get hit with an exorbitant repair bill for the engine/trans.
by elzbardico | 2025-12-11 16:46:25+00:00
LLMs have this strong bias towards generating code, because writing code is the default behavior from pre-training.

Removing code, renaming files, condensing, and other edits is mostly a post-training stuff, supervised learning behavior. You have armies of developers across the world making 17 to 35 dollars an hour solving tasks step by step which are then basically used to generate prompt/responses pairs of desired behavior for a lot of common development situations, adding desired output for things like tool calling, which is needed for things like deleting code.

A typical human working on post-training dataset generation task would involve a scenario like: given this Dockerfile for a python application, when we try to run pytest it fails with exception foo not found. The human will notice that package foo is not installed, change the requirements.txt file and write this down, then he will try pip install, and notice that the foo package requires a certain native library to be installed. The final output of this will be a response with the appropriate tool calls in a structured format.

Given that the amount of unsupervised learning is way bigger than the amount spent on fine-tuning for most models, it is not surprise that given any ambiguous situation, the model will default to what it knows best.

More post-training will usually improve this, but the quality of the human generated dataset probably will be the upper bound of the output quality, not to mention the risk of overfitting if the foundation model labs embrace SFT too enthusiastically.
by surprisetalk | 2025-12-11 16:46:59+00:00
This reflects my experience with human programmers. So many devs are taught to add layers of complexity in pursuit of "best practices". I think the LLM was trained to behave this way.

In my experience, Claude can actually clean up a repo rather nicely if you ask it to (1) shrink source code size (LOC or total bytes), (2) reduce dependencies, and (3) maintain integration tests.
by ryandrake | 2025-12-11 16:47:20+00:00
> Is software just going to get worse from now on?

I mean, yes? I think, as a pretty universal rule, you can expect commercial software to (on average) get worse every time it is changed. Companies spend little or no time fixing bugs and spend most of their time cramming (wanted or unwanted) features. Of course software is just going to get worse and worse over time.
by HarHarVeryFunny | 2025-12-11 16:47:21+00:00
Having a deprecated API just randomly return failures is an awful idea!

Better to give an actual timeline (future version & date) for when deprecated functionality / functions will be removed, and in the meantime, if the language supports it, mark those functions as deprecated (e.g. C++ [[deprecated]] attribute) so that developers see compilation warnings if they failed to read the release notes.
Show HN: AgentDepot – open-source directory of Cursor rules, Claude, Replit, MCP
by beeruot | 2025-12-11 16:47:44+00:00
I got tired of hunting for quality Cursor rules, Claude skills and MCP servers across GitHub repos, Reddit threads, and Discord servers. Everything's scattered, and half the time the "awesome lists" link to broken repos or have zero setup instructions.

Agent Depot solves this: - Single searchable index across different AI tool formats (Cursor .cursorrules, MCP servers, Claude plugins and skills) - Every agent is tested before being added - Actual installation instructions, not just links - Community-driven via GitHub PRs - No login, no paywall

Built in ~4 weeks as a developer tool for developers. The problem I'm solving: these AI coding tools are powerful, but finding and configuring the right agents shouldn't take hours.

Currently ~71 agents indexed. Looking for feedback on: - Search UX and discoverability - What categories/filters would be useful - Agent submissions welcome via PR

Repository: https://github.com/biagruot/agentdepot-agents Live site: https://agentdepot.dev