frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Outages reported at Bank of America, Chase, U.S. Bank, Wells Fargo and Zelle

https://apnews.com/article/bank-outage-chase-wells-fargo-truist-50fee2693c22f597fa6ca51a97ef2cda
395•samk3nny•2h ago•279 comments

Software is breaking down at a systemic level

https://www.breck-mckye.com/blog/2026/11/software-is-breaking-down-at-a-systemic-level/
219•zero_shift•2h ago•121 comments

Grazing sheep in fields with solar arrays

https://news.cornell.edu/stories/2026/10/sheep-grazing-solar-fields-offers-farmers-economic-ecolo...
132•PaulHoule•3h ago•107 comments

Jiff 1.0: A datetime library for Rust

https://burntsushi.net/jiff/
207•burntsushi•3h ago•46 comments

Frame – 31.5" color ePaper display

https://trmnl.com/blog/introducing-frame
151•geerlingguy•4h ago•86 comments

Squircles

https://linebender.org/wiki/curves/squircle/
22•raphlinus•12h ago•9 comments

The Secret ThinkPad Powerbutton Code to Bring Dead Laptops Back to Life (2007)

https://masnick.com/posts/the-secret-thinkpad-powerbutton-code-to-bring-dead-laptops-back-to-life/
263•sammatilda•8h ago•106 comments

Aristotle Expands into Rust

https://www.harmonic.fun/news/aristotle-rust-verification/
58•maufl•2h ago•33 comments

Michael Mann's 'Heat' Copyright Fight Turns on a Deal with Himself

https://copyrightlately.com/michael-mann-heat-copyright-termination/
45•speckx•2h ago•16 comments

Launch HN: Axonnic (YC F26) – Sleeves that track fingers and estimate force

2•arshpatankar•3m ago•0 comments

Giant Roadside Attractions Face Mounting Costs and an Uncertain Future

https://www.nytimes.com/2026/11/08/world/canada/roadside-attractions-giant-dinosaur.html
18•bookofjoe•6d ago•14 comments

Many of Amazon’s Black Friday and Cyber Monday “deals” offered no savings

http://groundworkcollaborative.org/news/amazons-decoy-deals-groundwork-investigation-reveals-near...
691•DeepLogin•6h ago•427 comments

How to Intercept HTTP/3 Traffic: QUIC and Qpack

https://interceptsuite.com/blog/intercept-http3-traffic-quic-qpack-explained/
14•anof-cyber•1h ago•0 comments

Jolt – Clojure that speaks C

https://jolt-lang.net/
53•michaelsbradley•4h ago•15 comments

How to make almost anything

https://pub.cba.mit.edu/863.26/site/
786•o4c•14h ago•130 comments

OpenAI: Strengthening the fight against online child sexual abuse

https://openai.com/index/strengthening-online-child-safety/
47•rossant•2h ago•73 comments

The Origins of the Placenta

https://www.caltech.edu/about/news/uncovering-the-hidden-origins-of-the-placenta
8•gmays•3d ago•1 comments

Microsoft blames monster email outage on software defect introduced in July fix

https://www.theregister.com/saas/2026/11/16/microsoft-blames-monster-email-outage-on-software-def...
82•Bender•7h ago•64 comments

Nvidia was in trouble before the Jensen Huang mess

https://www.wired.com/story/nvidia-was-already-in-trouble-before-the-jensen-huang-mess/
183•Brajeshwar•5h ago•174 comments

OOS – an open operating system for the Rigol Scopes

https://www.eevblog.com/forum/testgear/oos-an-open-operating-system-for-the-rigol-scopes/
114•qwezxcrty•2d ago•35 comments

Smallest possible nopert polyhedra: the Septopert

https://github.com/tom7/noperts/blob/main/septopert.md
41•RebelPotato•2d ago•3 comments

Interpreting claims that a theorem is correct because it was checked in Lean

https://xenaproject.wordpress.com/2026/11/12/and-the-proof-is-checked-in-lean/
259•matt_d•12h ago•113 comments

Coffeehouses and the Rise of Science [pdf]

https://www.monirbounadi.com/Bounadi_JMP.pdf
162•Michelangelo11•9h ago•98 comments

Just 400 US Data Centers Use More Electricity Than Michigan

https://www.wired.com/story/data-centers-use-more-electricity-than-michigan/
67•Betelbuddy•2h ago•52 comments

A 512 KiB binary message teaching chess without a shared language

https://artemlegotin.com/golden-board/
38•legotin•5h ago•7 comments

First phase of embedded assessments at OpenAI

https://openai.com/index/our-first-phase-of-embedded-assessments/
19•dvaplima•4h ago•4 comments

Researchers track whole body movement with just a smartwatch

https://news.cornell.edu/stories/2026/11/researchers-track-whole-body-movement-just-smartwatch
188•PaulHoule•3d ago•64 comments

Psychic: Like fzf but learns from your actions

https://klauria.tech/psychic/
23•articulatepang•4h ago•7 comments

How Billions in Safe Insurance Money Is Being Bet on A.I. Debt

https://www.nytimes.com/2026/11/16/business/insurance-ai-debt.html
42•syllablehq•3h ago•10 comments

The Active Directory Era Is Finally Over

https://infisical.com/blog/active-directory-machine-identity
92•FinnLobsien•6h ago•63 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".