Believe it or not, but in a world where you are editing text and moving between rows and columns with the arrow keys, being able to keep your hands in the same position and switch to jumping between words and paragraphs, or PgUp/PgDn/Home/End, simply by pressing a modifier key with your left pinky, ring finger or thumb, instead of moving your entire right hand to another part of the keyboard, actually is a great convenience. You are right about window management, though: Windows, macOS and the various Linux desktops all have some features I wish the others would adopt and others I wish they would simply drop.

In most situations your hands would be on or near home row anyway, so thatâ(TM)s not much of a benefit, meaning this whole subthread is all about arguing from familiarity. :)

1. After they went back from the stupid butterfly keyboards, Apple keyboards are back to being as reliable as ever. 2. After getting used to Fn+arrow keys for PgUp/PgDn/Home/End and Fn+backspace for Del, keyboards with separate keys for these functions drive me mad.

This is why we want IPv6 to become a thing - combined with relevant security layers, of course.

I would consider it much better not to support that scum even though I could afford to.

Sync is not backup - it is sad that someone had to learn that the hard way.

Letsencrypt/Certbot works just fine. What we really need is proper worldwide IPv6 deployment so everything can get its TLS certificates easily. As it is I spend time setting up internal certificates for machines behind my reverse proxy and letsencrypt certificates on its Internet-facing side, for anything where it is not practical to assign an individual IPv4 address.

I'm still on my maxed-out 2013 model and recently did a battery swap in order to be able to keep using the machine for as long as it serves its purpose. Thanks in large part to the frankly fantastic I/O performance of the SSD in this machine, a laptop that's meaningfully faster than mine will still cost the equivalent of $3500 or so, no matter its brand. Anybody whose work doesn't require the latest and greatest in GPU power would probably still be happy with this machine, so it definitely could be handed down to somebody else at this point unless I was too happy with it myself to get rid of it.

Had I gone for a smaller spec (8GB RAM/256 GB SSD, for example), it still wouldn't be a bad machine for many common use cases, and it would still be hard to find something faster at an equivalent price point. In other words: We're at a point where, unless you really skimped on everything when purchasing a new computer, kit can comfortably be handed down several years later without requiring upgrades to be reused.

If you just reap the fruit of another persons labor, it does not matter that you will be selling it below current market value - you are still making a profit.

Security mainly boils down to âthink about the consequences before implementing somethingâ, and âclean up your own mess to avoid introducing accidental consequencesâ. If a developer lacks these habits, they will write broken software from more perspectives than just security.

The problem is that the intruder doesnâ(TM)t have to come from outside, but most likely will be a naive user on your own network who clicks something they shouldnâ(TM)t have on a poorly secured computer. So: The basic protocols are still around, so you can still learn the basics of how to set up network services within a lab environment; nothing has really changed there. But donâ(TM)t stop learning once you know the basics; thatâ(TM)s the main lesson here. When you can reliably create a file share, learn how to manage user accounts and groups, and how to apply the principle of least necessary privilege.

How is someone even allowed to self-identify as a developer if they lack the understanding - not to mention experience - to perform proper backups of their work? What does that say about the quality of their software? Trainee or junior programmer? Possibly. Developer? Not at all.

There's no need for analysis paralysis. Try out some Python (I enjoyed reading Python Crashcourse by Eric Matthes). I would recommend Learn Python the Hard Way, but it hasn't been updated to cover Python 3. If you enjoyed Python programming, take a look at Apples's (imo) excellent Swift resources and guides. That language actually isn't a lot harder than Python to get started in. If you have an iPad, check out Swift Playgrounds. It is a game, but gives you a good feeling for basic programming concepts.

I think the rape on a successful movie franchise that is Alien vs. Predator is the worst case in this category. They had it all: A buildup for an intelligent plot, a buildup for a thrill, a buildup for a decent action sequence, and then someone says "Scrap that, audiences today don't like to think, to be scared or to see explosions and blood. Let's wrap it up and sell the movie". I actually don't remember the movie properly anymore (I just saw it once), I just remember this empty feeling when I stepped out of the theater...