PHP stack traces are effectively identical to Java's in every metric I'm concerned about.

If you get them sensibly in a log file, anyway. If you allow PHP to render this god awful fugly table inline with your page? Well, have fun. Yes, all the same info is there, and on paper it's organized in an easier to read format. But oftentimes the table will collide with and mangle with other elements and styling on your page, making the trace irritating or impossible to read.

This isn't much of a problem of course, because aforementioned log file is absolutely the way to do it in the first place, and PHP lets you. And hey, absolutely obliterating your page DOM in strange and exciting ways on error sounds like a fantastic way to ensure errors get caught and addressed in testing, so even the unpredictable mangled DOM bullshit is useful in its own way.

But if someone wants to dunk on PHP for at least outwardly appearing to promote trying to debug it with these awful stack trace tables, I think that's a well-earned roasting.

Making more money back than they paid.

It amazes me how every time a for-profit company that provided a free service goes mask-off and starts aggressively monetizing it so many people put on a shocked Pikachu face.

This is exactly how this works, people! The free shit is always bait to draw you in and get you invested. The trap was designed from the start to snap shut once there was enough of you in it. They fully intend to not just extract value from you to run the service, but also to retroactively pay for all the free shit they gave you. It was always a loan. An investment.

Oh, sure, you can always be sly by taking the free shit and ditching once monetization comes over the horizon. But do so knowing that every time you need to do this is the rule, not the exception. Companies aren't suddenly slighting you one by one out of the blue, it was always the strategy from the beginning for all of them.

There is a long, long list of classifications they may put you in. I believe appointing one to you is their job, so you don't get to pick. I read through all of these and couldn't decide which of them really applies to, "I am building a FOSS app/library".

There is a "scientific research" designation. Does that count? Well, if so, it says this:

Scientific research does not include activities of a type ordinarily carried on as an incident to commercial or industrial operations, as, for example, the ordinary testing or inspection of materials or products, or the designing or construction of equipment or buildings.

Is building software "designing or construction of equipment" that is "incident to commercial operations"?

Maybe it belongs under classification U41, which is Computer Science? Does building software count as "research" into comp sci for the benefit of the general public?

Maybe it's W80, public utilities? I think that's intended more for municipal utilities like electricity, water, gas, and sewer, not public software projects.

I really have no clue. Here be dragons.

IANAL and I have zero experience doing anything remotely like this.

But from my cursory reading of the IRS instructions on their website, doing this in the US specifically is more or less a two step process:

1. Form an organization by filing with your local state. Every state handles this process differently; in some (most?) this can be as straightforward as filling out a form, paying a processing fee on the order of $100 or so, and waiting for approval. Just don't form an LLC in particular, as that complicates the next step.

2. Fill out Form 1023-EZ with the IRS. This requires proving your organization qualifies for tax exemption (it is not clear to me whether this would) and a filing fee of $275. Your org also cannot possess more than $250,000 of assets, cannot receive more than $50,000 of revenue from donations within the span of a year, and cannot be registered as an LLC. If you fail to meet these, you need to fill out the regular Form 1023, which I believe is more involved and has a more expensive filing fee.

If both of these forms are accepted, kapow! You are now a tax-exempt organization, and other corporations can charitably donate to your project for tax breaks. Just remember to do your station-keeping tasks like filing your annual company and tax exemption status renewals, reporting your earnings to the IRS, and sending receipts to donors.

Every edition that isn't the Java edition has been merged into one edition that cross-plays with every other edition. Pocket Edition is the same edition as every console port as well as the Windows 10 native version.

I use KDE on Debian and did not encounter this problem when I did the reverse action (migrated /home from a second drive back to the system drive).

This may be an insulting question, but are your files in the new home partition inside a /home directory on that partition? Because if they are, that would definitely mess it up. If you mounted that to /home in your fstab file, then the path to your home dir would be /home/home/user instead of /home/user. Your user directory needs to be at the root of the filesystem on that partition.

I expect you did not make this mistake, but a sanity check never hurts...

Oh, and check the files on the new partition with ls -l as well. See who owns them. If you did the copy with the root account or with sudo, the owner of the files might be root. They should be owned by the user you are trying to log in as.

I can't give you precise directions on how to troubleshoot this, hoping someone else can chime in with some wisdom.

What I can tell you is that being able to log in and then failing to launch a session is definitely evidence that your system either cannot find or cannot access the /home directory. I ran into the same thing not too long ago, but I guarantee you that we don't have the same problem. Mine was file permission related due to installing a new OS. You have the same OS.

