MurphyA/hacker-news huggingface dataset:
by nextaccountic | 2026-03-11 04:12:10+00:00
> The rumors we hear have to do with projects inundated with more pull requests that they can review, the pull requests are obviously low quality, and the contributors' motives are selfish.

There's a way to handle this: put an automatic AI review of every PR from new contributors. Fight fire with fire.

(Actually, this was the solution for spam even before LLMs. See "A plan for SPAM" by Paul Graham. Basically, if you have a cheap but accurate filter (specially, a filter you can train for your own patterns), it should be enabled as a first line of defense. Anything the filter doesn't catch and the user had to manually mark as spam should become data to improve the filter)

Moreover, if the review detects LLM-generated content but the user didn't disclose it, maybe there should be consequences
by musicale | 2026-03-11 04:12:30+00:00
As you indicate, MIPS was widely used in computer architecture courses and textbooks, including pre-RISC-V editions of Patterson & Hennessy (Computer Organization & Design) and Harris & Harris (Digital Design and Computer Architecture.

In spite of the currently mediocre RISC-V implementations, RISC-V seems to have more of a future and isn't clouded by ISA IP issues, as you note.
by krackers | 2026-03-11 04:12:56+00:00
What level is copy pasting snippets into the chatgpt window? Grug brained level 0? I sort of prefer it that way (using it as an amped up stackoverflow) since it forces me to decompose things in terms of natural boundaries (manual context management as it were) and allows me to think in terms of "what properties do I need this function to have" rather than just letting copilot take the wheel and glob the entire project in the context window.
by GorbachevyChase | 2026-03-11 04:13:39+00:00
China did users a solid and Qwen is a thing, so the scenario where Anthropic/OpenAI/Google collude and segment the market to ratchet prices in unison just isn’t possible. Amodei talking about value based pricing is a dream unless they buy legislation to outlaw competitors. Altman might have beat them to that punch with this admin, though. Most of us are operating on 10-40% margins. Usually on the low end when there aren’t legal barriers. The 80-99% margins or rent extraction rights SaaS people expect is just out of touch. The revenue the big 3 already pull in now has a lot more to do with branding and fear-mongering than product quality.
by shiroiuma | 2026-03-11 04:13:46+00:00
And what about people who eat actual raw egg? I routinely eat freshly-made cake batter (made with raw eggs; I just clean the bowl, I don't actually gobble tons of raw cake batter), for instance. It's perfectly safe because I live in a country where they actually check eggs for salmonella before selling them and people routinely eat raw eggs on top of things.
by alwillis | 2026-03-11 04:14:12+00:00
> I doubt a highly tuned Linux box will be slower than the equivalent FreeBSD one.

That tracks but there's been a lot of work being done on FreeBSD's stack as well.

Most people are aware about the contributions Netflix has made to FreeBSD; they say their FreeBSD-based CDN streams terabytes per second [1].

In addition to the basic network stack, FreeBSD can load additional stacks like RACK TCP [2] stack (using Recent ACK, PRR, etc.) that can be loaded as a module and selected per-socket or as the system default. This is the re-written stack that Netflix uses after they helped develop it.

It seems that FreeBSD is kind of a testbed for new network implementations like Netgraph [3], a graph-based networking subsystem that enables modular, real-time packet processing inside the kernel and Network Offload and Socket Splicing (SO_SPLICE) [4] that enables kernel-level TCP proxying, resulting in reduced CPU overhead and eliminating unnecessary data copies.

I'm not usually into networking but this stuff sounds very interesting.

[1]: "Case Study: Maintaining the World’s Fastest Content Delivery Network at Netflix on FreeBSD" - https://freebsdfoundation.org/netflix-case-study/ (PDF).

[2]: "The RACK-TLP Loss Detection Algorithm for TCP" - https://datatracker.ietf.org/doc/html/rfc8985

[3]: "Inside FreeBSD Netgraph: Behind the Curtain of Advanced Networking" - https://klarasystems.com/articles/inside-freebsd-netgraph-ad...

[4]: https://klarasystems.com/articles/network-offload-and-socket...
by musicale | 2026-03-11 04:14:59+00:00
This is largely contradicted by the (pre RISC-V) MIPS editions of Patterson & Hennessy, Harris & Harris, etc., which teach you how to design a MIPS datapath (at the gate level.)

Regarding silicon implementations, consider that 1) you can synthesize it from HDL/RTL designs using modern CAD tools, and 2) MIPS was originally designed to be simple enough for grad students to implement with the primitive CAD tools of the 1980s (basically semi-manual layout).
by djrnz | 2026-03-11 04:15:06+00:00
Thanks for the kind words, shintomura!

That "hacker mindset" is really what kept me sane during the first few weeks post-layoff. You’re spot on about the privacy—handling resumes means handling very personal data, so keeping PII on-device was a non-negotiable for me from day one.

Glad to hear you're a Gemini fan too. I chose Gemini Pro specifically because the context window and speed made the resume tailoring much more accurate compared to other models I benchmarked.

Really appreciate the support, and good luck with your own personal projects!
by rtfeldman | 2026-03-11 04:15:58+00:00
I maintain a ~250K LoC Zig compiler code base [0]. We've been through several breaking Zig releases (although the code base was much smaller for most of that time; Writergate is the main one we've had to deal with since the code base crossed the 100K LoC mark).

