MurphyA/hacker-news huggingface dataset:
by ExoticPearTree | 2025-05-28 05:45:28+00:00
Nice! (no sarcasm)

I have very strong opinions about some subjects, one of them being BGP.

I believe sessions should not be tear down just because you receive malformed data. You should be able to remove just the corrupt data. Or treat as a withdraw message like one of the RFC recommends.

I for one one would like knobs to match on any attribute and value and remove/rewrite them at will. Imagine something akin to a very smart HTTP proxy.
by uejfiweun | 2025-05-28 05:47:15+00:00
Agreed. And unfortunately it's Musk's own fault.

It's a shame to me because I don't really give a damn about the guy, I just like space and think rockets are cool, but we have a situation where a potentially revolutionary rocket is being overshadowed by the CEOs antics to the point that people are rooting for the rocket to fail. It's tragic, in a way.
by const_cast | 2025-05-28 05:48:27+00:00
Thrift store pricing is pretty good IMO. At least real thrift stores - those more curated vintage stores are, obviously, going to be higher priced.

But if you know how to check for quality materials and craftsmanship you can find really, really good clothes and furniture for unbelievably cheap.

The thing about fast fashion is, well, the clothes suck. They're more plastic than fabric, they fall apart, they look awful, they're not breathable, and on. You don't actually want to thrift those, because their lifespan is approximately 5 washes. Yes, it's that bad with some brands.

But if you can find nice cotton trousers or a great trench coat for 8-10 bucks you're golden. Just have them dry cleaned, press them, and you're going to be getting a piece of clothing that's higher quality than anything you can find in stores.

I found a great 3 piece brown tweed suit a bit ago. Miraculous all three pieces are there, dated somewhere in the 1970s. The construction was sturdy, the material was thick and rough, but everything was lined with viscose. The buttons were actually wooden, shaped like little hot buns. Multiple sets of them too, large ones for the pants and suit jacket and little tiny ones for the waistcoat. A suit like that made today would be at least 800 dollars. I got it for less than 50.

Point is, old stuff isn't low quality. Over the past 50 years, clothes have progressively gotten poorer in just about every metric. Yes, buying new cheap junk is sometimes cheaper than old stuff. That's because the new stuff is just so incredibly bad.

The stuff you're buying on Temu, Shein, H&M, whatever - is not competing with quality garments from decades past. They're not just not in the same category, there's many categories between them.
by SyzygyRhythm | 2025-05-28 05:49:13+00:00
We don't know all the things they did to the Booster, but among them were deliberately not igniting some engines as well as taking a more aggressive angle-of-attack on descent (the rocket is a fairly effective lifting body, as it turns out!).

There may be more things, but between those two I think the latter was a bigger problem. It would have gotten hotter and more physically stressed. And then weakened to the point to where re-igniting the engines caused it to fail.

They also used a new hot-staging maneuver, where the gases were directed out one side so that it flipped more rapidly in the other direction. It was a really fast flip! A rocket the size of a small skyscraper turning 90 degrees in just a few seconds. That could have jarred something loose, too.

Hopefully we find out in the post-mortem. SpaceX doesn't typically give the public as much detail as we'd like, but they're pretty good at sharing the high-level reasons why something failed.
by Pamar | 2025-05-28 05:49:32+00:00
Well, if a party has enough votes to pass such a law, it means that the majority of the society has no problems with that.

Conversely, if this hypothetical party had a secret agenda to pass the law when they get elected, but they kept this a secret until then... first of all they will probably lose of voters in the next election. Also, they might find out that former immigrants do not automatically reward this behaviour in terms of votes.

I do not find this scenario particularly realistic.
by dorkitude | 2025-05-28 05:49:39+00:00
My favorite thing about this article is that it was released the exact same day as Claude 4 Opus.

If it's satire, it's brilliant: because most of the comments I see (here and elsewhere) are clearly written by people who tried agentic coding before Opus 4, and haven't given it a fair shake over the ensuing five days.

