Recent submissions

Comment · 3 days ago
You haven't used trains elsewhere if you think Dutch ones are bad.

Try a few weeks of German trains. Sometimes no trains leave on time for weeks.

Comment · 3 days ago
When computers fail here in the Netherlands, trains are just stopped until they can be fixed.

In some cases, trains can be ordered to drive "at sight" -- slow enough (walking speed, basically) to stop if there's something visible on the tracks that shouldn't be there (train, car, person, cow, whatever)

Comment · 5 days ago
Containers fix this.

As long as the container bundles the right libc, the program should work.

Comment · 10 days ago
All it takes is one small leak. Which seems to be what happened here.
Comment · 12 days ago
cue Creedence - Fortunate Son
Comment · 13 days ago
"Roads? Where we're going, we don't need roads!"
Comment · 1 month ago
Comment · 1 month ago
That's what the original OpenID (from back in the LiveJournal days) was supposed to be right?

"Host your own identity"

Comment · 1 month ago
I think this goes both ways.

More actual interaction between end-users and programmers makes the end-users better at reporting bugs and describing what they want (and at having an idea how complex a certain request actually is).

Because the multiple translations from customer wish to project manager language to backlog items are all lossy.

Comment · 2 months ago
When does the silver arrive in Maracaibo? Early or late in the year?
Comment · 2 months ago
Programmers, who knows what they're doing in there?
Comment · 2 months ago
DOS programs generally were like command line apps today (but simpler, obviously). They did a thing, then exited. Or they showed their "TUI" (as we'd call it today), and when you told it to exit, you got back to the DOS prompt to start the next program.

TSRs were a special kind of program, that instead of telling DOS "I'm done, here's my memory back", said "I'm done for now, but don't unload me", so their memory stayed allocated/used. And you got your command prompt back immediately to continue your work.

TSRs usually hooked into an interrupt like the keyboard interrupt, intercepting a hotkey to re-activate the program (so you could browse your address book while you were in your (text mode) word processor; "kind-of" multitasking), or they offered a service to other programs (like the mouse and CD-ROM drivers).

There were all kinds of things that ran as TSRs. Virus scanners (hooking into disk write/reads), modem tools (showing "RING" in the corner of the screen when the modem detected an incoming call), note-taking apps, address books, you name it.

Comment · 3 months ago
Comment · 4 months ago
Isn't that what (liability) insurance is for?

(if there's anything Germans like as much as bureaucracy it's insurance)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton