Indeed. My nephew and I played it tonight. He's 10 and I'm 35. We had no troubles and had a lot of fun setting the company owner's name to stupid stuff like "butthead".
I upgraded my XPS 15 (9550) from Ubuntu 17.04 to 17.10 about a week ago and have had no issues so far. Actually, I find it a little less buggy on my XPS than 17.04 was - overall I am pretty happy with it. Of course YMMV - my specs are below
It's a bit of a pain, but quite doable on most distros, if you know your way around. I just did it on two distros for my ThinkPad 25: with openSUSE it was part of a weekend of playing around with it and setting it up, and on NixOS it took an hour or two to set up how I like.
The real problem, imo, is that all of the solutions work badly (they either work at a performance penalty (as with Bumblebee) or require a separate X server for each GPU).
This is entirely a result of NVIDIA's refusal to implement decent support. The Nouveau drivers offer proper PRIME support, which yields an experience more like that on Windows in terms of workflow and the amount of setup (virtually none) required, but they have their own performance problems. Hybrid graphics with AMD GPUs apparently works nicely with whatever drivers you like, granted that the software stack is sufficiently up to date on your system.
I didnt bother - I set it up to only use the Intel GPU b/c I wanted longer battery life. Besides I don't game on the laptop anyway. I dual boot Windows (since the license came with the box) and can use that if I really want to game.
However if you really want to, everything pxc says below is spot on...
There were people in the bug report reporting issues on the XPS 13 and many more brands than just lenovo. Try waiting 6 months until Ubuntu can sort their shit.
edit: there is a guy complaining that it screwed his XPS 13 a few messages up.
Yeah, Maybe I got lucky. If you want to totally play it safe wait until 18.04 LTS is released. They should (hopefully) have this worked out by the LTS release.
I wouldn't worry that much about it, the differences between Django 1.11 and Django 2.0 aren't major ones with the exception of dropping support for Python 2.x and the new simplified URL routing syntax.
Django 1.11 is a LTS (Long Term Support) release so it will have security upgrades until 2020, so you are safe sticking with it.
However I'd go ahead with 1.11 and transition to 2.0 to learn how Django handles deprecation and how to upgrade a codebase, both very useful skills as Django has a steady release process and it's often easier to track Django than to do a multi-version migration.
Before I moved to Windows 10 I routinely had 150+ day uptimes. The old VMWare is rock solid and runs really fast.
Having to use an older version of xubuntu does kind of stink, but I'm pretty sure if you really cared you could use 16.04, but just downgrade xfce to use 14.04's version.
It's not something I bothered with because visually I'm happy with the way things look, using custom PPAs are easy and I use Docker for various programming language runtimes and services.
Is Docker (or any other container platform) a facilitator to reproducible builds? Making the environment standard between builds is probably easier in a container.
Docker is part of a broader "reproducible build environment" strategy, but doesn't really help with some of the things that cause problems (timestamps, kernel version, random IDs).
Docker seeks to reproduce a functionally equivalent software environment, motivated by version management concerns. Debian is trying to reproduce bitwise identical build products, motivated by security concerns.
Docker images built with the first-party toolchain aren't reproducible - if you run `docker build ...` on a Dockerfile, then delete the image and rerun it, you'll get a different set of image hashes. This is likely due to timestamp embedding.
There are other toolsets that supposedly create byte-identical Docker images generation (Bazel, some others), but I haven't tried them.
