I sync important files to s3 from a folder with awscli. Dot files and projects are in a private git repos. That's it.

If I maintained a server, I would do something more sophisticated, but installation is so dead simple these days that I could get a daily driver in working order very quickly.

Linux is a tool that big corporate entities have profited greatly from for many years, and will continue to. Same with BSD, Apache, Docker, MySQL, Postgres, SSH...

Valve, Sys76, Framework, etc. Are proving that using Linux to serve an end user market is also profitable, and are capable of supporting enterprise use-cases.

I understand that there may be specific problems to solve wrt improving adoptability, usability, compatibility, etc., but Linux is doing more than ok within the context of the FOSS ecosystem (and increasingly without).

Your thinking is slightly skewed, IMHO. Linux doesn't have an inherent incentive to compete with MacOS or MS, and if it did, it would be subject to the same pressures that encourage bad behavior like spying on users, creating walled gardens, and so forth.

I'm all for exploring nix on one of my own machines, but I'm honestly just punching a clock on MacOS and nothing more.

I have everything I need to do my work, I just will not ever enjoy the part where I have to do it in MacOS.

wat is 10 x 0

brogramming, dawg

yes

ok this could be it, i guess. they have some form of device management tool.

never used an m1, but i have an m2 for work and it is ass. stutters and does weird shit all the time

i haven't taken the time to learn zsh, but i imagine there is an advantage to configuring it for yourself

alluding to those who will say something like, "linux is great, and macos is ok, but windows is awful!"

I dunno what's best for you, that's what's so beautiful about Linux

also homebrew sux and blows

Workflow on Linux: Whatever I want. Workflow on MacOS: Whatever they want, and if I want to change something, I have to install a third party tool reverse engineered from their private API that will break on every update.

Whatever you do, steer clear of Plasma Wayland right now. Polonium has a lot of issues.

You haven't provided any info about your partition scheme for either drive, but I assume you've got your bootloader installed in an EFI partition in the newer drive. You will still have an EFI partition on the old drive created by the Ubuntu installer, so just be sure you know which bootloader you're using.

Option 1 and 2 aren't functionally any different. It's not clear what issues you're worried about, but if you're nervous about breaking the Ubuntu installation, you might just want to wait until you can get the new drive.

You also don't give any indication of how much data you have that you want to keep. If the 2tb drive is almost full, you have fewer options than if it is mostly empty or half full. You could resize your EXT4 partition and create a new partition, for example, allowing you to mount a fresh, clean filesystem to a subfolder in your home directory. Once the data migration is finished, you can format the old partitions and mount them somewhere else, or resize the newer partition over them. Be aware that your HDD will eventually fail mechanically, however. Maybe 5 years from now or next week, but they all fail someday.

It's not clear to me what the goal of option 3 is, but it's dependent on how you use your machine. If you want to install a lot of applications or games that you want to run fast, you don't want to migrate a bunch of your data to your newer SSD. If you just want a temporary place to store the data you want to keep until you can format the old drive, I guess this is a fine approach, but creating a dedicated user for this is just adding unnecessary complexity, IMHO.

The Man Who Never Took Anything Seriously

There's lots of debunking material on this trash. If Books Could Kill podcast did a episode on it, kind of an infotainment takedown.

I'd recommend just scripting with rsync commands and run with cron or whatever scheduling automation. Backup locally to an external drive or orchestrate with cloud provider cli tools for something like S3.

There are some tools that probably assist with this, but it's just very few moving parts to roll your own. Clonezilla seems overkill and harder to automate, but I will admit I'm not an expert with it.

I have Arch on a 2013 mbp and it has served very well for years. I think I had to do a little work getting the backlight controls bound to some hotkey combos, but that might depend more on DE than distro. I'm probably going to put NixOS on it, since I'm not using it as my work laptop anymore. Use whatever you want! Debian is always a pleasure, too, in my experience.

I was there to witness it's majesty. Probably a year or two after it actually happened, but still I remember none pizza left beef