Depends on where you imagine the work to be. I tend to think of unikernels as having to 'front-load' more of the work. That's why you can treat the end artefac

Depends on where you imagine the work to be. I tend to think of unikernels as having to 'front-load' more of the work. That's why you can treat the end artefact as almost disposable. With a traditional stack, it may be easier to set up, but you're then committing to acting as caretaker for the code that runs on that machine, inc. patches, upgrades, version constraints, etc. There's probably more work there over the long term. This is kind of where the distinction of 'cattle vs pets' comes from.