The language and stdlib changing hasn't been a major pain point in at least a year or two. There was some upgrade a couple of years ago that took us awhile to land (I think it might have been 0.12 -> 0.13 but I could be misremembering the exact version) but it's been smooth sailing for a long time now.

These days I'd put breaking releases in the "minor nuisance" category, and when people ask what I've liked and disliked about using Zig I rarely even remember to bring it up.

[0]: https://github.com/roc-lang/roc
by kindkang2024 | 2026-03-11 04:17:29+00:00
Great find — Satisfying to know ⍼'s origin story.

This reminds me of another Unicode block with ancient origins: the 64 I Ching hexagrams (U+4DC0–U+4DFF). Unlike ⍼, their meaning has been documented for 4,000 years — yet they carry their own encoding surprise. Unicode actually follows the traditional King Wen sequence: U+4DC0 is ䷀ (Heaven, #1) and U+4DC1 is ䷁ (Earth, #2). Interestingly, this is different from the binary Fu Xi arrangement formalized by Shao Yong (邵雍, 1011–1077), where ䷁ (000000) comes first and ䷀ (111111) last — the very diagram that captivated Leibniz in 1703 as a mirror of binary arithmetic [1][2]. Two valid orderings, encoding two different philosophies of where to begin: with pure creation, or with pure potential.

By the way, DNA also produces exactly 64 codons (4³ = (2²)³ = 2⁶) — the same number. Some have even noted functional echoes: DNA has start and stop codons that initiate and terminate translation; the hexagrams have corresponding structural counterparts [3]. Probably coincidence. Probably.

[1] https://leibniz-bouvet.swarthmore.edu/letters/letter-j-18-ma...
[2] https://leibniz-translations.com/binary
[3] https://www.goodreads.com/book/show/78369.The_I_Ching_and_th...
by willrshansen | 2026-03-11 04:17:33+00:00
This feels like two steps up from a highly customized vim config. But I want one step up.

I want to be able to piece together an editor from modular task specific executables. Different programs for file searching, input mapping, buffer modification and display, etc.
Probably similar to how LSPs are already separated from most editors.

One step less hardcore than writing a whole editor.

Anyone know of any existing projects along these lines?
by JumpCrisscross | 2026-03-11 04:17:53+00:00
> we’re finally admitting that all of that leetcode screening and engineer quality gating was a farce, or it wasn’t, and you’re wrong

We’re admitting a bit of both. Offshoring just became more instantaneous, secure and efficient. There will still be folks who overplay their hand.

Macroeconomically speaking, I don’t see why we need more software engineers in the future than we have today, and that’s probably a conservative estimate.
by scuff3d | 2026-03-11 04:18:20+00:00
"Of course, it's not that it cannot do all the work, but considering user experience and those hardware limitations, the experience, I think, differs significantly from mainstream products..."

I worked in retail for a decade, a lot of that was selling computers. The vast majority of what people buy computers for could be done a toaster. You don't exactly need top end specs to browse the internet, reply to emails, and write the occasional document.
by ogou | 2026-03-11 04:22:39+00:00
It's more than time. That program requires explicit authorization from them. It's designed for larger corporate integrations, not developer experiments. I seriously I doubt I would get approved even if I went through all the paperwork. It's not just a matter of just signing up for an API key.

As for your plan, gathering user data is probably the main thing they want to prevent.
by HalfEmptyDrum | 2026-03-11 04:23:44+00:00
If you read this: https://www.williamjbowman.com/blog/2026/03/05/against-vibes...

you will notice that this may not even be the correct workflow (depending on what you want to achieve of course. If you just verifiable web-dev, you can keep on doing what you do; even then there may be counter-args).

Generally, I noticed that when I went back to my old work flow of writing rough pseudo code (which aggregated doesn't add a lot of time), I was more efficient. I could then let the LLM translate the pseudo code.

What I was missing though was that the LLM also suggested changes to my pseudo code in my pseudo code style as well.

This is why I built the following skill (you can use /translate then):

https://github.com/HalfEmptyDrum/Pseudo-Code-Flow

I have written about it here:

https://news.ycombinator.com/item?id=47331647
by userbinator | 2026-03-11 04:25:23+00:00
NetBurst was supposed to be the application of RISC principles to x86 taken to its extreme (ultra-long pipelines to reduce clock-to-clock delay, highest clock speed possible --- basically reducing work-per-clock and hoping that reduces complexity enough to increase clock speed to compensate.) The ALU was 16 bits, "double pumped" with the carry split between the two, which lead to 32-bit ALU operations that don't carry between the lower and upper halves actually finishing a clock cycle faster than those with a carry.

https://stackoverflow.com/questions/45066299/was-there-a-p4-...
by montyanne | 2026-03-11 04:25:35+00:00
I was using this as a demo project for playing around with code generation tools, so it’s really not in a great state and entirely AI written, but I can share a link here when I get a chance.

My initial stab was a rust port targeting esp32 Heltec V4 (since it has some niceties like tokio) with Reticulum communication over serial, BLE, WiFi and LoRA. The serial interface was sort of working, but frankly debugging using rnsd/nomadnet was infuriating (there’s no tools just to easily see messages over the wire!).

I’ve moved onto a build system that can also target the SEEED Wio Tracker using no_std, but it’s been… messier. AI tooling doesn’t quite have the context length for big migrations like that yet.
by Loughla | 2026-03-11 04:27:48+00:00
There is a clear difference between "I don't want to look at the pipeline" and "pipelines have an established track record of cutting corners and avoiding regulation wherever possible which leads to leaks and spills, leaks and spills cause irreparable damage to the environment including the environment in the middle of our community, and the company is attempting to exploit our already historically exploited community"
by ProllyInfamous | 2026-03-11 04:28:00+00:00
>What do you do with this living space without a TV?

My main social space is my front porch, which is a semi-enclosed dogrun with ample seating (no TV). My "living room" doesn't have a couch, which naturally forces you towards seating (aforementioned outside). There is a small table, with two chairs only; bookshelves, artwork, and projectspace mostly for standing room only.

Not really much of a socialite, but I really don't like TVs (nor people in my small space).

>current generation feels ... about smartphones

I don't use those, either. Hate that everything is now an app (including parking).

old_man_yells_at_clouds.gif (early forties)
by TimorousBestie | 2026-03-11 04:28:09+00:00
> The core fiction that enables the university to work is a dedication to 'truth' and progress through discussion. . . . That breaks down when there isn't open discussion on campus.

Umberto Eco, “Ur-Fascism”: “Distrust of the intellectual world has always been a symptom of Ur-Fascism, from Goering’s alleged statement (“When I hear talk of culture I reach for my gun”) to the frequent use of such expressions as “degenerate intellectuals,” “eggheads,” “effete snobs,” “universities are a nest of reds.””

> The left now holds a place of orthodoxy in the universities and power structures.

Eco: “Thus at the root of the Ur-Fascist psychology there is the obsession with a plot, possibly an international one. The followers must feel besieged.”

> Whether the 'right' can break it back into an enforced balance is yet to be seen. . . . The opposition needs to “live” somewhere!

Eco: “However, the followers must be convinced that they can overwhelm the enemies. Thus, by a continuous shifting of rhetorical focus, the enemies are at the same time too strong and too weak.”
by satisfice | 2026-03-11 04:28:58+00:00
It’s called testing. And from the reports and comments, there doesn’t seem to be much of it happening. The reason is: it’s quite expensive to do well.

I find that for every hypothesis I might have to run a thousand prompts to collect enough data for a conclusion. For instance, to discover how reliably different models can extract noun phrases from a text: hours of grinding. Even so that was for a small text. I haven’t yet run the process on a large text.
by boomlinde | 2026-03-11 04:31:26+00:00
I stopped updating the compiler at 0.14 for three projects. Getting the correct toolchain is part of my (incremental) build process. I don't use any external Zig packages.

I think one of the more PITA changes necessary to get these projects to 0.15 is removing `usingnamespace`, which I've used to implement a kind of mixin. The projects are all a few thousand LOC and it shouldn't be that much trouble, but enough trouble that none of what I gain from upgrading currently justify doing it. I think that's fine.
by isodev | 2026-03-11 04:31:50+00:00
I don’t think you’re overreacting.

Great care and attention is required for critical system components and LLMs lack both.

Not to mention the copyright risks - do we really want a piece of code that can’t be licensed or turns out to be a verbatim copy from another project to end up in the kernel or something? (No, the answer is we don’t want.).
by dasil003 | 2026-03-11 04:31:54+00:00
It's also a function of young ambitious people just following the money over time. Finance has grown and grown and grown because it's the easiest place to skim the cream. Combine that with the fact that it's transferable from company to company and it's clear why the trend. Obviously the only innovation these people are capable of is financial innovation (repackaging derivatives, ever-more-convoluted deal structures to snow people, etc), but that doesn't much matter as long as there is a sufficient base of enough new companies with actual innovations sprouting up that it provides enough grist for the finance mill.
by aleyan | 2026-03-11 04:32:26+00:00
Yes, the angle above the horizon is usually what is most useful because it is used to find something small but visible. In the case of my ascii moon, the angle below the horizon, is there to explain why something is not visible. The Moon is large enough that people can easily find it on their own if it is not obstructed by the Earth itself.

Consider the Moon as viewed from NYC at time of comment [0], it is hiding below the horizon. If you were to look at my website and then at the sky you might become upset that I am reporting the shape of the moon, but obviously it can't be seen. Hence why the website reports the angle below the horizon roughly half the time it isn't visible.

Adding Azimuth and Elevation when the Moon is above the horizon would be for completionism only and not the real enterprise use-cases served by ANSI compliant renderings of the Moon.

[0] https://aleyan.com/projects/ascii-side-of-the-moon/?lat=40.7...
by aprdm | 2026-03-11 04:33:07+00:00
Why read code when you are getting results fast ? See https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16d...

I am not kidding. People don't seem to understand what's actually happening in our industry. See https://www.linkedin.com/posts/johubbard_github-eleutherailm...
by kalterdev | 2026-03-11 04:33:28+00:00
Acme [1]

It steps down from “customize everything” mantra, believing that approach leaves users with an underdeveloped essential system. But it still has two major API: one for windows manipulation [2], the other for text-based integration with the surrounding system via plumber [3].

All textual CLI tools (that is, those without pseudographics) work by default and are the heart of its style.

I use Acme for everything except web browsing (although most links are still managed by Acme).

[1]: http://youtu.be/dP1xVpMPn8M

[2]: http://9p.io/magic/man2html/4/acme

[3]: http://9p.io/sys/doc/plumb.html
by Retric | 2026-03-11 04:33:42+00:00
> making for a near industry-standard 33% cut.

LIES, from that link:

“On average, 67% of all spending in experiences supports OR goes to developers.” Supports here does not actually mean they get paid that money.

Later it mentions the actual money going to developers as: “This enables us to return 28%* directly to the developers.” And yes that 28% includes an asterisk.

That’s a 72% cut to the platform.
by nextaccountic | 2026-03-11 04:34:45+00:00
> Kahneman’s whole framework points the same direction. Most of what people call “reasoning” is fast, associative, pattern-based. The slow, deliberate, step-by-step stuff is effortful and error-prone, and people avoid it when they can. And even when they do engage it, they’re often confabulating a logical-sounding justification for a conclusion they already reached by other means.

Some references on that

https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow

https://thedecisionlab.com/reference-guide/philosophy/system...

System 1 really looks like a LLM (indeed completing a phrase is an example of what it can do, like, "you either die a hero, or you live enough to become the _"). It's largely unconscious and runs all the time, pattern matching on random stuff

System 2 is something else and looks like a supervisor system, a higher level stuff that can be consciously directed through your own will

But the two systems run at the same time and reinforce each other
by cortesoft | 2026-03-11 04:35:04+00:00
Well, the conversion process into the JSON representation is going to take CPU, and then you have to store the result, in essence doubling your cache footprint.

Doing it on demand still utilizes their cached version, so it saves a trip to the origin, but doesn’t require doubling the cache size. They can still cache the results if the same site is scraped multiple times, but this saves having to cache things that are never going to be requested.

Cache footprint management is a huge factor in the cost and performance for a CDN, you want to get the most out of your storage and you want to serve as many pages from cache as possible.

I know in my experience working for a CDN, we were doing all sorts of things to try to maximize the hit rate for our cache.. in fact, one of the easiest and most effective techniques for increasing cache hit rate is to do the OPPOSITE of what you are suggesting; instead of pre-caching content, you do ‘second hit caching’, where you only store a copy in the cache if a piece of content is requested a second time. The idea is that a lot of content is requested only once by one user, and then never again, so it is a waste to store it in the cache. If you wait until it is requested a second time before you cache it, you avoid those single use pages going into your cache, and don’t hurt overall performance that much, because the content that is most useful to cache is requested a lot, and you only have to make one extra origin request.
by dangus | 2026-03-11 04:35:54+00:00
The MacBook Pro is essentially a really conservative packaging choice for people who buy the plain M5 chip. They are buying the size/weight/thickness that's required to support the M5 Max, and Apple could probably even get an M5 Max into a thinner/lighter system.

The lineup is a little bit odd because of this, and I bring up the Zephyrus as something of a demonstration of the idea. When you by a MacBook Pro 14" M5, you buy an integrated graphics-class system and essentially you're getting a laptop that's the exact same size as a laptop you can get packed with a 100 watt RTX 5070Ti. Your CPU doesn't even really need a cooling fan and yet the computer it's inside of is the same size as a gaming machine with a dedicated GPU.

Obviously I don't mean to say that Apple should make a laptop that sacrifices fan noise to that degree, but the same idea is happening in their lineup:

You buy a M5 MacBook Pro, you're getting a laptop thick and heavy enough to thermally support a much higher tier system that isn't even on the same planet in terms of performance (an M5 Pro or Max system).

Here's how I would change the lineup:

MacBook Neo is your entry level, stays the same.

MacBook Air 13" and 15" handle your everyday computing very well, they stay the same.

MacBook Pro 14" and 16" with the M5 chip gets a thinner and lighter chassis, closer in size/weight to the MacBook Air. These systems are there to give you the extra I/O and better quality screen/other additional "pro" features that you get with the Pro lineup but for someone who is only doing medium-intensity tasks.

MacBook Pro 14" and 16" with Pro/Max chips remain roughly the same.

Bonus points: Apple could also more enthusiastically enter the PC gaming market (>900 million customers) if they put out something like the MacBook Neo but instead of targeting Chromebooks they would target low to mid range gaming laptops like Lenovo LOQ. Do a lot of the same cost-cutting as the MacBook Neo: no haptic trackpad (gamers don't need it), worse speakers, lower resolution screen (good for games), take the Steam Deck route of using an SD card for expandable storage and keep profit margins by continuing to solder the internal storage in and limit the size to ensure pros only buy the more expensive MacBook Pro lineup. Launch that along with a Steam Deck competitor handheld.
by LeFantome | 2026-03-11 04:35:59+00:00
First, x86-64 also has “extensions” such as avx, avx2, and avx512. Not all “x86-64” CPUs support the same ones. And you get things like svm on AMD and avx on Intel. Remember 3DNow?

X86-64 also has “profiles” which tell you what extensions should be available. There is x86-64v1 and x86-64v4 with v2 and v3 in the middle.

RVA23 offers a very similar feature-set to x86-64v4.

You do not end up with a mess of extensions. You get RVA23. Yes, RVA23 represents a set of mandatory extensions. The important thing is that two RVA23 compliant chips will implement the same ones.

But the most important point is that you cannot “just use x86-64”. Only Intel and AMD can do that. Anybody can build a RISC-V chip. You do not need permission.