Which OS are you using?

Termux provides its own pkg manager and compiled packages though you can setup distros using proot I havent really explored it.

If you are asking about azure VM i have a ubuntu 20.04 image setup.

Could you elaborate?

R has this concept of workspaces. A workspace contains the loaded modules as well as the state of all user-defined variables, their values, etc. And a common workflow is that the entire workspace state is persisted in an RData file. It's like you were working in some REPL, but the last state of the REPL is persisted in between your sessions. So it's a different kind of programming, it's more interactive if you don't need to start from scratch every time. That means if something takes a while to compute, it's OK, because you only run it once, not every time you "run the program".

Ah. I use R a lot but gotten so used to not saving RData and Rhistory that I forgot why they were useful.

I'm not sure it meets your criteria but R Shiny (https://shiny.rstudio.com/) is purely reactive.

I'm currently using Doppler (https://www.doppler.com/) but I'm not sure if it sidesteps the issues outlined in the article.

Doppler solves this problem by storing your secrets in the cloud *hand wave*.

In actuality, the Doppler CLI (a Go binary) fetches your secrets from Doppler's API and injects them as environment variables into your specified process. That looks something like `doppler run -- printenv`. This prevents your secrets from being written to the filesystem in plain text, and prevents the environment variables from being available more broadly. In the case of docker, you would bake the Doppler CLI into your image, thereby sidestepping the documented `docker inspect` pitfall.

Of course, the CLI still needs a way of authenticating to Doppler's API. You authenticate and authorize the CLI by running `doppler login`. This initiates a login flow that you complete in your browser. Once completed, your newly generated auth token is sent back to the CLI. The CLI then saves the auth token to your system keyring for later use. The identifier needed to access that keyring entry is then stored in plain text in the CLI's config file (~/.doppler/.doppler.yaml), which is only readable by the user.

We're exploring other means of injecting your secrets into your application, as some users are wary of using environment variables. This is a challenging problem though as there are few means of injecting secrets that don't require substantially changing your application's logic.

Could you post a link to the client?

Any advice for someone looking to get into the field?

Read the rust book, learn substrate and ink.

What's the name of the library?

Which phone is that?

Not OP but I have a OnePlus6 with 8GB RAM and never have had any issues with it. I've had it since it's release.

POCO.

I think Chinese manufacturers have realised they will never be "cool" enough to have insane profit margins.

I'm on Android and use Castbox. Wouldn't recommend the free version unless you're extremely tolerant to ads. It comes with a good selection of other features (comments, recommendations, etc.) but I don't use them.

I'd also (tentatively) put PocketCasts forward. I switched to Castbox because I encountered an issue that made it unusable, but it doesn't seem like it was widespread when I was trying to find out what was wrong. Unfortunately the Support Team couldn't help so I had to leave it.

It's not hard to figure out but it would be helpful to know which team (by kit color) is attacking.

Also is this just a collection of (controversial) calls VAR ruled as offside? Went through about 10-15 and that's all I got.

Nice idea. And yeah still need to get more added. It's not that easy to find.