Take a look at the T440p (i.e. the flagship thinkpad). They've removed the mouse buttons, but apart from that it meets all the criteria on your list. At the rate things are going, it's probably going to be the last model with physical function keys.

The second bit wouldn't even be necessary - as far as I'm aware, the only distro that made python3 the default was Arch. Because python2 is still the default on most systems and incompatible with python3, most programmers working in Python 3 explicitly specify python3 in the shebang. (Using /usr/bin/python only is considered poor practice for this exact reason.)

And that's precisely what this article is about - supporting pre-2.7 and 3.x are almost mutually exclusive due to changes in the language. Once written in 2.7, it's often possible to support 3 via a tool like six.

Even if a computer can't predict that as far ahead as a human, it can react much faster. Human reaction time is about 200 ms, but a computer could easily react within about 30 ms. That should be enough to compensate for the intelligence described in the vast majority of situations.

On page 10, the inability to have reserve banking is discussed. Could you explain why reserve banking is useful? As far as I can tell, it simply inflates the perceived amount of money present in the system beyond that actually present, introducing a potential failure mode (a bank run).

Not great.

However, if you asked "what are the chances of getting stuck in ice in Antarctica during the summer, given that it just happened to another ship nearby?", I'd say reasonably high. Conditional probability in action.

I'm in my early 20s, and very much grew up with GUIs and Windows. Despite this, I now use Vim (cue flame war) as my text editor after seeing how fast proficient users could be with it. I have a friend who uses Emacs as his desktop environment - no KDE or Gnome, just Emacs.
Both are powerful text editors with niche uses. e.g. programming. While fewer people are learning them now that they are no longer the default text editors on most distros, they're hardly dying.

tar -axf - automatically chooses compression algorithm based on extension
zsh - the autocomplete alone is worth it compared to bash (use oh-my-zsh to simplify setup). Right-hand prompts are pretty nice once you get used to them.
pv - pipe streams through it for a graphical progress bar
nice/ionice - lower the priority of background processes
ack - faster alternative to grep with better output formatting
lsblk/lscpu/lshw/lspci/lsusb - view attached hardware. lshw is great for a comprehensive list, and lsblk recognizes raid, encrypted volumes, etc.
pwgen - useful for generating passwords
apt-file/dpkg/$YOUR_PACKAGE_MANAGER - read the man pages - commands for determining which package a file belongs to (esp. if that package isn't installed) are particularly useful
Yakuake - not a CLI tool, but being able to pull up a terminal with a single keypress is pretty handy

I'm currently in the process of setting up something like this.
Kolab is a FOSS groupware server that can synchronize emails, to do lists, calenders, notes, etc. across multiple devices. You can access it from the included web interface (roundcube), the recommended client (Kontact), or via Outlook with the connector installed. Android support is available via ActiveSync, and I believe Kontact Touch will be ported to Android now that Qt 5 supports it.)

If you're not interested in running your own server, there're also sites like this which sell accounts.

Here are some notes on my experiences setting it up, for anyone interested:

• Make sure you read the documentation first, because Kolab is too complex to just jump right in and hit the ground running. In particular, make sure you have a FQDN
• Kolab pulls in a bunch of different daemons, including apache2, cyrus, mysql, postfix, slapd, clamav. It's a fairly heavy-weight solution, since it was developed with enterprise users in mind.
• Multiple users can use a single installation. Users can be added/removed from a web interface.
• By default, nothing uses SSL. This is undesirable if you're planning on connecting to it over the internet. The LDAP server uses a different SSL stack to the rest of the daemons (NSS), and you'll definitely want to run it over SSL because it sends passwords in plaintext. The easiest solution I found was to create a CA cert with certutil, use that to create the certificate for use with LDAP, then export that certificate to PEM format and use it for everything else. LDAP needs to be configured online, but all the other daemons just have configuration files with entries for the path to the certificates.
• On some distros, Kontact may not be compiled with Kolab support. (e.g. Sabayon)
• RSS syncing is currently the only feature in Kontact that doesn't sync with Kolab (AFAIK), although you can embed tt-rss in the web interface.

Background: I'm an ECSE student who has used both throughout my course.

Octave is very much like LibreOffice - it's usually good enough to use instead of MATLAB, but it's not perfect. Most of the functions are there, though some which are commonly used but not strictly necessary (e.g. importdata) are not. Octave's syntax is also looser than MATLAB's (you can use ! instead of ~ for logical negation), which means that you still need to test a program in MATLAB if that's what the recipient is going to be running it in.

Its main advantages are its cost and size - Octave is free and a full installation is 42 MB, whereas MATLAB costs tens of thousands and takes up about 5 GB. MATLAB also has rather cumbersome DRM that can cause issues.

The main disadvantage is speed. Running a SVD on a largish matrix (e.g. 350x350) is one or two orders of magnitude slower under Octave compared to MATLAB. i.e. it takes 10 min instead of 10 seconds. That's a pretty niche use though - most of the computations people use MATLAB for aren't particularly intensive.

It doesn't matter if they give him his wallets - they've already emptied them into a new one. The original wallet files will let him access his now empty wallets, but not the bitcoin that were once in them.

The article is pretty light on details, but what dependency resolution algorithm has exponential scaling? Topological sorts are usually O(V + E).