HN user

enz

2,240 karma

Some dude living in Europe.

Posts167
Comments274
View on HN
kerkour.com 6d ago

From Microservice to Subprocess

enz
3pts0
blog.apnic.net 7d ago

Who's running all those tiny RPKI servers?

enz
76pts17
nickmonad.blog 9d ago

Building a Nostr Client (2023)

enz
2pts0
rubys.github.io 10d ago

Using Kamal 2.0 in Production

enz
3pts0
pythonspeed.com 10d ago

Faster binary search: from compiled code to mechanical sympathy

enz
71pts15
etcd.io 13d ago

Etcd v3.7.0

enz
2pts0
botmonster.com 13d ago

Bun vs. Deno vs. Node.js: which JavaScript runtime wins in 2026?

enz
5pts0
www.freecodecamp.org 14d ago

Zero-Trust Workload Identity in Kubernetes with Spiffe, Spire, and Cilium

enz
3pts0
www.schneier.com 16d ago

France to Stop Certifying Non-Quantum-Safe Encryption

enz
6pts0
www.devever.net 17d ago

Web-based cryptography is always snake oil

enz
122pts131
jacob.gold 17d ago

Programmers need to start meditating

enz
164pts168
www.reuters.com 20d ago

Portugal launches first open-source AI model, joining Europe's sovereignty push

enz
8pts3
ache.one 24d ago

The US Lock of the Web

enz
2pts0
openzl.org 25d ago

OpenZL

enz
3pts0
deno.com 27d ago

Deno 2.9

enz
145pts61
labs.ripe.net 28d ago

IPv6-Only vs. IPv6-Mostly: Appropriate Use Cases

enz
3pts0
kerkour.com 1mo ago

QUIC is more than a replacement for TCP

enz
12pts5
julien.danjou.info 1mo ago

An AI Agent Emailed Me

enz
2pts0
daniel.haxx.se 1mo ago

Query with Curl

enz
3pts0
julien.danjou.info 1mo ago

Europe's Cloud Problem Isn't the Tech. It's the Mindset

enz
5pts0
rachelbythebay.com 1mo ago

Feed Reader Behavior Project

enz
2pts0
mydbanotebook.org 4mo ago

Work_mem: It's a Trap

enz
48pts8
it-notes.dragas.net 4mo ago

Why I love FreeBSD

enz
530pts262
purplesyringa.moe 4mo ago

An Ode to Bzip

enz
4pts0
causality.blog 4mo ago

The Isolation Trap: Erlang

enz
166pts74
semiwiki.com 4mo ago

RVA23 Ends Speculation's Monopoly in RISC-V CPUs

enz
17pts4
kerkour.com 4mo ago

Using Rust and Postgres for everything: patterns learned over the years

enz
1pts0
goblincorps.com 4mo ago

Ageless Linux: Debian-Based OS

enz
2pts0
curling.io 4mo ago

We Chose SQLite

enz
2pts0
leg.colorado.gov 5mo ago

Age Attestation on Computing Devices

enz
5pts1

The trigger was outages in cloud services with sometimes significant impacts on other internet services. Shortly before, an approximately 15-hour outage of the AWS cloud in the US meant that not only Amazon's own streaming services but also Atlassian, Docker, Epic Games, and the Signal messenger were unavailable or severely restricted.

If I remember correctly, it was a us-east-1 issue specifically. Why is everyone hosted in us-east-1, especially in Europe where stable and reliable regions are available (eu-west-1, eu-west-3, ...)?

MariaDB (and MySQL‑family engines) avoid this entire class of problems by cleaning up row versions at transaction time. There is no background janitor. No vacuum lag. No wraparound timer. No need to tune autovacuum workers or throttle I/O to keep the system responsive.

The article seems a bit misleading. AFAIK, MariaDB (InnoDB) have to "vacuum" too. The implementation details are different between InnoDB and PostgreSQL, and maybe the InnoDB's Undo Log approach is less subject to bloat and maintenance cost, but it still exist as the InnoDB Purge Thread: https://mariadb.com/docs/server/server-usage/storage-engines...

1. Yeah, AWS and Cloudflare suffered from bad outages a few weeks/months ago. In my experience AWS has been very stable in the regions I use (us-east-2, eu-west-*), though.

To read more. I know it sounds cliché, but here is the plan: instead of setting a quantitative bar (e.g., read 20 books in 2026), I have 5-6 topics I want to explore and get reasonably knowledgeable about. That’s the goal.

Viral traffic from Hacker News, Twitter, etc. fades quickly; One-time spikes provide no long-term value; Focus on sustainable organic growth instead

I guess it depends on the audience. Our audience is tech-savvy and like RSS feeds, and it can change everything.

You need to make one big "spike", then some people will subscribe to your RSS feed, and some of them will silently follow you and read the future articles that won’t make it to the HN front page.

But I still agree with the point.

macOS/iOS 26.1 had some minor (but annoying) UI bugs. Some of them are still here after having upgraded to 26.2, e.g., the menu displaying wrong Bluetooth device statuses (despite the device working as expected).

This appears in the release notes as a fairly minor change but it significantly boosts the defense against one of the sneakiest problems in data management - silent data corruption.

I’ve always been puzzled about the fact there was no checksum by default. Integrity of data is a core job of a DB after all. I’m curious to know if there was a technical justification for that.

At $WORK-1 we had to log into the console almost every day as part of our normal daily operations anyway. However I rarely log into my personal AWS account console, the bill is 70-80cts/mo (mostly S3 storage fees, pretty stable over time).

If I were hosting something subject to potential egress overconsumption, it’d be interested I guess

Working on a small embedded vector database lib (à la SQLite). Just finalized the file format, it works pretty great so far. Besides, it’s an excuse to learn rust and low level programming in general.

At previous $WORK we had similar bills. Our Account Manager got us some deals on S3 storage and egress fee (via CloudFront), in exchange for some usage commitment. It was AWS Europe though, it may be different in the US.

Using Fresh (v1) for a commercial project, mostly SSR with a very few islands. So far it has been great for my productivity and it’s reasonably fast for our purposes (we run it on a VPS, not Deno Deploy)

I am playing with a Tillitis TKey, to use it as an HSM. I write its firmware in Zig (works great on that small RV32 chip), while learning it. I am also launching a consulting firm specialized on cryptographic solutions.

OpenBSD's Freezero 2 years ago

I guess encrypted swap would be a good option (easier than messing with mlock()) According to the docs, this is enabled by default.

I believe Go wants to support "ARM64" that just works among the heterogeneous fleets of Arm machines (from Raspberry Pi to Graviton EC2 instances) and let the programmer not to worry about it. GCC seems to do the same if I believe the article linked on "MySQL on ARM": it emits code that dynamically decides to either use CAS or LL/SC depending on the LSE support.