News for hackers. Stuff that matters.
Re:Unikernels were hard. key word: were by tgv on Sunday October 11, 2026 @04:08AM (#50040704)
Not just that. Unikernel sounds ok if all your linux server does is run one service that doesn't need anything but tcp/ip, and whose users don't need extra resources. But being able to deploy a new binary and other files through any means (ssh, pipelines, git), having localized log files, etc., are more than a convenience. Sure, I could log on another server, run a db on another server, and deploy html/css/js from yet another server, but would that make life easier? And this is just a really simple case. If you have multiple services, you'll need multiple servers with a uni-kernel approach, or build some monster thing. It's horses for courses.
Re:Unikernels were hard. key word: were by pjmlp on Sunday October 11, 2026 @05:29AM (#50041303)
Welcome to cloud computing, where software is cattle, not pets.

There isn't a Linux server taking care of a couple of services.

There are services deployed as Kubernetes pods, or serverless language runtimes across a cluster abstraction, running directly on top of type 1 hypervisors, or minimal kernel images enough to power distroless container images.

Re:Unikernels were hard. key word: were by xorcist on Sunday October 11, 2026 @06:16AM (#50041560)
And before you know it you've built a very complex, and not very secure, operating system.
Re:Unikernels were hard. key word: were by FridgeSeal on Sunday October 11, 2026 @07:05AM (#50041887)
Let me know when your local OS does multi-machine scheduling across heterogeneous hardware and application constraints, networking, observability, service accounts and a finer grained permissions system, in a way that’s far less confusing and piecemeal.

Also, this argument only works if you just broaden the definition of “OS” to “anything that runs that isn’t your apps”.

Re:Unikernels were hard. key word: were by timschmidt on Sunday October 11, 2026 @02:10PM (#50046046)
> Let me know when your local OS does ...

Sounds like Plan 9. Which would put that around 30ish years ago. Mainframe OSes can probably make similar claims even earlier.

Re:Unikernels were hard. key word: were by pjmlp on Sunday October 11, 2026 @06:27AM (#50041618)
Depends on the skills on managing EC2, AKS,...
Re:Unikernels were hard. key word: were by convolvatron on Sunday October 11, 2026 @09:31AM (#50043131)
maybe we _should_ be thinking about building proper distributed operating systems instead of loose collections of services. we really missed an opportunity to rethink the OS interface for 'the cloud'. or rather we kind of wasted alot time and maybe we should get our shit together and do it properly. no matter how much we chant 'cattle not pets' everyone is still installing individual nodes and logging in and puttering around.
Re:Unikernels were hard. key word: were by xorcist on Sunday October 11, 2026 @10:01AM (#50043398)
Agreed! There were many promising distributed operating systems, most got stuck at the research phase however. But the cloud pretty much killed them all.

Not that many people keep large distributed workloads anymore, and SLURM-like schedulers on top of regular operating systems were deemed good enough for supercomputers.

Re:Unikernels were hard. key word: were by convolvatron on Sunday October 11, 2026 @11:04AM (#50044069)
not always. Asci-red had a distributed version of OSF/1. this wasn't a great design because it was built on distributed shared memory, so it had fault tolerance and performance problems. the MTA had a shared memory monolithic BSD, but that was almost a forced choice.

The Cray T3D had a really nice distributed services model (really kind of a distributed exokernel) that would be worth emulating

on some machines there was an interactive ganged run facility like 'mpirun'. I think even this distinction where there are 'login' or 'service' nodes and anonymous runners would be at least a little structure. I guess you could argue that k8s is this, but it kind of falls short and seems to require a lot of continuous propping up.

I worked on a single system image project that didn't ever get shipped. it turns out that a syscall proxy layer isn't that difficult to implement, and that leaves you with an undisturbed user space.

anyways, there are a whole host of design options that don't look like k8s or slurm. and having spent some time recently on non-hyperscaler clusters, that bottom level of bringup (provisioning, networking management, reporting, fault tolerance, distributed filesystems) is really a nightmare. I think we lost a lot of traction there by raising generations exclusively in someone else's operational context.

Re:Unikernels were hard. key word: were by DrBenCarson on Sunday October 11, 2026 @02:02PM (#50045956)
Yep. We say cattle not pets, but even cattle often need personal attention for one reason or another. It doesn’t mean you’ll never need that option in your back pocket
Re:Unikernels were hard. key word: were by convolvatron on Sunday October 11, 2026 @03:02PM (#50046647)
if you didn't have a multi-user operating system running on every node that basically demands this, because of its complexity and fragility, and you had the necessary introspection to look at memory usage and open sockets, and disk bandwidth, and everything else you might need to mange those processes, then the utility of your escape hatch - which also is complicated and fragile, becomes negative.