When you installed your OS, did you create a root user account? Not an account that can use sudo, I mean the root user. That user has a special home directory, /root, which is entirely separate from /home. If you can find a guide that tells you how you can boot your OS as the root user, try that.

Put your system back into the broken state with the new partition in the fstab file, reboot, log in as root, and check the filesystem. If you did things correctly, a /home directory should be there, and there should be files in it. If you don't see it, it means for whatever reason it failed to mount on startup. Try using the mount command manually to force it to mount, and see if it gives an error. If it works with the command, it means your fstab is not correct.

Best of luck! Welcome to the Linux experience... lmao

or is it a really good OS for privacy that sacrifices in usability?

Privacy and usability are inversely correlated. Anyone who tells you otherwise either has a relatively weak definition of "privacy" or a relatively exotic definition of "usable". If you're at the point of installing an OS like Gentoo just for its privacy benefits alone, I'd say you're already the latter case, even from the perspective of most fellow Linux users.

Of course, that doesn't necessarily imply very un-private software is always very usable, or that highly privacy-respecting tools with good UX don't exist. Just that most highly UX-polished software tends to have poor privacy, and most privacy-focused software expects the user to do a lot of hoop-jumping to make up for all the systems and workflows the user can't utilize due to having some dealbreaking non-privacy-respecting component to them.

Here's an overview of how Linux reads its filesystems on boot:

1. You press the power button on your PC.
2. Your motherboard receives power and begins a process called Power-On Self-Test, or POST. This is essentially the motherboard "feeling out" on all of its ports to see what's connected. It senses all of your hard drive(s).
3. The motherboard picks one of the partitions on one of the connected drives and tries to run it as an operating system. For a linux system, you want this to be /boot.
4. /boot finds your actual system partition and tries to spin up the OS using it. This partition becomes the "main" one you'll see by default when it's fully up and running.
5. At some point in the boot process, Linux checks the contents of the file at /etc/fstab. "fstab" here is short for "file system table". It's basically a list of other partitions plugged into your PC, and a mapping of where it should be mounted in your filesystem. If your system partition was Partition A, for example, and you had another Partition B that you want to be accessed at the path /B, you'd add a line to your fstab file that says something to the effect of, "hey, reach out to the connected partition with ID , and if it's there, create the folder /B, and make the files inside of the partition show up there." This is called "mounting" the filesystem. You can do it manually at any time with the mount command. The fstab file is just a way to get Linux to auto-mount permanent partitions on startup. You can mount any drive to any path, including /home.

What you need to do is:

1. Format your new drive, and create a new partition there.
2. Mount the new partition with the mount command. Park it anywhere you want. /media/new_home or whatever you like. This will just be a temporary place.
3. Copy everything from your /home directory to the newly mounted one.
4. Move the existing /home folder to literally anyplace else than where it currently is. \home_old would do. It just needs to be out of the way. You almost certainly want to do this only when logged in as the root user, or from another OS running off a USB. You will not be able to log in as any user after you do this until you finish the following steps.
5. Edit your /etc/fstab file to point your new home partition to the path /home. This will "hook up" the new partition.
6. Reboot to make Linux mount the new partition.
7. Verify everything works.
8. Delete the backup home directory.

Answering some of your questions:

Can /home live on a separate drive from the system partition?

Yes. Linux does not care in the slightest where any mounted drives are. A drive is a drive is a drive. If it mounts, it mounts. Just make sure it's in your fstab file.

How should I organize my partitions?

There is no right answer. It depends entirely on what you need and how you intend to use your PC. But since that answer is unhelpful, I'll tell you how I've done mine. I currently have a single 2TiB SSD split up like this:

[ 200 MB boot | ~500 GB system | 2 GB free | ~1.5 TiB home | 8 GB swap ]

Boot comes first and is tiny. System is probably an order of magnitude bigger than it ought to be, but whatever. 2 GB of deliberately unallocated space is there for the exceedingly rare situation where a dumb bug chews up all the storage on the system partition rendering it un-runnable; it's emergency expansion space I can tack on to get it running just long enough to resolve the problem. Home gets the lion's share. And swap goes at the end, where home can cannibalize it if some day I decide I don't need so much swap space.

You would probably organize your drives in a similar way, except one drive would be entirely dedicated to /home and nothing else, and system taking up the bulk of the other drive. That would be the easy and naive solution. Some users may be inclined to create other partitions for organizational purposes. I personally don't care for that organizational pattern, so, w/e.

I cannot help you with your display troubles. :(

I also have trouble crossing wires with the Balkans and the Baltics.

Radio?

Oh, you mean the app with the heart my mom uses?