See the Pop!_OS article.
Pop!_OS only supports the x86_64 (sometimes called amd64) architecture.
Not at this time.
Sure! Pop!_OS is designed for creatives, but since it is based on Ubuntu, it is easy enough for anyone to install and configure a fully functioning system.
See also the Installation guide.
Get involved, contribute your code/solution to the community. If it is well regarded by the community and development team, perhaps it will be merged. The Pop!_OS community thrives on contribution and sharing of code and tools.
When it's ready.
Yes and maybe. Pop!_OS itself is very stable, in no small part due to the testing that goes into the Ubuntu releases that Pop!_OS is based on, as well as the further testing and tweaking done by the System76 team. However, any operating system is only as stable as you let it be. If you like tinkering and tweaking on your own, things may break. If you install unstable or prototype software, things may break.
Bring it up with the Pop!_OS team. This is an unofficial community-backed resource, we have no direct control over Pop!_OS or its advertising efforts.
Essentially, unused RAM is wasted RAM.
Many new users notice how the Linux kernel handles memory differently than they are used to. Since accessing data from RAM is much faster than from a storage drive, the kernel caches recently accessed data in memory. The cached data is only cleared when the system begins to run out of available memory and new data needs to be loaded.
We could distinguish the difference from
$ free -h
total used free shared buff/cache available Mem: 2.8G 1.1G 283M 224M 1.4G 1.2G Swap: 3.0G 881M 2.1G
It is important to note the difference between "free" and "available" memory. In the above example, a laptop with 2.8G of total RAM appears to be using most of it, with only 283M as free memory. However, 1.4G of it is "buff/cache". There is still 1.2G available for starting new applications, without swapping. See
man free(1) for detail. The result of all this? Performance!
The answer to this question depends on your system. There are some fine utilities that may help you find the answer.
First, you need to figure out if this error is something the Pop!_OS team can fix. Sometimes it is not (e.g. Firefox crashes may be the fault of the Mozilla team); this is called an upstream error. If it is a Pop!_OS problem, there is a series of steps you can take:
If you are using a desktop environment like KDE or GNOME, the program should automatically show up in your menu. If you are trying to run the program from a terminal and do not know the binary name, use:
$ dpkg -L package_name | grep /usr/bin/
Package updates will be released when they are ready.