Keeping the home directories in another tree has been a thing for a very long time. I was working with Xenix in the early 1990s with a second hard drive, and kept all the home directories on the external hard drive. When I needed to do an OS reinstall, it just a matter of mounting the external file system on the path. Same would apply if you're using NFS or any other network file system.

What distort? We're running Ubuntu LTS on workstations, and we keep the updates rolling, and have no significant issues. Generally when we want to do feature updates, we don't do in-place upgrades at all, we just build a new image and roll it out. We want complete control over new feature rollouts, including any major new upgrades of key software like LibreOffice.

And honestly, that's pretty much how we were managing Windows prior to beginning the migration. Updates in general are always a risky business, and I've seen upgrades in every OS I've worked with since Windows 3.1 go horribly awry. I've baked Windows systems, Linux systems, BSD systems, and even had to finally give up and reinstall my M1 Mac because the major release upgrade worked about 90%, but there was enough peculiar behavior that it just wasn't worth trying to track down.

In all cases in an enterprise environment, regardless of OS, you don't want feature updates, significant changes to functionality, or installs of major version of updates to software. When it comes to that, you're working in a lab environment, rolling out to a few users to test stability and interoperability, and then pushing them out to all the workstations. This isn't a Linux thing, this is just how an IT department stays sane and doesn't screw up the whole organization's workflow.

There are only a few circumstances I can imagine where LTS support over three or four years would even be desirable, and most of those are pretty niche use cases dealing with specialized equipment or legacy systems. In general, whether it's Linux, BSD, Windows or even MacOS, it's always better to do a full reinstall with the new OS. Heck, by the time Windows Server 2003 went mainstream, only madmen were doing in-place upgrades on domain controllers. The better solution was always to build a new DC and then decommission the old one.

All my worst upgrade disasters in any OS came from in-place upgrades just fucking everything up. At best, it left a lot of old cruft hanging around, at worst it rendered a system almost unusable, and it was usually a bit of both.

The way I'm rolling out Debian and Ubuntu at work these days is just working images. Sometimes there's some funky hardware that requires after I clone an image that needs some intervention, but generally it just works. New images are generated every six months, or when a new release has been tested, rinse and repeat. In the business world you don't give a crap about anything but quick up time, and I have a stack of spares in a closet that get refreshed regularly, and when something blows up, you grab one off the shelf and move on. New OS upgrade, new image.

It's almost like elections have consequences, and America has elected that it and its businesses are going to be treated like the plague. Well, even more than that, even visiting the US is dropping, and now with US Marines on city streets in a major US city, well, fuck that banana republic. I will never enter the US again.

I've had rendering nightmares in Word, including docx files. There are most certainly version and rendering issues in Word just like any other word processor. It gets really horrendous with tables and frames, particularly when they are used as some sort of typesetting system, at which point try to open up on a different version of Word than the documented was created on, and it can turn into a mess.

I can get native Zoom apps on Windows, MacOS, Android, iOS and Linux. It isn't perfect, and they've added a lot of cruft, but all in all, I've had less problems than I've had with Teams.

It's not like the writing in the original Star Wars film was all that great. Guiness's dialogue was cheesy enough that he begged Lucas to kill his character off (and Lucas, to his credit, found a way to get Guiness into two more films).

But if I were making fun of the third trilogy at this point, it wouldn't be so much about the bad writing (though in general it's bloody awful), but the almost complete lack of any kind of plotting.

The Producers? Young Frankenstein? Blazing Saddles? High Anxiety?

I'm not sure there's a funnier scene in any movie ever made in history than Springtime For Hitler (the reaction shots in that scene are the best I've ever seen in a movie), with the possible exception of Dr. Frankenstein and his monster doing a song and dance number to Putting On The Ritz.

For me, at least, Mel Brooks is probably the pinnacle of comedy filmmaking.

The only one I can think of is John Candy (which is a big hole), but Rick Moranis has been retired for many years now, and he's rebuffed most attempts to get him in front of a camera again.

And that underlies the reality of WYSIWYG, that there are limits to what any word processor can actually do to guarantee formatting and fixed placement. It's why Tex/LaTeX and PDF were invented to begin with, and why there's really a point at which trying to force any WYSIWYG word processor to behave that way is going to lead to fragile misbehaving documents that fall apart. As a very good example, the use of tables and frames in documents (both docx and odt) to guarantee the positioning of various elements creates can quickly lead to documents so fragile that any attempt to update styles causes havoc.

I'm working my way through some biology and general science courses right now in my spare time, and I'm seriously looking at re-familiarizing myself with LaTeX to produce reports and papers, because the amount of work I've had to do to get diagrams and images to stay put, and to break my cardinal rule relying solely on styles for formatting makes me think the kind of work I'm doing is much more in typesetting than in word processing.

Selecting office software so that you aren't held digitally hostage to a government that is, say, threatening to annex a significant proportion of your territory, is both eminently defensible for operational, security AND political reasons.

Providing you have control of your DNS, it means using DKIM , SPF or similar measures. I've been self-hosting email for three decades, and it ain't complicated.

"Likes long romantic walks in the park, binging Buffy the Vampire, pasta, and overthrowing the US government by lynching the Vice-President and the Speaker of the House."

I've been using it pretty much full-time for the last couple of years, and while there's some compatibility oddities, all in all it works and works pretty well, to the point that I find manipulating styles far more coherent than in Word. It's actually opened some docx files that were just outright screwy when I opened them in Word, so I'm baffled at times how such documents get produced.

It's going into the oceans, just so the combination of pH fuckery and increased warming turns the world's oceans into an tepid acidic brine.