Sure you can write readable and maintainable Perl.
But most people don't.
the problem is "developers" that have never had to maintain someone else's code often enough to understand the value of readability and maintainability.
The same is true of Python (and most other languages for that matter).
I did exactly the same with a Core Duo iMac at work. Just replaced a 2006 vintage Mac this past summer, so ~8 years old.
Not to imply that Apple has never released a less than stellar model, but Macs have generally held on better/longer than PCs, it's never been that uncommon to see them last at least 6-7 years, and at that point it's less an upgrade because the old computer stopped working than because the new ones are now "enough" better.
True, but only if the capitals gains and/or dividends for the mutual fund in that particular year exceed a certain threshold (or, as the reply above mentioned, you have certain classes of investments which trigger automatic reporting). Off the top of my head I don't recall what threshold is, but it's been quite a few years since I had to fill out Schedule D, which wasn't really all that complicated.
Federal law enforcement officers or private contractors shall not seize any photographic equipment or their contents or memory cards or film, and shall not order a photographer to erase the contents of a camera or memory card or film.
Exactly. I've been doing the same for more than the last decade, except using a second workstation as the backup device (as opposed to NAS).
If the backup machine is on the same LAN, I export the drive (or directories) to be backed up read-only, mount them on the backup read-only, and copy using rsync
If the machine is in a different location, I share a key pair and pull what I want backed up using rsync (over ssh) from the backup machine
This is fairly bulletproof, and in no way can anything running on the original host modify the backup, aside from possibly replacing a changed file.
To thine own self be true. (If not that, at least make some money.)