nottheengineer

Maybe they fixed that part, but that isn't a good thing. Now you can't feel whether something is installed as snap and will probably run into snap issues without a clue what could be causing them.

Copied from another comment I wrote about that:

Because snaps are terrible. They constantly break parts of apps for no reason. If you have container issues with a flatpak, just use flatseal to punch a hole through the container. With snaps, people will tell you to install the non-snap version because that's easier than beating snap into submission. I learned that the hard way when I had a university project with kubernetes and docker was installed as a snap. I spent way too much time trying to make it work at all before giving up and switching to a VM on my work laptop where it went surprisingly smooth without snaps.

Flatpaks are better in every way and since this isn't about money, we should all just move on and use the best tool for the job.

But what does canonical think should happen when you run sudo apt install firefox and press Y? That's right, you now have firefox as a snap. Have fun waiting for 5 seconds every time you start it.

Shit like that scares new users away from linux as a whole

You can play whatever you want, it just gets reencoded if it's not AAC already.

Something like mint or fedora is just as easy to install and has less issues than ubuntu (snaps)

Use something other than gnome and, while you're at it, you might as well use something other than ubuntu.

KDE is very hard to break, you can go wild with customization there.

Yes, too many variables. The most important thing is the bluetooth implementation. My Xiaomi android TV has a different latency every time I connect.

Depending on the implementation, the latency can be reduced by tuning the aptX settings (which the gaming mode does) but if those are fine and the latency comes from somewhere else, it won't help.

In general, chinese devices and anything from Samsung are bad in this regard. Other phones tend to be better and the steam deck has been excellect for me.

Unfortunately you need something with long firmware and software support. Qualcomm is your enemy, they stop updating the firmware of their chips after about two years and that's why android phones often stop getting updates less than 2 years after you buy them.

That's mostly politics as well.

Installing arch is a great way to learn. Also don't be scared of daily driving it, it's not like it breaks twice a week. More like once a year, which is better than ubuntu in my experience.

If it has one/two 3.5mm jacks like the A40, that depends on the sound card. Nowadays all PCs have built-in ones that are about as good as what's in a playstation so you'll have to try hard to hear a difference. You might need an adapter to switch between the single 4pin jack and dual 3pin jacks though.

Bluetooth is a mess for headsets so avoid that. The proper wireless ones come with a dongle and have the same quality on all devices.

90hz screen with 180hz polling is what my phone uses as well, it's nice that the deck has now caught up to that.

Also remember to leave your original deck on when downloading games on the new one so it can transfer them locally, which should be faster. There's a setting for that, but I think it's on by default.

But you still need to remember the port of the service you're trying to reach, which isn't great.