frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: LocalGPT – A local-first AI assistant in Rust with persistent memory

https://github.com/localgpt-app/localgpt
160•yi_wang•5h ago•48 comments

The world heard JD Vance being booed at the Olympics. Except for viewers in USA

https://www.theguardian.com/sport/2026/feb/07/jd-vance-boos-winter-olympics
36•treetalker•11m ago•6 comments

Haskell for all: Beyond agentic coding

https://haskellforall.com/2026/02/beyond-agentic-coding
77•RebelPotato•5h ago•19 comments

SectorC: A C Compiler in 512 bytes (2023)

https://xorvoid.com/sectorc.html
269•valyala•13h ago•51 comments

Total surface area required to fuel the world with solar (2009)

https://landartgenerator.org/blagi/archives/127
33•robtherobber•4d ago•33 comments

Software factories and the agentic moment

https://factory.strongdm.ai/
208•mellosouls•16h ago•358 comments

Speed up responses with fast mode

https://code.claude.com/docs/en/fast-mode
172•surprisetalk•13h ago•163 comments

LLMs as the new high level language

https://federicopereiro.com/llm-high/
75•swah•4d ago•137 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
184•AlexeyBrin•18h ago•35 comments

Brookhaven Lab's RHIC concludes 25-year run with final collisions

https://www.hpcwire.com/off-the-wire/brookhaven-labs-rhic-concludes-25-year-run-with-final-collis...
76•gnufx•12h ago•60 comments

Stories from 25 Years of Software Development

https://susam.net/twenty-five-years-of-computing.html
176•vinhnx•16h ago•18 comments

Substack confirms data breach affects users’ email addresses and phone numbers

https://techcrunch.com/2026/02/05/substack-confirms-data-breach-affecting-email-addresses-and-pho...
31•witnessme•2h ago•8 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
328•jesperordrup•23h ago•98 comments

First Proof

https://arxiv.org/abs/2602.05192
138•samasblack•15h ago•81 comments

The Architecture of Open Source Applications (Volume 1) Berkeley DB

https://aosabook.org/en/v1/bdb.html
8•grep_it•5d ago•0 comments

Wood Gas Vehicles: Firewood in the Fuel Tank (2010)

https://solar.lowtechmagazine.com/2010/01/wood-gas-vehicles-firewood-in-the-fuel-tank/
35•Rygian•2d ago•10 comments

Show HN: I saw this cool navigation reveal, so I made a simple HTML+CSS version

https://github.com/Momciloo/fun-with-clip-path
86•momciloo•13h ago•18 comments

Vouch

https://twitter.com/mitchellh/status/2020252149117313349
78•chwtutha•4h ago•21 comments

Al Lowe on model trains, funny deaths and working with Disney

https://spillhistorie.no/2026/02/06/interview-with-sierra-veteran-al-lowe/
109•thelok•15h ago•24 comments

Start all of your commands with a comma (2009)

https://rhodesmill.org/brandon/2009/commands-with-comma/
593•theblazehen•3d ago•213 comments

Show HN: A luma dependent chroma compression algorithm (image compression)

https://www.bitsnbites.eu/a-spatial-domain-variable-block-size-luma-dependent-chroma-compression-...
41•mbitsnbites•3d ago•5 comments

FDA intends to take action against non-FDA-approved GLP-1 drugs

https://www.fda.gov/news-events/press-announcements/fda-intends-take-action-against-non-fda-appro...
115•randycupertino•8h ago•243 comments

The AI boom is causing shortages everywhere else

https://www.washingtonpost.com/technology/2026/02/07/ai-spending-economy-shortages/
315•1vuio0pswjnm7•19h ago•505 comments

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
907•klaussilveira•1d ago•277 comments

Where did all the starships go?

https://www.datawrapper.de/blog/science-fiction-decline
161•speckx•4d ago•245 comments

Selection rather than prediction

https://voratiq.com/blog/selection-rather-than-prediction/
36•languid-photic•4d ago•17 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
304•isitcontent•1d ago•39 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
314•dmpetrov•1d ago•158 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
149•videotopia•4d ago•48 comments

Microsoft account bugs locked me out of Notepad – Are thin clients ruining PCs?

https://www.windowscentral.com/microsoft/windows-11/windows-locked-me-out-of-notepad-is-the-thin-...
149•josephcsible•11h ago•186 comments
Open in hackernews

Chauffeur Knowledge and the Impending AI Crack-Up