IMO the most important engineering skill in 2025 isn't low-level programming, or the craft of debugging, or even having a firm grasp of system architecture. Believe it or not, I truly believe the vibe-first juniors will learn that stuff too, over the course of their careers, just as we did: through necessity (As an aside: if you don't think they'll encounter such necessity, then it's inherently not one any more than the countless other once-honored, fastidious hallmarks of craft that have since been rendered obsolete. And if you don't think they'll learn even upon encountering a true necessity, then you underestimate them.)

No, the most important engineering skill in 2025 is non-attachment: constantly update your priors, and hold your opinions very loosely. Because those opinions could be fully wrong before the essay even gets shared.
by simonw | 2025-05-28 05:49:59+00:00
> Why don't people publish public logs of their interactions to prove it can do this beyond a "make a bouncing ball web game" or basic to-do list app?

It's possible I've published more of those than anyone else. I share links to Gists with transcripts of how I use the models all the time.

You can browse a lot of my collection here: https://simonwillison.net/search/?q=Gist&sort=date

Look for links that's at things like "transcript".
by simonw | 2025-05-28 05:53:48+00:00
That's likely a change that needs to be made to either https://github.com/simonw/llm-gguf or https://github.com/simonw/llm-llama-server

... OK, I got the second one working!

brew install llama.cpp llama-server --jinja -hf unsloth/gemma-3-4b-it-GGUF:Q4_K_XL

Then in another window:

llm install llm-llama-server llm -m llama-server-tools -T llm_time 'what time is it?' --td

