I don't think people appreciate what "abstractions are leaky" means in practice.

The higher in the stack, the more layers of leaky abstractions a piece of software has to deal with.

Ignoring them means weird errors and unexpected behaviors as assumptions break down. Working around them means maintaining random workarounds.

The higher the abstraction level the more workarounds there are to maintain and weird errors to contend with.

"Let's move to the browser" means "more of these, please". 👀

Follow

@rysiek What I find weird and frustrating is that it's very often hard to convince people that making them less leaky is worthwhile (e.g. that it's worthwhile to be able to succinctly formulate the contract something exposes to the things above it).

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.