frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

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

https://spillhistorie.no/2026/02/06/interview-with-sierra-veteran-al-lowe/
50•thelok•3h ago•6 comments

Hoot: Scheme on WebAssembly

https://www.spritely.institute/hoot/
115•AlexeyBrin•6h ago•20 comments

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

https://openciv3.org/
811•klaussilveira•21h ago•246 comments

Stories from 25 Years of Software Development

https://susam.net/twenty-five-years-of-computing.html
49•vinhnx•4h ago•7 comments

The AI boom is causing shortages everywhere else

https://www.washingtonpost.com/technology/2026/02/07/ai-spending-economy-shortages/
91•1vuio0pswjnm7•7h ago•102 comments

Reinforcement Learning from Human Feedback

https://rlhfbook.com/
72•onurkanbkrc•6h ago•5 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
1053•xnx•1d ago•600 comments

Start all of your commands with a comma (2009)

https://rhodesmill.org/brandon/2009/commands-with-comma/
470•theblazehen•2d ago•174 comments

U.S. Jobs Disappear at Fastest January Pace Since Great Recession

https://www.forbes.com/sites/mikestunson/2026/02/05/us-jobs-disappear-at-fastest-january-pace-sin...
45•alephnerd•1h ago•14 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
197•jesperordrup•11h ago•67 comments

Selection Rather Than Prediction

https://voratiq.com/blog/selection-rather-than-prediction/
8•languid-photic•3d ago•1 comments

Speed up responses with fast mode

https://code.claude.com/docs/en/fast-mode
9•surprisetalk•1h ago•2 comments

France's homegrown open source online office suite

https://github.com/suitenumerique
537•nar001•5h ago•248 comments

Coding agents have replaced every framework I used

https://blog.alaindichiappari.dev/p/software-engineering-is-back
204•alainrk•6h ago•311 comments

A Fresh Look at IBM 3270 Information Display System

https://www.rs-online.com/designspark/a-fresh-look-at-ibm-3270-information-display-system
33•rbanffy•4d ago•6 comments

72M Points of Interest

https://tech.marksblogg.com/overture-places-pois.html
26•marklit•5d ago•1 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

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

Software factories and the agentic moment

https://factory.strongdm.ai/
63•mellosouls•4h ago•68 comments

Where did all the starships go?

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

Show HN: Kappal – CLI to Run Docker Compose YML on Kubernetes for Local Dev

https://github.com/sandys/kappal
21•sandGorgon•2d ago•11 comments

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

https://github.com/valdanylchuk/breezydemo
271•isitcontent•21h ago•36 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
199•limoce•4d ago•110 comments

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

https://github.com/pydantic/monty
284•dmpetrov•21h ago•151 comments

Making geo joins faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
155•matheusalmeida•2d ago•48 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
553•todsacerdoti•1d ago•267 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
424•ostacke•1d ago•110 comments

Ga68, a GNU Algol 68 Compiler

https://fosdem.org/2026/schedule/event/PEXRTN-ga68-intro/
41•matt_d•4d ago•16 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
348•eljojo•1d ago•214 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
466•lstoll•1d ago•308 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
367•vecti•23h ago•167 comments
Open in hackernews

Software is about promises

https://www.bramadams.dev/software-is-about-promises/
90•_bramses•8mo ago

Comments

hosh•8mo ago
There's an entire semi-formal language on promises, called promise theory. This includes promises autonomous agents (humans, back when this was conceived) make for other autonomous agents. Promise Theory was the basis for CFEngine, which spawned Puppet and Chef, but it's applicability is much broader. The kind of promises examined within this article can be described and analyzed by promise theory.

The central insight is understanding that promises are not obligations, and why and how that matters. From there, interesting things can be analyzed -- using types and contracts in a development team, unit tests, integration tests, specs, user interface and user experience, compliance, signaling, APIs, etc.

I think it is particularly useful now in the age of LLMs, agenic AIs, and autonomous robots that have to navigate spaces shared with humans.

https://markburgess.org/promises.html

agumonkey•8mo ago
Not long ago I discovered that there was a https://en.wikipedia.org/wiki/Evaluation_strategy#Call_by_fu... term
hosh•8mo ago
While I can apply promise theory to call-by-future, call-by-future by itself does not really bring out the richness of promise theory.

Promise theory isn't really about computation. It is about voluntary cooperation among agents. Agents, for the purpose of this semi-formal language, is defined as something that can make its own promises -- that is, communicate intent to a set of observers, some of whom might also be agents.

