> A Dell developer laptop could have been another option, but they are always unavailable in European shops.

Never ever order something from the dell website. Always seek out to either A. and Dell distributor or B. Dell directly (most likely you pay less than the price on the website).

Also there is a Ubuntu Dell Workstation in the European shops. (It's just a little bit hidden) http://www.dell.com/de-de/shop/dell-notebooks/xps-13/spd/xps...

Directly under notebooks 13" the simple versions it's the newest and besides the fact that it's a little bit noisy it's really really great, it even works with the dell wd15 dock just perfectly.

Thanks for the link, I keep it around for when the time to replaces the netbook comes around.

However, the prices being listed give an edge to Windows installations, even though we cannot compare Windows 10 Home with Ubuntu.

> Intel GPUs are no match for good 3D acceleration, case in point, what they just announced with AMD.

For regular tasks I find Intel GPUs great. Plus they consume little power.

NVIDIA is also OK on the open Nouveau driver. And when I do deep learning on a workstation, NVIDIA's closed drivers are good.

> Windows can also rollback without issues, just keep the snapshots and shadow file system configured.

Nix rollbacks have absolutely nothing to do with filesystem-level rollbacks.

Let me ask you something: doesn't it bother you that something like Nix is necessary for the problems Nix claims to solve? Why is a system so fragile as to require what Nix provides?

If you stay in the bleeding edge some setups might break. E.g. package A doesn't work with library B anymore unless you switch back to another version.

I have very rarely experienced this problem, and in 8 years time I have never had to roll back any critical packages like the kernel, firefox, emacs or any system utilities.

It's not something that bothers me because it's so rare, and I understand it's the product of very complicated setups and bleeding edge configurations.

Nix is mostly valuable for simple declarative configurations, the ability to alter package build recipes quickly, and for package and setup reproducibility.

That's my whole point though: why does this library conflict occur at all? Why do you need such a convoluted tool just to have a reproducible setup? Doesn't something about the nature of that situation seem off to you? Like, Nix solves a problem that maybe only exists because the system itself is fundamentally flawed?