revive VS ALVR

The v1.3.4 of revive, the fast, configurable, extensible, flexible, and beautiful linter for Go, is available.

I would suggest checking out something like revive to improve the code. For instance you use an errors.New(fmt.Sprintf(... when you can just use fmt.Errorf(... to simplify it. I am not saying obey everything but there are some good lints included that can even catch bugs (for instance misusing errors.Is or errors.As or general equality).

Linting and static analysis: https://revive.run/

For people using this linter (like me) https://github.com/mgechev/revive

Been using https://github.com/mgechev/revive in all my projects.

The day after, I talked about the Hacktoberfest to Salvador (architect colleague and my technical/career unofficial mentor). He is known for contributing to revive a Golang linter. We decided that I could contribute by solving these 3 issues (2 new rules and add a docker image to the release). Since this moment, I have been coding every available hour I had. It felt so reviving to spend time coding on new projects, rewarding to solve issues for people actually using the tool. Here are all my contributions.

While golint may be deprecated it has been brought back as revive. You can also enable in golangci-lint.

This release adds support for revive, a ~6x faster, stricter, configurable, extensible, and beautiful drop-in replacement for golint.

https://github.com/alvr-org/alvr

They also achieve very low latency, I didn't follow every single optimization they added but it basically boils down to a few encoding tricks (better image in the center, accept blurriness in the peripheral vision), good network infrastructure, and hardware decoding / encoding being really fast.

To use steamvr on flatpak I used this tutorial . There was a disclaimer that nvidia GPUs are not supported, but the guy that suggested it has a 3090, so it might work for me too.

They have a Wiki page on GitHub with a settings tutorial and troubleshooting. A downside with a lot of open-source software is that it's relatively difficult to setup but it might fix some of your issues.

You can play wirelessly using Air Link, Virtual Desktop, or ALVR.

They also have a detailed wiki page on GitHub

https://github.com/alvr-org/ALVR/wiki/Settings-guide Goes in-depth about a lot of the features/settings

Quest 2 needs some workarounds (dev mode account), but once you've done those you can just install ALVR (I recommend nightly). As for the games, check ProtonDB. Some VR games (Pavlov beta, for example) have EAC that blocks proton. Some VR games don't work with ALVR due to https://github.com/alvr-org/ALVR/issues/1392, like the Pavlov beta and Crawlspace. Just install the proprietary NVIDIA drivers and use Xorg and most things should work fine. Steam has Proton, which lets you play Windows games with high performance.