https://ryanglover.net/blog/chauffeur-knowledge-and-the-impending-ai-crack-up
15•rglover•8mo ago

Comments

Terr_•8mo ago
> Chauffeur Knowledge

Going into this piece, I expected an analogy where the user is like an out-of-touch wealthy person, who builds a shallow model of the world from what they hear from their LLM chauffeur or golf-caddy.

That is something I fear will spread, as people give too much trust to the assistant in their pocket, turning to it at the expense of the other sources of information.

> That's when it hit me: this is going to change everything; but not in the utopian "everything is magical" sense, but in the "oh, God, what have we done" sense.

I think of it like asbestos, or leaded-gasoline. Incredibly useful in the right situation, but used so broadly that we regret it later. (Or at least, the people who didn't make their fortunes selling it.)

andy99•8mo ago
This makes me think of eternal September which I'd say the author would argue we've reached with respect to coding.
rglover•8mo ago
I wasn't thinking about that when I wrote this but that's an accurate take.
satisfice•8mo ago
The repeated use of the phrase “it works” is unhelpful. What the author means is “it appears to work.”

There is a vast difference between actually working and looking superficially like it works.

This is a massive testing problem.

rglover•8mo ago
That's the thing, though, it does work. Does it need a fair amount of hand holding to get there for non-trivial tasks? Yes. But if you have a basic skill set and some patience, you can get impressive results with a shocking number of common problems.

You're right that the "working" is superficial in a one-shot sense. But if you spend the time to nudge it in the right direction, you can accomplish a lot.

satisfice•8mo ago
As a software tester who takes pride in his vocation, I need to use words more carefully. I hope you will, too.

You are saying "it does work" for something that often seems to work, and for which you almost never carefully check to see that it is working (because that would be expensive). "Does" implies that it almost always actually works. That's not been my experience, nor, as I look around, does it seem to be anyone else's.

rglover•8mo ago
> you almost never carefully check to see that it is working (because that would be expensive)

I don't know about you, but I test everything thoroughly, whether I wrote it myself or used an LLM.

I think you're nitpicking over language here when what I said is clear. It can and does work with the proper amount of attention and effort, but that doesn't mean that it will just magically work with a one-shot attempt (though simpler code certainly can—e.g., "write me a debounce function").

As a software tester, you seem to be personalizing what I'm saying as encouraging developers to be a burden to you. Instead, I'm looking at it purely from a productivity standpoint. If your own team is just willy nilly dropping code that maybe works on your lap (with limited to no testing of their own), it might be time to find a new team. Being a tester in that type of environment will always be stressful, irrespective of how the code is written.

anon373839•8mo ago
I think this author makes the mistake, as many people do when they project AI trends forward, of ignoring the feedback mechanisms.

> Third, and I think scariest: it means that programming (and the craft of software) will cease to evolve. We'll stop asking "is there a better way to do this" and transition to "eh, it works." Instead of software getting better over time, at best, it will stagnate indefinitely.

“Eh, it works” isn’t good enough in a competitive situation. Customers will notice if software has weird bugs, is slow, clunky to use, etc. Some bugs can result in legal liability.

When this happens, other firms will be happy to build a better mousetrap to earn the business, and that’s an incentive against stagnation.

Of course, the FAANG type companies aren’t very competitive. But their scale necessitates serious engineering efforts: a bad fuck-up can be really bad, depending on what it is.

rglover•8mo ago
> Customers will notice if software has weird bugs, is slow, clunky to use, etc. Some bugs can result in legal liability.

I'd like to believe this, but some ~30 years into the popular internet, we still have bug-riddled websites and struggle to build simple software that's both usable (UX) and stable. You're right that if a company offers an SLA they're liable, but there's a wide range of software out there that isn't bound by an SLA.

That means that as this thing unfurls, we either get a lot of broken/low quality stuff, or even more consolidation into a few big player's hands.

> When this happens, other firms will be happy to build a better mousetrap to earn the business, and that’s an incentive against stagnation.

I agree this is likely, but the how is important. The hypothetical cost reduction of doing away with competent staff in favor of AI-augmented devs (or just agents) is too juicy for it to not become the norm (at least in the short-term). We're already seeing major players enforce AI-driven development (and in some cases, like Salesforce, impose hiring freezes under the assumption that AI is enough for most tasks).

The optimist in me agrees with what you're saying, but my gut take is that there will be a whole boatload of irrational, careless behavior before we see any meaningful correction.