frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Pill to treat pancreatic cancer hailed as 'biggest breakthrough in decades'

https://www.theguardian.com/society/2026/nov/20/pill-pancreatic-cancer-breakthrough-daraxonrasib
583•rafaelc•1d ago•140 comments

Lean verification of the Riemann Hypothesis

https://leanprover-community.github.io/blog/posts/riemann-hypothesis/
820•g-b-r•10h ago•662 comments

Inkling-2-Mini in 5.4 GB Memory

https://github.com/ShinMegamiBoson/lookatmyquant
348•k__•7h ago•91 comments

Brazil's tax authority open-sources its tax calculator on GitHub under MIT

https://www.gov.br/receitafederal/pt-br/assuntos/noticias/2026/novembro/receita-federal-publica-p...
745•dvaplima•4d ago•239 comments

Detonating a pile of lead azide

https://www.science.org/content/blog-post/detonating-huge-pile-lead-azide-really
515•beginning_end•11h ago•345 comments

PcapAnalyzer – self-hosted pcap analyzer with 27 problem detectors

https://github.com/sebaandrada-cell/PcapAnalyzer
49•sebaandrada•3h ago•5 comments

Getting the mind to steer the body to steer you

https://notnottalmud.substack.com/p/getting-the-mind-to-steer-the-body
143•jger15•1d ago•52 comments

My monitor was cutting my download speed by 75%

https://blog.tymscar.com/posts/studiodisplayethernet/
482•soheilpro•14h ago•231 comments

Advice for the next 100 Rust GUIs

https://linebender.org/blog/next-100-guis/
78•raphlinus•4h ago•7 comments

PostgreSQL Extensions in Go

https://jespino.github.io/gopgext/
117•valyala•8h ago•20 comments

Pandex – Official European Law for AI Agents, over MCP

https://www.pandex.io
27•vasie•4h ago•4 comments

The Emergence of Inequality in the Czech Corded Ware Culture

https://www.jna.uni-kiel.de/index.php/jna/article/view/1560/1746
26•marojejian•4h ago•11 comments

Inkling 2 Mini

https://thinkingmachines.ai/news/inkling-2-mini/
1384•jasondavies•1d ago•280 comments

Tasklet (YC P26) Is Hiring Product and Agent Infra Engineers

https://tasklet.ai/careers
1•mayop100•4h ago

Windows has two settings that bring work back after restart, both off by default

https://www.makeuseof.com/windows-can-bring-your-work-back-after-restart/
34•surprisetalk•2d ago•31 comments

Upload2Shell (CVE-2026-125396)

https://pwn.ai/upload2shell
76•f311a•6h ago•29 comments

Tropical Rainforests Species may be surprisingly young

https://phys.org/news/2026-11-species-tropical-rainforests-young-emergence.html
40•PaulHoule•4d ago•18 comments

Show HN: Zero C# – C# without a runtime or GC

https://onurgumus.github.io/zero-csharp/index.html
126•reverseblade2•9h ago•96 comments

Bolt's Scooters Are Becoming Accessibility Sensors

https://geoawesome.com/bolt-scooters-accessibility-mapping-wheels4wheels/
31•chippy•4d ago•37 comments

Verification files for the Lean proof of the Riemann Hypothesis

https://math.mit.edu/~drew/grh/
92•Bluestein•9h ago•36 comments

Exponential Behavior in Magic: The Gathering

https://levineuwirth.org/essays/exponential-magic/
89•neuwirth•3d ago•62 comments

Shaping the Loops, Closing the Loops

https://revyl.com/blog/pattern-engineering/
3•based0x10•3d ago•2 comments

Sandwich Simulator

https://stulle.app/
5•subdomain•1h ago•0 comments

RCE in Gnupg

https://lists.gnupg.org/pipermail/gnupg-announce/2026q4/000517.html
231•gdgghhhhh•16h ago•93 comments

LLMs can read and write executables byte by byte from a hex dump

https://sgiannopoulos.github.io/blog/machine-code-programming/
190•fortran77•3d ago•123 comments

Why there are still no non-WebKit browsers on iOS

https://blog.mozilla.org/en/mozilla/internet-policy/apple-ios-browser-engine-rules/
480•lapcat•1d ago•269 comments

Ask HN: I have been unemployed for 2y. 15 years of experience, US. What to do?

609•LetThingsBeDiff•1d ago•678 comments

I'm quite pleased by the tech architecture of my art website

https://klauria.tech/klauria-art/
147•evakhoury•1d ago•33 comments

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
2389•jasondavies•1d ago•1160 comments

International UN talks on controlling use of autonomous weapons collapse

