rootnod3

That is a wild stack to use for a RSS feed.

This feels very US centric. The title or link should reflect as much.

Exactly. The true answer is ed

Right. Better throw money at 5 different ones and then people come and tell you that you just need MORE agents and throw MORE money at it or you're not doing it right.

For Japan it might be the Felica chip.

Wonder how that happened...

I think Idris has a better chance there.

If you run it as a server mostly, I think the home partition at least can be shrunk to like 2GB or something.

You could also manually partition.

And coachings!

All of Prot's packages[1] are really nicely designed imho.

[1]: https://protesilaos.com/emacs/

Right...check the vibe coded slob pile for reference...

That is a whole lot of unsafe blocks.

The irony is not lost there. But at least some department there has see the light apparently

Yes. AI involved.

Self-hosting is king.

Absolutely. My daily driver on all my machines. My homelab started with FreeBSD on all machines with liberal use of jails. Now it is fully OpenBSD and only the file server is running FreeBSD now. All laptops are also OpenBSD, even the M2 Macbook Air

You hiring? Sounds like a dream. Dead serious.

So, Haskell people smart, other people dumb?

Also, where do you go from "preferring strong CS theoretical grounds" to "cutting corners"? They don't have to be mutually exclusive.

That garbage collection that Haskell has? Guess where that came from. The whole "functions as data to pass around", guess where that came from. It was those pesky lispers on a Tuesday.

Edit: typo

Maybe they let 5.6 do the calculation.

Jealous of both of you

Salary range limits should be adjusted. JPY definitely needs higher ranges.

Transpiling and a LLM hallucinating some code that _somehow_ passes the tests is not really the same thing though.

With the absolute irony that you cannot watch Netflix on FreeBSD (barring using the Linux compat layer to run a Linux version of Chrome)

Because the abstractions of old still required you to read man pages and learn stuff.

And manual steps are good. At least you know what is happening.

The old Unix philosophy. Simple tools that combined become powerful.

If you use _anything_ in production, you better make sure you understand the stack.

Uhm....source?

And yes, I went into that a while ago on my blog (https://blog.wollwage.com/2026/20260212-daily-source-reading...)

Difference is that capsicum is after the fact and mostly about file descriptors. You need to open them in advance and _then_ call capsicum. But it does nothing about syscalls.

Capsicum is really nice if you plan ahead, but pledge/unveil is easy to drop into any existing code base.

And some code is absolutely unnecessary. Look at the yes command. GNU version is optimized to death for no reason at all[1].

OpenBSD's version is as simple as it gets[2].

[1]: https://github.com/coreutils/coreutils/blob/master/src/yes.c [2]: https://github.com/openbsd/src/blob/master/usr.bin/yes/yes.c

They mostly dropped it because nobody was around who could maintain it. Wasn't just about security.