Not to nitpick, there is a 'native' option. Atleast it has been available on Arch for many years now (when SteamOS was on Debian?). In most cases we just the symlink the newer versions of libs to the older versions and the games run fine / better.
It almost is, the first change you'd see is understanding that each container is a separate process and thus for it to auto start you'd need to generate systemd service files. podman has an autogenerator for this, so it is 'just' two extra commands on the terminal but something easy to miss when you are starting out.
In this case semantics do matter so to keep the improvements in the Software Commons as Commons. Weak / Permissive licenses will ensure that all the voluntarily contributed labour would be enclosed and profitable only to those who can hire an army of engineers. Strong licenses will ensure your call for a free exchange.
AGPLv3 or GPLv3 is a good choice to ensure that all changes stay out in the open. Then the competition becomes who can change the code faster and reach more customers.
Escitalopram for anxiety works quite well, you should continue with it, mostly along with Therapy to create productive coping mechanisms against anxiety.
Facing discrimination when you are foreigner is pretty common in most countries. I think if you are from the white diaspora you wouldn't have noticed in the western countries but every time a friend (I am from India) goes to countries in NA & EU, there is almost always some form of discrimination preventing access to service or being overcharged without legal intervention.
Java libs are definitely helpful, the time I mentioned includes wrapping Object oriented code into functions. This is easy if all that is required is one or two methods from the Java, however for more than immediate usage, it feels like building a library just because I need to use it.
In Python ecosystem, that labour already done by someone else, preferably who didn't start writing a library just to deliver code within a week.
One good thing about writing libraries in Clojure is the immense stability and composibility it offers. We can use the same code many years later without fearing breakage,a 'primitive' function can also be easily squeezed into numerous other functions which means reusability is quite high.
However, it is still an impediment for shops less than 5 devs.
Getting a 'hang' of clojure as a language is quite easy, my colleague and I took only two weeks to jump into things. Even today, specific code development is order of times faster than we can do in Python.
However, lack of general 'all-purpose' libraries for numerous use cases means we have to implement that API or library in a general way (if only for our use case) then integrate it into the system.
This approach has worked quite well, creating our own template code (as everything is functional) helps reuse across many projects, however the initial investment of time/labour is something we would like to avoid for the sake of finishing the work fast.
I have been using Clojure as a solo developer for about two years now, there is definitely a productivity increase. It always feels like the amount of time required to do the next thing is incrementally decreasing (like Ologn?)
While all that is fun, Clojure is still a very enterprise ecosystem, where participants don't share as much elementary code as in Python ecosystem. Participants are also quite experienced, thus I have to sit, read through and make architectural decisions for the entirety of the project. When we add this thinking time into the measurement, the time taken for a Clojure 'project' (not a piece of code) is definitely more than Python or Java (IMO).
Zulip has a thread based Instant messaging model which helps facilitate multiple different conversations in the same channel without losing track / context.
https://bitwarden.com/pricing/