Promises are not obligations, and as such, the intent to do something is not the obligation to do something. There is no guarantee that the intent will be executed at all. Maybe other agents are actually doing this by best-effort. Sometimes external circumstances can trigger a failure. Sometimes the agent is not able to execute the promise well. Sometimes, the agent may deceive, and deliberately communicate an intent when it is intend to do something else.

How well an agent kept is promises is an assessment -- crucially, assessments are not global determination of an agent's ability to keep a promise. Each agent makes its own subjective assessment on how well another agent keeps its promises. Understood in this way, this can model both centralized and decentralized systems of voluntary cooperation.

agumonkey•8mo ago
Yeah I didn't skim enough through the article and since I just found out about call-by-future .. I premacommented.
zvr•8mo ago
Right. The work that Mark has done for more than three decades is amazing.

Unfortunately I think it has been unappreciated and largely unknown, leading to people either re-inventing things already known, or, even worse, trying to create something that essentially contradicts the theory and results and therefore failing.

kqr•8mo ago
Huh, interesting. I recognised the name from my time working with CFEngine – a very impressive piece of software in a space full of crap – but did not know there were books on it. Colour me intrigued.

Is the Thinking in Promises book too shallow or is it a good start?

hosh•8mo ago
I am not familiar with that book and that sounds interesting. I have not read that book so I won't make a recommendation on where to start.

I was working through "Promise Theory: Principles and Applications" and read through the first handful of chapters. For me at least, it was more accessible than math-heavy books. Yet, I can tell that it helped sharpened my reasoning ability about promises. I only made it through the first handful of chapters and yet it set a foundation that I was able to use over the years. Reading through some of the comments and reviews again, I see there are even more ideas that I could understand if I make my way through the book.

niekiepriekie•8mo ago
`software can be anything in imagination, but must be something in reality.` - I like that. I should stick it on my wall.
handfuloflight•8mo ago
This truism can be applied to any object that exists in physical reality.
meindnoch•8mo ago
Only async software.
sirlantis•8mo ago
> (to JS programmers: not that kind)
vrnvu•8mo ago
> When publishing software, you make a promise to your users.

Just to add on to that. Beyond a promise, it's a contract, and someone has to be responsible and accountable for it.

Like when you're walking or driving and see a traffic light... you don't stop to wonder if there's a race condition or if another signal is out of sync. You trust it and act.

Unfortunately, it feels like in software today, promises are made... but rarely kept. And worse, most people just seem to accept that. If traffic lights were broken, we'd just need to upgrade to the next version right?

arccy•8mo ago
actually, you're usually taught to look both ways at a traffic light...
Verdex•8mo ago
Second this. My dad always called it being "dead right" if you go through a green light without checking.
MichaelZuo•8mo ago
By definition the vast majority of software publishers are not that virtuous or credible.

Hence why large businesses pay a lot of money to get guarantees in writing from reputable firms, even though the nominally same software may be available for free.

behnamoh•8mo ago
I disagree. A lot of open source software literally come with "it's what it is" clause in the license, meaning that the maintainer has ZERO responsibility towards you, the user. No promises were made, you take it as is or leave it. Just because the dev generously decided to open source the code doesn't give you, the user, any "rights" to inundate the dev with issues.
badlibrarian•8mo ago
WARNING: Putting some code on the internet may yield curiosity and contact from other like-minded humans. The more potentially useful it is, the more people you may hear from. Gasp!

A simple "I put this up but please do not contact me" solves the problem.

A software license is not a social contract but that doesn't mean you can't bring some kindness and common sense to the situation.

bmitc•8mo ago
Yes, exactly. Especially when a lot of open source projects seem to be resume padders. They're presented as if they're the most useful library in the world with implied support, and then when your first issue is closed immediately with "yea, we don't care about that", you realize the reality.

It goes a long way if a "maintainer" simply states upfront about their mode of operation and sets expectations accordingly.

stronglikedan•8mo ago
> that doesn't mean you can't bring some kindness and common sense to the situation

It doesn't mean you have to either. There's no social contract either way, so there's nothing to debate. Doing whatever you want is the correct thing to do regardless.

badlibrarian•8mo ago
Setting expectations is basic human decency.
Verdex•8mo ago
Setting expectations is decent. However I suspect it to be advanced human decency.

Basic human decency is probably something more along the lines of 'live and let live'.

motorest•8mo ago
> A lot of open source software literally come with "it's what it is" clause in the license, meaning that the maintainer has ZERO responsibility towards you, the user.

There's a loophole in that scenario, which is created by the fact that in FLOSS there is no clear distinction between users and mantainers. Meaning, the whole concept of FLOSS is based on community modifying and redistributing their own contributions, as a form of giving back to the community.

The same principle applies to wikis. You can take it or leave it, but the whole notion of a wiki lies on your ability to make it your own.