Not really. I'm not giving away which of these happens in which episode and a lot of the technology is recurring throughout the different stories. In most episodes the general idea of how the tech works is given away fairly early on and the real plot points are more about how it affects the characters.
In fact the parental controls idea is literally this: http://j.aufbix.org/plif/archive/wc161.gif and I'm pretty sure the soldier one was taken from an episode of Outer Limits or Twilight Zone.
Pay attention to what people do more than what people say. People vote with their feet. A senior engineer at Google can easily get a high paying job anywhere else.
Well it just works and is extremely simple to use.
I usually debootstrap into /var/lib/machines/something and do "machinectl enable something; machinectl start something", that's it. Then I attach to the machine using "machienctl shell something" and configure networking (host0 interface) inside the domain, that's it.
For drop in configuration systemd-nspawn parses a config file /etc/systemd/nspawn/something.nspawn which usually just contains network configuration on my hosts:
[Network]
Bridge=br-int
Systemd-nspawn enables and user namespacing by default and chowns the machines's root filesystem on first start. If that's not desired (Things like Samba fileservers don't work well with user namespacing) just disable it in the .nspawn file:
[Exec]
PrivateUsers=no
Everything you need to know is in the manpages systemd-nspawn and systemd.nspawn. I usually install systemd from stretch-backports because running a fairly recent systemd version helps as it still gets new features, but I never had problems with stability.
One thing I somewhat miss from what you are explaining is all the aditional things that LXD gets you (snapshots using ZFS, image publishing/sharing, migrating containers between LXD hosts...)
But maybe some of those things are still doable (e.g. mounting a ZFS dataset as storage for /var/lib/machines/containerX)...
Haven't dealt with live migration, but mounting filesystems should be easy using systemd's unit dependencies.
Just drop a .mount file in /etc/systemd/system and set RequiredBy=systemd-nspawn@something.service and StopWhenUnneeded=true and the filesystem should be mounted before the machine starts and unmounted when the machine is shut down. See the manpages systemd.unit and systemd.mount for details.
"Erlang Solutions" says Erlang is the bee's knees...
I really like when someone that doesn't have a horse in the race reviews some language (better if it has been used in anger). You gotta value the perspective of a pragmatic engineer that has misapplied a tool.
There's a lot to learn about where a language is best used, but when someone pay is somewhat tied to a language I don't trust the analysis as much.
Just a thought, imagine how this article would be if the companies were reversed. Would it be the same?
And that's how you recognize objectivity...