Wrote it up here: https://simonwillison.net/2025/May/28/llama-server-tools/
by csomar | 2025-05-28 05:54:09+00:00
The bubble has popped and the euphoria has tuned down. However, the stable coins market is a $1-2trillion market (https://defillama.com/stablecoins), so there is still a long way to go/grow. Other cryptos like Bitcoin and Ethereum will continue to exist. Bitcoin mainly as an asset against the stable and Ethereum as a network to process defi transactions (you can exchange stable coins for crypto without an exchange now).
by scott_w | 2025-05-28 05:54:24+00:00
Except if your schema changes in a way that forces your API contract to change, you have a big red alarm to tell you to investigate what’s using that contract and update it too.

When your apps connect to a DB schema, the change is silent. You just run ALTER TABLE and… whoops, you just brought down a service you didn’t know existed because the contract was implicit.
by leonim | 2025-05-28 05:54:37+00:00
One my favorite tools is Visidata (https://www.visidata.org/). It is great for viewing and working with data in the terminal. It is useful if you need to quickly explore data and change some data.

VisiData makes it possible to view a lot of data such as CSV, JSON, databases, etc. All the supported formats are listed in https://www.visidata.org/docs/formats/

There is a wonderful tutorial in https://jsvine.github.io/intro-to-visidata/
by const_cast | 2025-05-28 05:54:55+00:00
The difference is I'm a person - I get special privileges. A computer program does not, we don't need to cater to them because, well, they don't have feelings. Or rights.

Ultimately these are tools, slaves to humans, meant for one thing only - to serve us. If they're not serving us, they should be eradicated. Because that's what we do.

Stealing from humans, no matter how convoluted, is bad. We shouldn't do that, and luckily that's completely optional and we don't have to stand for it. The computer programs can't fight back, it's okay.
by Aurornis | 2025-05-28 05:54:56+00:00
> Simply don't set voltage or current limits in the standard,

There are thermal and safety limits to how much current and voltage you can send down standard cabling. The top PoE standards are basically at those limits.

> and instead let endpoint devices advertise what they're capable of.

There are LLDP provisions to negotiate power in 0.1W increments.

The standards are still very useful for having a known target to hit. It’s much easier to say a device is compatible with one of the standards then to have to check the voltage and current limits for everything.
by tanelpoder | 2025-05-28 05:55:02+00:00
When doing 1M+ IOPS, you probably do not want to use OS IO schedulers due to the OS (timer & spinlock) overhead [1] and let the hardware take care of any scheduling in their device queues. But you're right about flattening the IO burst spikes via DB configuration, so that you'd have constant slow checkpointing going on, instead of a huge spike every 15 minutes...

All this depends on what kind of storage backend you're on, local consumer SSDs with just one NVMe namespace each, or local SSDs with multiple namespaces (with their own queues) or a full-blown enterprise storage backend where you have no idea what's really going in the backend :-)

[1]: https://tanelpoder.com/posts/11m-iops-with-10-ssds-on-amd-th...

Edit: Note that I wasn't proposing using an entire physical disk device (or multiple) for the low latency files, but just a part of it. Local enterprise-grade SSDs support multiple namespaces (with their own internal queues) so you can carve out just 1% of that for separate I/O processing. And with enterprise SAN arrays (or cloud elastic block store offerings) this works too, you don't know how many physical disks are involved in the backend anyway, but at your host OS level, you get a separate IO queue that is not gonna be full of thousands of checkpoint writes.
by krige | 2025-05-28 05:56:11+00:00
The Commodore Amigas had their 68k clock speed differ based on region due to carrier frequency difference (more specifically, 2x freq for NTSC, 1.6x for PAL, which resulted in almost the same, but not quite, clock speed).

It's interesting how the differing vertical resolutions between these two (200p /400i vs 256p /512i) also had some secondary effects on software design, it was always easy to tell if a game was made in NTSC regions or with global releases in mind because the bottom 20% of the screen was black in PAL.
by AlotOfReading | 2025-05-28 05:56:20+00:00
One of the big advantages is visibility. You can be aware of what other people are doing because you can see it. They'll naturally come talk to you (or vice versa) if they discover issues or want to use it. It also makes it much easier to detect breakages/incompatibilities between changes, since the state of the "code universe" is effectively atomic.
by kgeist | 2025-05-28 05:58:36+00:00
I've found that Linux already does this out of the box: if you load a model once, subsequent loads are much faster because the OS caches the on-disk pages entirely in RAM (assuming you have enough RAM). If you switch to another model and/or run out of RAM, the OS will automatically unload some parts to make room. So all you need to do is read the most used model(s) on startup, to warm the disk cache + add a TTL to unload models and stop actively occupying (V)RAM.
by shawabawa3 | 2025-05-28 05:58:51+00:00
Every time I've been monorepos compares with polyrepos it's always "monorepo plus millions of dollars of custom tool engineering" vs "stock polyrepo"

Why can't we add millions of dollars of tool engineering on top of polyrepos to get some of the benefits of monorepos without a lot of the pain? E.g. it wouldn't be too hard to create "linked" PRs across repos for changes that span projects, with linked testing infrastructure

And I don't see how discovery changes significantly from browsing through loads of repositories instead of loads of directories in a repository
by palmfacehn | 2025-05-28 06:00:08+00:00
There are still interesting use cases for blockchain based applications and payments. I'm not sure that these uses justify the current valuations. Similar things can be said about traditional financial markets or momentum driven stocks.

Cryptocurrency markets exists on the extreme end of over-financialization. Bubbles and financial mania are not unique to blockchain tech. Pets.com would be another example. These things exist downstream from easy money policies.

Most of the hyper-grifters have pivoted to AI + blockchain hype.
by hi_hi | 2025-05-28 06:00:53+00:00
Ah, yes, of course. I wasn't trying to make quite the esoteric point. More specifically that currently, if starship succeeds, it will be good business for SpaceX and enable them to launch many more satellites around earth at a cheaper cost but greater scale. I don't think this will be much of a positive for humans in general (beyond the current state).

Now if the lofty goals of enabling Mars and Moon habitation come to fruition, I would take a different view. For now I consider achieving that goal to be science fiction, but hopefully that changes in my lifetime.
by jader201 | 2025-05-28 06:01:39+00:00
I actually prefer the (grammatically incorrect) sentence-starting “And”.

Sentence-starting “And”s bring the drama. And that’s why I love them.

Or even better:

Sentence-starting “And”s with line breaks bring even more drama.

And that’s why I love them.

Yeah, all kinds of rule breaking with this (pluralized quote word). But that’s how I like to write.
by shkkmo | 2025-05-28 06:03:18+00:00
The thread is this.

#1 Troy works for Microsoft.

#2 No Troy doeys, as he clearly states.

#3 Being a Microsoft Regional Director makes him an employee and any claims otherwise are based on some arbitrary semantic distiction, not a real difference

#4 No, there is a real difference. That award is like these other awards and none of them take you anywhere near being an employee.

#5 the arguemnt in #3 is flawed because MRD is confusing and the example title others aren't. (Which misses the point, that using non-confusing examples is much better than using other confusing examples if you want to explain something.)

#6 that doesn't affect the argument being made in #4

#6 repeat ad nauseum

Troy is not a Microsoft employee, no ammount of semantic wiggling will make him a Microsoft employee, no matter how confused people are by the title of the MRD award. That confusion may be justifiable, but doubling down when your error has been explained is not.
by keeganpoppen | 2025-05-28 06:04:44+00:00
Bitcoin proof of work is both the sine qua non and the ne plus ultra of the entire sphere… and i say this as an enjoyer of all the fancy math et al. in the space. it is genuinely a monumental achievement… one whose value… is indeterminate (at best; and worst). and i wouldn’t dare opine on that point, because i’m “from Switzerland” on this. but that it opened a mathemeatical pandora’s box is undeniable. when i read the original Bitcoin paper (about a year after publication) i was suffused with the feeling that something fundamental was “discovered” in a way i’ve only felt a handful of times in my entire life… (and then i spent all my BTC on drugs)
by Disposal8433 | 2025-05-28 06:04:51+00:00
> we may see captchas blocking humans

That article comes at the same time I am blocked by PayPal's stupid captcha because I don't have a "web GPU" (whatever that shit is) in my browsers (even on Chromium) despite having 2FA enabled. A good reminder that I should stop using PayPal for my subscriptions and donations.

In addition to that, we have web sites broken because they don't implement properly the CloudFlare protection and give me 403 or 500 errors. We really need a new web.
by vinnymac | 2025-05-28 06:06:49+00:00
I established monorepos for the last two large projects I operated. I’ve never heard such nice compliments from contributors in my whole career. It seems not only can it be a productivity booster but people genuinely love when things are easy to grok and painless.

Multiple large monorepos in an organization are highly valuable imo, and should become more of a thing over time.
by zer00eyz | 2025-05-28 06:06:51+00:00
> One thing that this article didn't mention is that most development was done either on your development server running a datacenter (think ~50-100 cores)

I have done this for many small teams as well.

It remains pretty hard to get engineers to stop "thinking localy" when doing development. And with what modern hardware looks like (in terms of cost and density) it makes a lot of sense to find a rack some where for your dev team... It's easy enough to build a few boxes that can run dev, staging, test and what ever other on demand tooling you need with room to grow.

When you're close to your infrastructure and it looks that much like production, when you have to share the same playground the code inside a monorepo starts to look very different.

> managing large scale build systems ends up taking a team that works on the build system itself

This is what stops a lot of small teams from moving to monorepo. The thing is, your 10-20 person shop is never going to be google or fb or ms. They will never have large build system problems. Maintaining all of it MIGHT be someone's part time job IF you have a 20 person team and a very complex product. Even that would be pushing it.
by weaxme983 | 2025-05-28 06:06:54+00:00
I wrote a deep-dive tutorial on how to build a simple Retrieval-Augmented Generation (RAG) API using Python, LangChain, FastAPI, and PostgreSQL + pgvector.

The post covers:

- RAG system architecture for small-scale use cases - Embedding loading & storage with pgvector - Document splitting, embedding, and retrieval - Building a FastAPI interface for question answering

Code included. Ideal if you're experimenting with LLMs or want to ship a working prototype quickly.

https://vitaliihonchar.com/insights/python-rag-api

Happy to answer any technical questions or get your feedback!
by creatonez | 2025-05-28 06:07:12+00:00
WebGPU requires Vulkan or a Vulkan-like API to be present and not blacklisted. I wonder if they are fingerprinting the nuances of your system's Vulkan implementation? Not sure why WebGL based fingerprinting wouldn't be enough for this -- maybe because folks wishing to get around the fingerprinting have already made deterministic OpenGL renderers.
by rukuu001 | 2025-05-28 06:07:13+00:00
Some interesting points:

> Never again will we try to persuade the stupid person with reasons, for it is senseless and dangerous.

> The impression one gains is not so much that stupidity is a congenital defect, but that, under certain circumstances, people are made stupid or that they allow this to happen to them.

> And so it would seem that stupidity is perhaps less a psychological than a sociological problem

> it becomes apparent that every strong upsurge of power in the public sphere ... infects a large part of humankind with stupidity. ... The power of the one needs the stupidity of the other.

> ... one virtually feels that one is dealing not at all with a person, but with slogans, catchwords and the like

> This state of affairs explains why in such circumstances our attempts to know what ‘the people’ really think are in vain

> In the 1970s, Carlo Cipolla, a social psychologist, developed FIVE LAWS OF STUPIDITY. The term itself, he said, wasn’t a description of intellectual acuity, but of social responsibility
by SyzygyRhythm | 2025-05-28 06:07:17+00:00
You can prove it easily by induction. If Wm(n) is a mustard watch containing n micrograms of mustard, then it suffices to show that Wm(0) exists, and that if Wm(n) exists then Wm(n+1) must exist. Obviously a single additional microgram of mustard could not overload the structure of a watch. Therefore, Wm(10^100) or any other size must exist.
by nan60 | 2025-05-28 06:08:58+00:00
Intel's chips have become so absolutely awful in the last few years I also have no desire to buy one, even in laptops where power efficiency is so important. Maybe I'm just yelling at clouds but the whole P-core and E-core architecture seems off to me (and clearly Intel too), and having to implement new schedulers for virtually zero performance gain (just power efficiency) is really annoying. Especially as a Linux user where power efficiency isn't really the priority and battery life tends to suck anyway.
by bufferoverflow | 2025-05-28 06:12:05+00:00
But how do you classify a question as high vs low complexity? Some seemingly simple questions can turn out to be very very complex. For example, integer solution to

x³ + y³ + z³ = 42

took over a hundred years of compute time to find.

Or another seemingly simple equation with positive integers x,y,z

x/(y+z)+y/(z+x)+z/(x+y) = 4

requires elliptic curve knowledge, and the solution is huge

x = 154476802108746166441951315019919837485664325669565431700026634898253202035277999 y = 36875131794129999827197811565225474825492979968971970996283137471637224634055579 z = 4373612677928697257861252602371390152816537558161613618621437993378423467772036

(Solution is discussed here: https://www.quora.com/How-do-you-find-the-positive-integer-s...)
by kristopolous | 2025-05-28 06:13:00+00:00
I'm actually planning on abandoning Simon's infra soon. I want a multi-stream, routing based solution that is more aware of the modern API advancements.

The Unix shell is good at being the glue between programs. We've increased the dimensionality with LLMs.

Some kind of ports based system like named pipes with consumers and producers.

Maybe something like gRPC or NATS (https://github.com/nats-io). MQTT might also work. Network transparent would be great.
by friendzis | 2025-05-28 06:13:44+00:00
Exactly. Take your monorepo, split it into n repos by directory at certain depth from root, write very a rudimentary VCS wrapper script to sync all the repos in tandem and you have already solved a lot of pain points.

> E.g. it wouldn't be too hard to create "linked" PRs across repos for changes that span projects, with linked testing infrastructure

Bitbucket does this out-of-the box :)
Show HN: OpenPaper – Understand Papers Using AI (Open-Source)
by sabakhoj | 2025-05-28 06:13:57+00:00
Hi HN!

Open Paper allows you to annotate and understand your research papers with an AI copilot.

I wanted a paper-reading assistant that let met actually dig into papers in-place while benefiting from AI tooling. When it comes to studying, I'm not a fan of the typical chat interfaces that obfuscate uploaded files and turn them into black box 'content'. Hence, I've implemented a split-pane view.

To mitigate the risk of hallucinations, all AI responses come with grounded citations that refer back to the source material in-flow.

Some feature highlights:

- Actually read your papers in one place with an AI chat

- Generate an audio overview from any paper

- Find related papers (powered by OpenAlex)

- Every AI response comes with grounded citations

- Inline annotations

- Compose your knowledge base with uploaded papers

- Swap between GPT4 and Gemini2.5 Pro

- Shareable annotations

What are you looking for in a research assistant? Would love to get some thoughts / feedback on what I've built so far :). Thank you!

Check out the GitHub --> https://github.com/sabaimran/openpaper