https://www.theguardian.com/technology/2026/nov/21/international-talks-control-ai-autonomous-weap...
32•nephihaha•2h ago•4 comments
Open in hackernews

Making code last a long time

https://twitter.com/jonathan_blow/status/1923414922484232404
28•robinhouston•1y ago

Comments

turtleyacht•1y ago
Make and maintain the virtual machine that runs your program, which executes custom instructions.

See uxn and justification: https://wiki.xxiivv.com/site/now_lie_in_it.html

And https://100r.co/site/story.html

kevmo314•1y ago
> The way you make code last a long time is you minimize dependencies that are likely to change and, to the extent you must take such dependencies, you minimize the contact surface between your program and those dependencies.

A lot of value is driven from those dependencies though. Zapier as a pointed example: Zapier sans dependencies is ... well I don't even know. So sure, you could avoid dependencies at all cost, but at some point you might end up deleting the reason someone else wants to use your code in the first place.

Of course, if you're writing code only for yourself that will totally work, but most professional software engineers are not -- it's a balance and it's not fair to say all they have to do is stop writing glue code.

j45•1y ago
Your example of Zapier dependence resonates - being sure to put a simple layer between your code and Zapier is the critical component.

The code makes the same call to a Zapier type command but it could be routed to Zapier today, and somewhere else in the future.

This can take a nominal amount of time longer than integrating Zapier directly.

It could be a couple more tables to setup and manage, or it can be done in the code somewhere.

caseyohara•1y ago
I've been working on the same product for ~13 years and I can confidently say the most important thing to ensure the longevity and long-term maintainability of a codebase is aggressive minimization of dependencies.

Engineering is all about compromises. If near-term velocity is more important to you than long-term evolution and maintainability, then go ahead and use all of the dependencies if it allows you to ship faster. But that is a form of technical debt that you will have to pay down eventually.

QuadrupleA•1y ago
What are you doing with Zapier that you couldn't do with your own code, or carefully curated small set of libraries? For networked services, the REST APIs of popular providers (Stripe, AWS, etc.) are usually kept backwards compatible for a long time.
henning•1y ago
I was about to comment how easy Zig makes it to make platform layers where the right code for an OS is compiled at compile-time and AFAIK there is no runtime cost, it's basically conditional compilation. But the Zig language itself is incredibly unstable and code you write now probably won't compile a year from now.
taylorallred•1y ago
This seems like another case where jblow's opinions are guided by his experience as a game dev. Games can be "finished" and never touched again. I think I mostly agree with him that software could be made to be timeless to some degree. But, in the world of web apps and saas, the culture is to offload much of the work to third party libraries/APIs which locks you into a never-ending cycle of dependency management. I don't know if this culture is totally necessary (maybe to ship fast and keep up with security updates?), but in a world where users expect software to be constantly improving you can't expect anything to be "done". Maybe you could get close if you built everything in-house, but even still you have to keep up with security flaws.
QuadrupleA•1y ago
From experience - if you look at the "security flaws" in detail that updates and patches address, an app with good dependency hygiene is rarely vulnerable to them, and doesn't need the purported fixes. So in those cases it's mostly a comforting mirage that your software is improving as you do "security updates" on your libraries and dependencies, except in rare cases.

And, security updates should not break your app! What breaks your app are feature changes, API changes, and the like, which is a breach of backwards compatibility and IMHO kind of lazy and hostile on the part of the library developers. It creates massive unnecessary work for developers, and unnecessary bugs and problems for millions of end users.

boznz•1y ago
Software in a closed ecosystem should run for the life of that ecosystem, an example would be Firmware on a non-connected device. eg the ECU in my car from 1991.
juancn•1y ago
I kind of agree. There's another world, where software lasts a really long time, it's a much better world, but just a few of us get to live in it.

Building tools for other engineers is where it's at, the library maintainers for long lived libraries, like libc or any collections library.

If you get a sorting algorithm in a mainstream language library, it will likely live forever (or forever-ish in software terms).

The harder the problem you solve (in the math sense) the more likely that if you craft that code properly and carefully, it will outlive you.

burnt-resistor•1y ago
Well, when I was in school, the goals were wide compatibility and portability. I was writing network C code in the 00's that could run without any changes on Windows, Linux, FreeBSD, HP-UX, AIX, SGI, SCO, and Solaris.

Code only "rots" when its dependencies rot from assholes who churn the language or break API promises. These low expectations lead to normalization of deviancy that churn without clear and present value is "okay", when it's merely job security or coding theater to appease others that everything must be touched and changed constantly or otherwise it's "broken".